I don’t personally use iOS, but some friends of mine have given good reviews about Podcast Republic - note that it has a one-time ads free unlock to it.

ActivityPub does use cryptographic keys for Actors (“users” in this case) - so even in theory if you were to destroy your instance and then set it up on the same domain and recreate the user, things would be quite broken still… But unfortunately it still does rely on the domain name itself, so I agree.

I think the problem is, without the domain name, there is no way for you to lookup who @russjr08 would be, or where to send data to them. The domain effectively acts as a mailing address (a well suited analogy considering that ActivityPub also uses inboxes/outboxes) so that Instance A always knows that User B can be found on Instance B.

I doubt its an impossible challenge to solve, but probably quite a difficult one I’m sure.

They have access to your password hash, effectively the “infrastructure” admin(s) as I’ll call it (not admins of the site - they need to have access to the actual system that is running the instance) have access to the same things that infrastructure admins of another site would have.

Lemmy should implement proper post deletion, possibly with a delay to allow moderators and admins to inspect deleted posts, but expect anything you share via ActivityPub to follow the once on the internet, always on the internet rule even more than in the past.

How would this be done? Like you mentioned, anyone can run a modified instance of Lemmy that does not honor delete requests. I suppose you could put something that retrieves content from other servers as a pull operation instead of a push, but that’s going to break Lemmy’s ability to work with other ActivityPub applications (at the very least).

Yeah, AFAIK ActivityPub itself heavily relies on the domain being part of your identity - so its not really possible to change the domain on any of them, along with other federation implementations such as Matrix.

This is why while Mastodon allows for profile transfers, it doesn’t transfer your post content - it simply just sends a signal to your followers to unfollow your old account and follow your new one. The actual content itself is intrinsically tied to your identity on the old domain.

Authorized Fetch has been a thing for a bit on Mastodon at least - but as far as I can see it’s a global toggle rather than saying “If you present as a domain on the blocklist then you must be authorized to fetch this resource” (the selective authorized fetch I assume they’re talking about).

Never used Akkoma though, so I can’t speak for it.

To be honest, as an instance owner I would not want to even have that data touch my instance - that would be a nightmare waiting to happen whether some instance operator does so with or without malice intent (such as a server compromise).

I just did this the other week, all of your followers (who are on servers that are still online of course) will follow your new account and unfollow the old account.

It was a bit funny, because I had already signed into the mobile I used and was flooded with notifications as each account followed me (some might be slightly delayed, but all in all it didn’t take more than an hour for the ~50 followers I had).

You will however want to export the list of people you follow from the old account though, because that isn’t automatic. Once you plug the export file into the new account though it’ll do the rest for you.