rougetimelord
commented
10 months ago I'm in on this one. The extension already creates a database of all blocked users, it should be pretty easy to implement a feature to export to a CSV/JSON file, basically what the the history page already does. On the import side we would just need to add an import function in the background script that goes through an imported file and pushes usernames to the queue.
The export function I proposed might not be ideal for making curated lists though, because it would only contain users blocked by the extension. I'm not sure if the extension currently captures manual blocks, and it definitely does not have a way to distinguish blocks for different lists.
In terms of following a served list, I think that there might be some privacy concerns? Another idea I have is that the extension could add the list name as the reason for a block so that the users on the list would get unblocked on unsubscription from the list.
cooljeanius
alanpaone
Skillou
Sorry for the maybe stupid request, but with the rise of AI in art spheres I've been wishing for some way I could make use of my ability to detect plagiarism to help others, but I don't have the ability to program to make something as useful as this. From what I see, Kheina is involved in furry art culture, so this might also be relevant to their world.
I wanted to float the idea adapting the way this add-on detects and acts on the site to function (at least, if it does how I assume it does) similar to a uBlock for Twitter users, or more spiritually a return of blocklists, where people more dedicated to the task can update what are essentially lists that identify the @ usernames (or otherwise more concrete methods) associated with whatever the blocklist is for (in my case, AI plagiarism) and export them or host them somewhere periodically updated. This would hopefully have the accounts blocked as soon as it appears on the persons feed automatically.
Ideally, a way to update this automatically would be ideal (as more and more continue to pop up and hit algorithms), which I assume would be a call to some server to update the list, but even local list importing would still be good starting functionality. I think the automation power this potentially brings would actually create a notable dent in the circulation of AIGen, and help people filter out fraudulent content they shouldn't have to be exposed to if they don't want when the algorithm demands it and takes advantage of their benefit of the doubt.
Much like the effectiveness of Adblockers, this could have a similar effect rather than relying on every individual to be knowledged and experienced in identification and building their own blocklists.
Thanks,