Most of the Koopa kids were named after musicians
- Wendy O. Williams from the Plasmatics
- Iggy Pop from Iggy Pop & The Stooges
- Roy Orbison, the songwriter and rock & roll legend
- Lemmy Kilmister from Motörhead
- Ludwig van Beethoven, obviously
Most of the Koopa kids were named after musicians
YunoHost “packages” are just scripts. In the case of Lemmy, Lemmy_ynh’s install script actually fetches the Lemmy Docker image and extracts the files (including pre-built binaries) from it. And then it writes the config files to use the system Psql instance instead of a containerized version.
FWIW I don’t care how YunoHost installs the apps. Whether it’s fetching and running containers, or building from source, or grabbing binaries. As long as the apps work and the reverse proxy gets wrangled it’s fine with me. Just in this case refusing to run the Docker images directly is, at least momentarily, a problem for updating the app.
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.
If they really do shut off API access I’ll go into partial link aggregator withdrawal. My Lemmy instance still isn’t upgraded to the latest versions which are compatible with apps, so I don’t browse on my phone.
We’re on the Fediverse now. Our software has way better bugs.
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.
Hey Stux!
Yeah YunoHost is extremely awesome. I use it to host my Mastodon and Lemmy instances. It’s just a little unfortunate that until Debian 12 is supported, their supported Lemmy version is stuck at 0.16.7. So if you want to set up an Lemmy instance today YunoHost might not be ideal.
Hopefully they can get Debian 12 and latest Lemmy support working without any roadblocks.
Yunohost is awesome. I use it myself for my Lemmy instance. Unfortunately because YunoHost doesn’t use containers and Lemmy now requires psql 15 it’s stuck on Lemmy 0.16.7. So it’s not ideal if you want the latest version of the sure to be quickly changing Lemmy software.
There’s many different ways DID could be implemented on top of ActivityPub. I don’t think full content replication (what you’re mentioning) is likely as that’s a fundamentally different style of protocol.
But I can imagine signing in to a different instance with my ID, at which point I subscribe to all my communities from this instance and get notifications if someone replies to one of my comments etc. Just as if I had created an account on this instance and had posted from there. It just means “your” instance can go down and you can continue future interactions mostly uninterrupted from another instance.
YunoHost is a tool which aims to solve the problem of (relatively small scale) self-hosting for people. I use it to host my Mastodon and Lemmy instances and it was very easy. I haven’t dealt with email but that’s also something it supports.
It’s a pretty great platform, although unfortunately it’s currently unable to upgrade Lemmy past 0.16.7 which is a bit of a pain… So it’s hard to recommend it for Lemmy right now.
100% agreed with both. Especially DIDs just need to happen on all ActivityPub platforms. It will not only free users from being locked to an instance, but it will also allow instances to be much more flexible in scaling their capacity. Lemmy.ml is overloaded because they have too many users, and anyone who signed up there can no longer use their account. DID would allow them to immediately use their account from any small or large instance with spare capacity without changing the experience. The same would go for Mastodon.
Beehaw only defederated from Lemmy.world because of the currently limited moderation tools in the software. This is not going to be a problem forever.
I hope people can find communities both on large instances (Beehaw, Lemmy.world) as well on as very small niche instances. Discoverability is a bit a problem but I think over time we will find communities we like, and participate in them. What instance they are hosted on is not all that important.
Their first album indubitably is my favorite, obviously.