I've been recently thinking about the future of lemmy-meter and where should we go next from where we stand today.

It quickly became obvious to me that I've got no clue where do we stand today. I've been too caught up with my life (and possibly too lazy and distracted) that I never ran a survey to gather any sort of feedback.

Since many of you have been using lemmy-meter for more than a month already, I'd like to redirect the following important questions to you:

Strengths

What do you think lemmy-meter does right? What are its strength? In other words, what makes you enjoy using lemmy-meter (if at all)?

Weaknesses

Where do you think lemmy-meter falls short? What are the things that make unsatisfied or even disappointed?

Potentials

Do you see any areas to explore that we haven't touched yet? Do you think lemmy-meter can expand to cover new realms? What could be the ideas that would take lemmy-meter to next level?

Thank you, Your friendly neighbourhood observability enthusiast

cross-posted from: https://lemmy.ml/post/18315517

> I wanted to share a personal experience that might resonate with some of you. I've been diagnosed with ADD and major depressive syndrome, and for a long time, I struggled to enjoy over-the-board chess. > > The fast pace and constant need for focus left me feeling drained and frustrated – blaming myself for not being able to concentrate. > > Then, I discovered correspondence chess! This format allows for a much slower pace, giving me the time I need to analyze positions and make thoughtful moves. It's been a game-changer. No more pressure, just the joy of strategic thinking without the stress. > > Do you ever feel like traditional chess isn't quite the right fit? > > If you struggle with focus or find the fast pace overwhelming, correspondence chess could be for you! Here are a couple of options to get you started: > > - ICCF.com (International Correspondence Chess Federation): This is the official platform for serious correspondence chess with tournaments and rankings. > > - Daily Chess on chess.com: This is a more casual option where you can play correspondence games at your own pace. > > Let me know in the comments if you've tried correspondence chess, or if you're interested in giving it a go!

I stumbled upon Opening Master the other day and am quite tempted to buy the Golem subscription and use it with Scid.

Have you ever used their databases? If yes, can you share your thoughts please?

In particular:

• How is the quality of the compilation?
• Are there any annotated games in the database (like ChessBase)?
• Is it as large as they claim it to be?
• Does it receive proper regular updates?

cross-posted from: https://lemmy.ml/post/17978313

> Shameless plug: I am the author.

Shameless plug: I am the author.

cross-posted from: https://lemmy.ml/post/15607790

> Just wanted to share some (exciting) news about my Common Lisp project, euler-cl. I finally got the time to sit down and integrate it with Codecov! This means a couple of cool things: > > * 📈 Test Coverage Tracking: I can now see how well my code is tested over time, giving valuable insights into code quality. > * 🏅 Codecov Badge: euler-cl now sports a snazzy Codecov badge to show off! > * 📦 Reusable Setup: The code and setup process should be simple enough to be used as a reference to integrate Codecov (and potentially other services) into your own Common Lisp projects! > > If you're interested this commit is almost all you need: https://github.com/bahmanm/euler-cl/commit/855b014 > > Let me know in the comments if you have any questions or want to chat about integrating Codecov into your own projects!

If you've found yourself manually crafting complex Docker images or repeatedly installing tools, I've got something for you 😁

Check out "fusions" in bdockerimg project (https://github.com/bahmanm/bdockerimg).

---

With fusions, you merge base images into powerful composite images.

Currently there are:

• sdkman.bmakelib
• quicklisp.bmakelib

---

Let me know what other fusions would make your Docker life easier 🙏

I've been working on a small project called bdockerimg.

It's a collection of pre-built Docker images for some less common development tools (currently bmakelib, QuickLisp, and SDKMAN).

The idea is to streamline setup, especially for CI/CD pipelines, where I found myself repeating the same Dockerfile steps a lot. Basic functionality tests are included for a bit of extra peace of mind.

---

👀 Here's the repo if you're interested: https://github.com/bahmanm/bdockerimg 🗣 And here's the the Matrix room: https://matrix.to/#/#bdockerimg:matrix.org

---

I'm curious:

• Does this seem like something you might find useful?
• Are there any specific tools you'd love to see as easy-to-use Docker images?

---

This project is still in its early stages, so any feedback or contributions are much appreciated 🙏

Do you know any chess clubs/programmes for a 5-7 year old in Vancouver/Richmond area?

I would preferably want to be able to look up the coach(es) online or attend one of their lessons before enrolling my kid.

PS: I know I may sound very picky, but I have witnessed first hand how a not great tutor in the early ages can ruin the enthusiasm for chess and change the future.

I just started learning Prolog (based on "Programming in Prolog") and in doing so I've been trying to write code as much as I can.

So far, my little collection of tiny predicates have seemed OK, to my mind.

However, I'm not sure if I'm confident about the most recent piece of Prolog code I've written: https://github.com/bahmanm/prolog-etudes/blob/main/basic-list-techniques/mapping_nested.prolog

Which is why I'm asking if I could please get a code review from the experts. Any hint/feedback is highly appreciated 🙏

bmakelib v0.7.0 has just been released.

The highlight is the fail-fast alternative to $(shell) which relieves you from checking .SHELLSTATUS every time $(shell) is used.

---

Makefile:

```makefile include bmakelib/bmakelib.mk

VAR1 := $(call bmakelib.shell.error-if-nonzero,\ echo Fails hard❗ && false)

unreachable-target : ```

Shell:

text $ make unreachable-target Makefile:3: *** shell.error-if-nonzero: Command exited with non-zero value 1. Stop.

You may have noticed that things have been quite quiet these past few weeks and there hasn't been any new developments.

The reason is that I have recently become a father (again) and my life, as I had expected, have become quite busy leaving literally no free time for me and my FOSS endeavours.

I anticipate that starting from Spring, things will slowly fall back to normal and I will find myself comfortable w/ life's new routines and schedules and will resume the work on lemmy-meter.

In the meantime, in case of urgencies, the best way to reach out to me is via my e-mail (Bahman@BahmanM.com)

Stay warm and keep safe,

Latency, aka Roundtrip Time (RTT) or Time To Load (TTL), is the time it takes for the instance to respond to an HTTP request.

---

Latency indicators have been added to the instance health breakdown dashboard, allowing you to view the latency of your favourite instance compared to itself:

• Past 3 hours compared to the past 7 days
• Past 24 hours compared to the past 30 days
• Past 24 hours compared to the past 90 days

---

Screenshot 1

!

Screenshot 2

!

cross-posted from: https://lemmy.ml/post/8492082

> bmakelib is a collection of useful targets, recipes and variables you can use to augment your Makefiles. > > --- > > I just released bmakelib v0.6.0 w/ the main highlight being the ability to define enums and validate variable values against them. > > --- > > ➤ Makefile: > > Makefile > define-enum : bmakelib.enum.define( DEPLOY-ENV/dev,staging,prod ) > include define-enum > > deploy : bmakelib.enum.error-unless-member( DEPLOY-ENV,ENV ) > deploy : > @echo 🚀 Deploying to $(ENV)... > > > ➤ Shell: > > text > $ make ENV=local-laptop deploy > *** 'local-laptop' is not a member of enum 'DEPLOY-ENV'. Stop. > > $ make ENV=prod deploy > 🚀 Deploying to prod... >

bmakelib is a collection of useful targets, recipes and variables you can use to augment your Makefiles.

---

I just released bmakelib v0.6.0 w/ the main highlight being the ability to define enums and validate variable values against them.

---

➤ Makefile:

```Makefile define-enum : bmakelib.enum.define( DEPLOY-ENV/dev,staging,prod ) include define-enum

deploy : bmakelib.enum.error-unless-member( DEPLOY-ENV,ENV ) deploy : @echo 🚀 Deploying to $(ENV)... ```

➤ Shell:

```text $ make ENV=local-laptop deploy *** 'local-laptop' is not a member of enum 'DEPLOY-ENV'. Stop.

$ make ENV=prod deploy 🚀 Deploying to prod... ```

As of a couple of days ago, uptime indicators have been added to the health breakdown page allowing you to glance at the availability of the instance during the past 7, 30 and 90 days.

Screenshot 1

!

Screenshot 2

!

lemmy-synapse is a light-weight observability and monitoring stack for Lemmy servers.

---

Using Prometheus and Grafana, it allows the admins to visualise and query the stats of their instance. v1.0.0 comes out of the box with 3 detailed dashboards:

• Host stats (CPU, RAM, disk, network, ...)
• PostgreSQL stats (connections, locks, transations, queries, ...)
• Docker stats (container CPU, RAM, disk, network, OOM signals, ...)

---

It runs as Docker compose cluster alongside the Lemmy cluster and does not require any changes to it in most cases. Uninstalling lemmy-synapse is as easy as tearing down its cluster and deleting its installation directory.

---

Got questions/feedback? Pray drop a line:

• #lemmy-synapse:matrix.org
• !lemmy_synapse@lemmy.ml

As an instance admin, would you be interested in receiving alerts in case lemmy-meter detects your instance's health has deteriorated?

The alerts could be sent to any combination of

• a Matrix chat (private or channel)
• a Discord server
• an e-mail address

For example, you could receive an alert if the landing page hasn't been loading for the past 5 minutes.

---

The details of alerting levels and the conditions that'd trigger them will be ironed out later. At this stage I'd mostly would like to know if there's interest in this feature in the first place before getting to the implementation.

---

Follow up on https://github.com/bahmanm/lemmy-meter/issues/71

cross-posted from: https://lemmy.ml/post/6863402

> Fed up w/ my ad-hoc scripts to display the targets and variables in a > makefile(s), I've decided to write a reusable piece of code to do > that: https://github.com/bahmanm/bmakelib/issues/81 > > --- > > The first step toward that would be to understand the common commenting styles. So far I have identified 4 patterns in the wild which you can find below. > > Are there any style guides/conventions around this topic? Any references > to well-written makefiles I can get inspiration from? > > --- > > ### A > > > VAR1 = foo ## short one-liner comment > my-target: ## short one-liner comment > … > > > ### B > > > # longer comment which > # may span > # several lines > VAR1 = foo > > ## comments can be prefixed w/ more than # > ## lorem ipsum dolor > my-target: > … > > > ### C > > > ##### > # a comment block which is marked w/ several #s on > # an otherwise blank line > ##### > VAR1 = foo > > > ### D > > > ##### > #> # heading 1 > # This is a variation to have markdown comments > # inside makefile comments. > # > # ## It's a made-up style! > # I came up w/ this style and used it to document `bmakelib`. > # For example: https://is.gd/QtiqyA (opens github) > #< > ##### > VAR1 = foo >

Fed up w/ my ad-hoc scripts to display the targets and variables in a makefile(s), I've decided to write a reusable piece of code to do that: https://github.com/bahmanm/bmakelib/issues/81

---

The first step toward that would be to understand the common commenting styles. So far I have identified 4 patterns in the wild which you can find below.

Are there any style guides/conventions around this topic? Any references to well-written makefiles I can get inspiration from?

---

A

VAR1 = foo ## short one-liner comment my-target: ## short one-liner comment …

B

```

longer comment which

may span

several lines

VAR1 = foo

comments can be prefixed w/ more than

lorem ipsum dolor

my-target: … ```

C

```

a comment block which is marked w/ several #s on

an otherwise blank line

VAR1 = foo ```

D

```

#> # heading 1

This is a variation to have markdown comments

inside makefile comments.

## It's a made-up style!

I came up w/ this style and used it to document bmakelib.

For example: https://is.gd/QtiqyA (opens github)

#<

VAR1 = foo ```