this post was submitted on 22 Jul 2023
3 points (80.0% liked)
ActivityPub
674 readers
5 users here now
This is a community dedicated to discussing technical details related to ActivityPub.
We welcome developers familiar with the protocol!
https://activitypub.rocks/
https://www.w3.org/TR/activitypub/
Other ActivityPub communities on Lemmy
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The proper way would be to probably make an API client that logs in to each of these accounts, queries the list of subscribed communities, and unfollows each community. But I'm not even sure the backend deals with all this correctly... I'm working on testing to add it.
As you have discovered, your instance is not initiating a "fetch", it is actually the other servers sending to you. Those other instances have your now-gone users (on your server) still subscribed to the communities.
Short of defederating, you have to get the other servers to remove your subscribers to those communities, or at least unsubscribe. This kind of thing is currently not trivial to do, likely requires new code or direct SQL statements for those other servers to execute.
So I guess, I'm just gonna have to wait until Lemmy devs implement this?
I am actively working on testing code to try and reproduce what happens in these situations when a remote server does not unsubscribe from communities. Doing a direct SQL delete of rows from the persons table is perhaps out of scope, but there is a lot of cleanup. There was an explosion of instances (new servers) out there and many have since gone offline. So I am sure the the topic of how to clean up old orphan data will keep coming up.
Oh, it's great to hear! Where can I follow your progress on this topic?
A lot going on right now regarding federation consistency between servers, so not sure, it's scattered on a variety of topics. You are welcome to comment reply to me every few days if you are curious.