You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When someone creates a block list, and users subscribe to it, if that person then deletes their account or is suspended, there's no way in app for those users to then access the list and unsubscribe/unblock. The list persists after account suspension, the list creator is suspended so can't log in to delete it, and in-app users cannot access the list to unblock it (i.e. delete the app.bsky.graph.listblock record) because the profile associated with the list creator returns an error (account taken down).
The only way currently to fix this is with direct API access - I've done it in python fairly simply (listing listblock records for a user with com.atproto.repo.listRecords, finding the ones related to the lists from suspended accounts, and running com.atproto.repo.deleteRecord from a logged in client), and there's a tutorial here on how to do it with browser API calls and a CURL client online
User A creates a mod list
User B subscribes to that mod list with the "block" option
User A deletes or is suspended
User B can now no longer access user A's list to unblock, but anyone on the list is still blocked
Expected behavior
Make the "view moderation lists" dialogue in app properly display the results of com.atproto.repo.listRecords with the app.bsky.graph.listblock NSID, even the ones from invalid/suspended DIDs, and provide a button next to each to run com.atproto.repo.deleteRecord.
Alternatively, properly delete all user lists when an account is deleted or suspended.
The text was updated successfully, but these errors were encountered:
Describe the bug
When someone creates a block list, and users subscribe to it, if that person then deletes their account or is suspended, there's no way in app for those users to then access the list and unsubscribe/unblock. The list persists after account suspension, the list creator is suspended so can't log in to delete it, and in-app users cannot access the list to unblock it (i.e. delete the app.bsky.graph.listblock record) because the profile associated with the list creator returns an error (account taken down).
The only way currently to fix this is with direct API access - I've done it in python fairly simply (listing listblock records for a user with com.atproto.repo.listRecords, finding the ones related to the lists from suspended accounts, and running com.atproto.repo.deleteRecord from a logged in client), and there's a tutorial here on how to do it with browser API calls and a CURL client online
https://cohost.org/signpostkw/post/7429398-how-to-unblock-one-o
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Make the "view moderation lists" dialogue in app properly display the results of com.atproto.repo.listRecords with the app.bsky.graph.listblock NSID, even the ones from invalid/suspended DIDs, and provide a button next to each to run com.atproto.repo.deleteRecord.
Alternatively, properly delete all user lists when an account is deleted or suspended.
The text was updated successfully, but these errors were encountered: