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?

Shameless plug: I am the author.

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

I'm interested in registering for the tournament but I've got no clue as to where to begin? Where can I find the list of teams? How can I request to join a team?

I'd appreciate any help/hint 🙏

Follow up on a previous post: [DISCUSS] Recent momentary outages

I've been working on a simple opt-in solution, primarily for Lemmy end users like me (but also helpful for admins), to easily check the status/health of their favourite instance.

🌎 lemmy-meter.info

You can find the details of the implementation in lemmy-meter github repo.

❓ @admins: would you be interested in adding your instance to lemmy-meter?

You don't need to do anything except confirming - I'll handle the rest. It should only take a few minutes for your instance to show up in lemmy-meter.

Out of the box it will send only 4 HTTP GET requests per minute to your instance. However that is totally configurable if it sounds too much or too little.

PS: I wasn't sure how to reach out to the admins short of messaging them individually.

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

Follow up on a previous post: [DISCUSS] Recent momentary outages

I've been working on a simple opt-in solution, primarily for Lemmy end users like me (but also helpful for admins), to easily check the status/health of their favourite instance.

🌎 lemmy-meter.info

You can find the details of the implementation in lemmy-meter github repo.

❓ @admins: would you be interested in adding your instance to lemmy-meter?

You don't need to do anything except confirming - I'll handle the rest. It should only take a few minutes for your instance to show up in lemmy-meter.

Out of the box it will send only 4 HTTP GET requests per minute to your instance. However that is totally configurable if it sounds too much or too little.

PS: I wasn't sure how to reach out to the admins short of messaging them individually.

I'm working on lemmy-meter which is a simple observability solution for Lemmy end-users like me, to be able to check the health of a few endpoints of their favourite instance in a visually pleasing way.

👉 You can check out a screenshot of the pre-release landing page.

💡 Currently, lemmy-meter sends 33 HTTP GET requests per minute to a given instance.

For a few reasons, I don't wish lemmy-meter to cause any unwanted extra load on Lemmy instances.
As such I'd like it be an opt-in solution, ie a given instance's admin(s) should decide whether they want their instance to be included in lemmy-meter's reports.

❓ Now, assuming I've got a list of instances to begin w/, what's the best way to reach out to the admins wrt lemmy-meter?

PS: The idea occurred to me after a discussion RE momentary outages.

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

A few days DHH (from 37signals) wrote about how they moved off the cloud and how that has helped reduce their costs by a good measure.

Well, earlier today, he announced the first bit of tooling that they used as part of their cloud exit move: Kamal - which is already at version 1.0 and, according to DHH, stable.

I took a quick look at the documentation and it looks to me like an augmented and feature-rich Docker Compose which is, to no surprise, rather opinionated.

I think anyone who's had experience with the simplicity of Docker Swarm compared to K8s would appreciate Kamal's way. Hopefully it will turn out to be more reliable than Swarm though.

I found it quite a pragmatic approach to containerising an application suite with the aim of covering a good portion of a the use-cases and requriements of smaller teams.

PS: I may actually try it out in an ongoing personal project instead of Compose or K8s. If I do, I'll make sure to keep this post, well, posted.

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

There are two major flavours of variables in GNU Make: "simple" and "recursive".

While simple variables are quite simple and easy to understand, they can be limiting at times. On the other hand, recursive variables are powerful yet tricky.

...

There is exactly one rule to recall when using recursive variables...

🧠 The value of a recursive variable is computed every time it is expanded.

From GNU lists earlier today:

We have learned with deep sadness that Thien-Thi Nguyen (ttn) died in October 2022. Thien-Thi was a hacker, artist, writer, and long-time maintainer and contributor to many GNU programs as well as other free software packages. He was the GNU maintainer of the rcs, guile-sdl, alive, and superopt packages, and he was working on GNU Go as well.

Thien-Thi especially loved GNU Emacs, GNU Taler, and GNU Go: he was the author and maintainer of the xpm, gnugo, ascii-art-to-unicode, and hideshow GNU Emacs packages and made substantial contributions to many others such as vc, as well as to GNU Taler and its documentation.

We greatly miss Thien-Thi in the free software community - his death is a great loss to the Free World.

To be fair, here's the complete paragraph which makes sense:

Vagrant public networks are less private than private networks, and the exact meaning actually varies from provider to provider, hence the ambiguous definition. The idea is that while private networks should never allow the general public access to your machine, public networks can.