Removed the post myself after realising the community only allows articles. My bad!

Please refer to the pinned post. Support questions should be posted on !lemmy_support@lemmy.ml.

Migadu doesn’t provide sources for their deployment, as far as I know, but most of the components they use are open and available on the usual places: https://github.com/migadu

On my system, I can use the compose key to type a bunch of unicode chars, such as —, …, ≠, → and so on. Sadly, the pervasive use of em-dashes by LLMs ruined my use of them… It’s a pity, because I quite like them stylistically.

Yes, “they” (the Lemmy maintainers and contributors) should eventually do that, but those systems are hard to get right, doubly so on a decentralised network such as this one. For now, it doesn’t seem to be a priority (v1.0 is).

The recent evolution is great and I’ve been a happy KDE user for many years, but my oh my is NetworkManager bad. It’s not good on all systems that use it under the hood, but I find it especially unintuitive and so outdated. The applet thing is fine (still suffers from weird behaviour from NM’s core), but actual settings screen drives me crazy… The Bluetooth one should also receive some love, but it’s decent. NM needs serious revision.

I agree it’s a nice way to try it out, though it has some limitations. Also, my experience with encryption at rest has been a mixed bag, though I think that’s just because Nextcloud’s implementation isn’t quite mature enough.

(happy cakeday!)

Yes! Oh my, I’m silly; that was precisely my point and I managed to mess it up 🙃

Thank you for the correction!

As others have also mentioned, Minoxidil can be effective at slowing or stopping balding, with daily application, though it isn’t immediate (may take a couple of weeks to start showing results). It can vary a lot from person to person, so give it a shot for a couple of months before deciding whether to commit or not.

While the issue of the inter-server protocol being overly chatty is very much real, putting the burden on the users isn’t a good solution.

The focus should instead be on improving the protocol itself and its implementation with better algorithms, batching, etc. I’m not super knowledgeable about the inner workings, but I feel like there’s still some relatively “low hanging fruits” in the protocol design (are activities properly batched? are they sent as linear broadcasts to all federated instances? could we use some alternative broadcast distribution, like binomial? etc) and implementation (is the data model leading to some expensive operations? are the SQL queries well written? could we speed them up some other way?).

I say this as someone who’s been running an instance for many years now, and can tell you for sure it has been a rather bumpy ride, as a small server. Running a good and fast server with lots connections is not cheap; not as much as it should, at least imo.

This. And to add to what other commenters have said, by using Bitwarden and paying for their Premium plan (very cheap, just $10/year), even if you don’t use all their features, you’re supporting a good project. It’s critical infrastructure, I think the price is more than fair.
Either way, you should always make periodic backups from any cloud service you use, encrypted of course.

Very useful, even for someone who has been using Linux for many years. Sometimes you just forget or need that tool you rarely use. tldr can be much handier than parsing a man page when you’re in a pinch.

I use the tealdeer implementation, but any is fine really.

Great comment, cheers!

It’s named after some things: https://github.com/LemmyNet/lemmy#whys-it-called-lemmy