But do we need some kind of SSO layer with DID verification? All I need to prove my identity anywhere, technically, is my private+public keypair. As long as I hold on to this keypair, distribute it between apps/computers, back it up, I could log in anywhere on a federated platform and use it.

I hope we’re going to see key-based decentralized identity on ActivityPub at some point… Having accounts tied to instances is just not very robust or scalable.

What they really mean is: Polite to them, the people with the means of easily inflicting deadly violence upon others.

Gun ownership is just another expression of the deep selfishness ingrained in American culture.

Someone should tell Retsuko about this kind of service.

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.

I’m no expert but I think we’re looking at parts of the vehicle which were outside the pressure hull. Those parts would not have been subjected to such extreme forces when the hull failed.

Most bits of a DSV are actually outside of the pressure hull, just look at the designs of Trieste or Limiting Factor. This is to maximize the space available to human passengers inside the relatively small (and very expensive to construct) hull.

We’re on the Fediverse now. Our software has way better bugs.

I mean obviously “Taxation without Representation” is one of the foundational injustices which led to the declaration of independence, so I’m in favor for letting non-citizen residents vote. But if the state constitution says voting is only for citizens then maybe the state constitution needs to be amended…

A few states do have provisions for letting non-citizens vote in local elections: https://ballotpedia.org/Laws_permitting_noncitizens_to_vote_in_the_United_States

We continue to inch closer to full-blown corporatocracy. We’ve all watched and read enough cyberpunk to see where that leads.

It will always be LLIIIINE PIEECE to me

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.

Great news. I think we’re still not quite there yet with cultivated meat, but it has great promise. Cultivated meat has the potential to be cheaper, far more environmentally friendly, obviously more ethical, and maybe even healthier. I hope it reaches full scale production with all these benefits in my lifetime.

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.

The Fediverse is still a strange concept to a lot of people. They assume only email is federated and the rest of the web is sites with only internally facing channels of communication.

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.