After 5y+ running herds.eu I have lots of accounts that are no more active/reachable (quitter.se, et al.) and cluttering the install. It might be a good idea to make a script to clean those? Like:
deleting profiles/previews/avatars/remote medias of unreachable instances
unless a user has interacted with a notice (reply, fav, repeat), in that case save the notice and related medias
remove instance/feeds of followers/followed
Moreover, I'm getting a good bunch of ERROR: unsubscribe request failed when running Ostatus/scripts/gcfeeds --delete, like:
Getting a lot of errors when updating ostatus profiles (30k+ profiles), like:
Updating OStatus profile 'http://quitter.se/user/122134' ... Could not reach profile page http://quitter.se/user/122134.
Getting a lot of errors when updating ostatus profiles (30k+ profiles), like:
```
Updating OStatus profile 'http://quitter.se/user/122134' ... Could not reach profile page http://quitter.se/user/122134.
```
Things get worse when trying to delete an account with a lot of interactions: being unable to connect to dead nodes makes impossible the deletion. Update_activitypub_profiles.php runs here every week, so i guess it is not doing its job correctly...
Things get worse when trying to delete an account with a lot of interactions: being unable to connect to dead nodes makes impossible the deletion. Update_activitypub_profiles.php runs here every week, so i guess it is not doing its job correctly...
An (auto) correction to my last post: as noted by @diogo, update_activitypub_profiles.php script deletes no-longer existing remote profiles. That is true, but only if the remote node is working.
An (auto) correction to my last post: as noted by @diogo, update_activitypub_profiles.php script deletes no-longer existing remote profiles. That is true, but only if the remote node is working.
Well, of course, but how would you tell apart a dead instance from one that is having temporary issues? At most we could try to come up with a script that allows to delete local data from a given instance. But in general, this seems like a bad idea. You can't delete a profile and leave their previous posts.
Well, of course, but how would you tell apart a dead instance from one that is having temporary issues? At most we could try to come up with a script that allows to delete local data from a given instance. But in general, this seems like a bad idea. You can't delete a profile and leave their previous posts.
You are right, @diogo, that's something tricky. Maybe implementing that script and using it for nodes that you know for sure aren't coming back (i know some of them).
You are right, @diogo, that's something tricky. Maybe implementing that script and using it for nodes that you know for sure aren't coming back (i know some of them).
After the exponential queue retries, stop attempting potentially dead nodes and prompt the admin for action in the /panel
Review admin tools regarding dead actors and its local cached presence
TODO (TFN):
* After the exponential queue retries, stop attempting potentially dead nodes and prompt the admin for action in the /panel
* Review admin tools regarding dead actors and its local cached presence
After 5y+ running herds.eu I have lots of accounts that are no more active/reachable (quitter.se, et al.) and cluttering the install. It might be a good idea to make a script to clean those? Like:
Moreover, I'm getting a good bunch of ERROR: unsubscribe request failed when running Ostatus/scripts/gcfeeds --delete, like:
Getting a lot of errors when updating ostatus profiles (30k+ profiles), like:
+1 on this. Deleting those profiles would save some space
ActivityPub's
update_activitypub_profiles.phpscript deletes no-longer existing remote profiles. Don't know if OStatus has something like that...Things get worse when trying to delete an account with a lot of interactions: being unable to connect to dead nodes makes impossible the deletion. Update_activitypub_profiles.php runs here every week, so i guess it is not doing its job correctly...
An (auto) correction to my last post: as noted by @diogo, update_activitypub_profiles.php script deletes no-longer existing remote profiles. That is true, but only if the remote node is working.
Well, of course, but how would you tell apart a dead instance from one that is having temporary issues? At most we could try to come up with a script that allows to delete local data from a given instance. But in general, this seems like a bad idea. You can't delete a profile and leave their previous posts.
You are right, @diogo, that's something tricky. Maybe implementing that script and using it for nodes that you know for sure aren't coming back (i know some of them).
TODO (TFN):