Somewhere between Linux woes, gaming, open source, 3D printing, recreational coding, and occasional ranting.
🇬🇧 / 🇩🇪
And two networks and a reverse proxy and four more volumes …
It’s absurdly complex and annoying and lacks proper documentation.
There currently is no sane way to deploy it via docker since it needs half a dozen of different containers and volumes and networks to barely work at all - overwriting/ruining your already existing setup while doing so.
The cleanest would likely be setting up a VM where you set up docker in and let Lemmy do whatever it wants.
ICQ for the Fediverse
You mean, like XMPP?
Oh no. Anyways …
… but it’s pretty bad on “both sides” in my opinion.
That’s actually pretty good!
ChatGPT has a voice?
Like Mastodon, but commercialized?
Streaming for things you consume. Offline media for things you like.
The old age of the Docker image is a bit of a red flag to me.
I settled with SWS since the Docker image and a locally installable version are actively maintained by the creator. It just serves static files and optionally directory listing as JSON (which comes in quite handy).
I can’t remember when I had such little RAM in a machine I own.
How come they always change to a new shitty design once you accepted them previous shitty design?
They slowly start it. When Google killed XMPP they also didn’t do it within a week.
Meta just pays enough.
The thing is, Meta does not care about community safety, or moderation, or protecting user data. (Fun fact: they don’t have a data protection agreement, but a data usage agreement.) All they care about is how they can get the most money out of something. Killing off things left and right of their path.
The question is not IF Meta kills the Fediverse but only WHEN they do it.
So wasn’t Google when they killed XMPP.
I cannot see anything bad here. Blocking an actively malicious actor should be the norm.
TIL