anji

Well it is "working" for me. I'm using a YunoHost Lemmy 0.16.7 to type this comment :). But I agree there should be some kind of warning on the project that it's only really partially working, and very outdated (thanks to the recent flurry in activity and changes).

Mainly though I wish YunoHost would just support Docker idiomatically and install Lemmy "as intended". Yeah Docker can be a bit of a pain and it uses more resources, but it also has many real advantages like siloing the apps from the host system..

Were you able to migrate your database from an outdated YunoHost installation to a v18 Lemmy running in Docker? I like YunoHost but I'm considering the same move, as this old Lemmy version has a lot of incompatibilities and other issues.

The main blocker, at least so far, was Lemmy is designed mainly to use use Docker containers to version itself and its main dependencies like Postgresql, while YunoHost runs on the bare system. And since YunoHost is still on Debian 11 it only has access to Postgresql 13 while Lemmy now wants 15. This unfortunately is hard to resolve. YunoHost doesn't want to introduce Docker, and upgrading the entire platform to Debian 12 is slowly happening but it's a lot of work.

Because what Twitter really needs right now is less engagement.

Yeah, this happened to Mastodon (aka the microblogging part of Fedi) also. I was on Mastodon on-and-off for years before the Twitter exodus, and it was a very different place back then. I can see why people miss the overall community on a platform before it became popular, but then I feel like ActivityPub gives us the tools to shape the communities we want, so we have to engage with it and be more selective than we were before.

Oh, yeah in that case I guess Lemmy propagates this information so other instances can show the "banned" information on a user profile.

I think some people reacted a bit too quickly to that sublemmy appearing though.. Give admins some time to evaluate and resolve the situation before impulsively defederating an entire 6000-user instance.

Those must be bans from communities, I assume. A community is linked to a single instance so it can control who is banned. But banning a user from an instance is only meaningful on that single instance. At least that's my understanding..

Nice setup. I grew up using classic macs. Powerbooks, Macintoshes, Powermacs. All such beautiful and functional machines (until an Error of Type 2 occurred anyway). I miss that era of being amazed at these wonderful computers, with seemingly new features every year. MIDI. CD-ROM. Netscape!

We’re just like the big commercial social media sites then. Sweet success!

I think a difference between email and ActivityPub-based social media is there's arguably less of a need to have federation between any two servers. If you can't email the government, your sister living abroad, or a client, that's a big problem. But if you can't follow a cat pictures account or your friend's constant stream of baseball rants because the servers don't federate it's not quite the same.

If Meta becomes ActivityPub interoperable instances may or may not federate with them. Either way it's not necessarily going to change my social media experience.

Having used both, while the market implications of NACS are still unclear it sure is the more ergonomic of the two standards. Those CCS2 DC connectors are just too large and unwieldy.