terribleplan

No, these issues are pretty much by-design. In ActivityPub IDs are inherently tied to the domain on which they were created. Based on the nature of federation it is safe to assume someone somewhere will still go looking for that thing via the outdated URL.

Basically, no:

It can cause some wackiness… basically you will need to maintain that old domain forever and everything will still refer to that old domain.

For example, your post looks like this from an ActivityPub/federation perspective:

{
    [...]
    "id": "https://atosoul.zapto.org/post/24325",
    "attributedTo": "https://atosoul.zapto.org/u/Soullioness",
    [...]
    "content": "<p>I'm curious if I can migrate my instance (a single user) to a different domain? Right now I'm on a free DNS from no-ip but I might get a prettier paid domain name sometime.</p>\n",
}

The post itself has an ID that references your domain, and the the attributedTo points to your user which also references your domain. AFAIK there is no reasonable way to update/change this. IDs are forever.

It would also break all of the subscriptions for an existing instance, as the subscriptions are all set to deliver to that old domain.

IMO your best bet would be to start a new instance on the new domain, update your profile on the old one saying that your user is now @[email protected] and maintain that old server in a read-only manner for as long as you can bear.

So, hear me out... What if we put a scheme in place where anyone who wanted to use the API had to pay for access? And then we charge like 20x what we should to put them out of business. I am sure that would work out well.

If you're taking that approach make sure you shut down the stack before you copy the data over so everything gets copied over consistently (e.g. the DB isn't in the middle of a write), and yes it should pretty much be that easy.

Nope, not from a DNS level. All the posts you are reading are cached by whatever instance your account is on. Basically the only thing served from the remote instance is full-size media uploaded to that instance. Even thumbnails are served from whatever instance you use. Mastodon/Akkoma/etc can be set up to even proxy full-size media for users, which is a feature I imagine will eventually make its way into Lemmy. Your best bet at the moment would be to find an instance that defederates those you don't want to see (or run your own and do so yourself). I know "blocking" an instance is an often-requested feature, so that may end up a feature in Lemmy itself at some point.

Whoo, can't wait for this season of "Wait, I thought we made progress last episode/chapter!?"

I am a bit behind on the manga, but it has been really hard to be motivated to read it. It feels like any minuscule piece of progress is followed by immediate regression. I was very much in the mindset of "Fuck you, I'll see you next week" for a while, haha.

I'll comment my thoughts after I get around to watching the episode a bit later today.

Lemmy and Akkoma, both in docker with Traefik in front.

Ext4 because it is rock solid and a reasonable foundation for Gluster. Moving off of ZFS to scale beyond what a single server can handle. I would still run ZFS for single-server many-drive situations, though MDADM is actually pretty decent honestly.

Nope. PETG is maybe the easiest "safer" option, but AFAIK there isn't a true food safe filament. Also 3d printed things will basically be impossible to clean without extensive post-processing (including probably needing to coat it in something), so "safer" single use pretty much.

Yep, nobody is talking about it at all...

• https://prime8s.xyz/post/3812
• https://lemmy.ml/post/1409164
• https://lemmy.one/post/337062
• https://lemmy.world/post/1079916
• https://lemmy.world/post/1060627
• https://lemmy.one/post/629353

A few of these servers were stacked on top of each other (and a monitor box to get the stack off the ground) in a basement for several years, it's a journey.

No. - sent from my iNstance