The base consumer models from regular brands usually have no write cache and are thus cheaper, and obviously slower, but for data storage that doesn’t matter so much.

But you can also look into 2.5" HDDs if you are looking for power savings and noise reduction over regular HDDs.

Well, obviously if you host from your home ISP, people will be able to figure out your home’s approximate location via a reverse IP search.

But otherwise go for it. It’s not that hard to do and a nice learning experience.

Something like that could be also interesting for a Lemmy frontend to make it easier to share images on instances that have strict upload limits.

Wait for the next hardware upgrade and then set up a new system while keeing the old system running in parallel.

It requires a bunch of browser features that non-user browsers don’t have, and the proof-of-work part is like the least relevant piece in this that only gets invoked once a week or so to generate a unique cookie.

I sometimes have the feeling that as soon as some crypto-currency related features are mentioned people shut off part of their brain. Either because they hate crypto-currencies or because crypto-currency scammers have trained them to only look at some technical implementation details and fail to see the larger picture that they are being scammed.

Movim does, for Libervia and Dino I am not 100% sure right now, but at least for Libervia the browser version should have it as it is really more of a general Webrtc browser feature than client specific.

Maybe it was based on the “lifetime” of their hamster 🤷

The currently common older implementation of e2ee in xmpp has the same issue with only the message body being encrypted. There are newer specs of OMEMO that have better metadata protection, but its adoption in xmpp clients has been very slow.

Prosody is more of a sandbox, with Snikket being a preconfigured version of it, but yes running Slidge will be a bit easier with a normal Prosody server.

Today xmpp uses a distant relative of those original jingle specifications, which have been modernized to use Webrtc.

Xmpp is mostly used for private groups and 1:1 chat, so more of a WhatsApp than a Discord replacement.

But you can find some public channels here: https://search.jabber.network/

The issues you mentioned have been fixed, and XML was never an issue 😅

Jitsi-meet is already using xmpp under the hood.

But there are some efforts to add multi-user video calls to full xmpp clients as well. Dino can already do it for a while, and Movim and Libervia recently added experimental support.

Its not quite a full Discord replacement, but for private groups it works quite well.

Why would you down-grade from Snikket to Matrix?

If you want to skill up a bit add a Slidge.im gateway to your Snikket xmpp server to access Matrix (and Discord etc.) from there.

Jitsi-meet does that. Easy to install as well.

Cool. It’s actually still on my long to do list to try this. Thanks for the update!

I use one pod per app more or less. The reverse-proxy conf depends a bit on the specific app so that depends, but it will probably work for most by sharing a network and exposing the ports in the pods

Don’t use the kube stuff. That’s entirely seperate from Quadlets and some sort of Kubernetes compatibility.

Woodpecker is more mature and I can control access better since I am not the only one using my Forgejo. But I think at some point the built in ones might reach feature parity.

Experimented with selfhosting a Woodpecker CI as a complement to my Forgejo.

Works quite nicely, I just need to set up a native ARM64 agent as the overhead of cross compilation on x86_64 is quite big.

Just install Linux on the laptop and start experimenting.

Yunohost is very easy, but something like Debian or Fedora Server Edition will be more flexible.

Matrix mobile clients got worse, yes 😅

Otherwise not really. Three years ago Conversations was quite good already, although the newer forks Cheogram and Monocles added some nice convenience features.