@aussocialadmin Static blocks, you fill them in (its a file of instance you specifically want to block), dynamic blocks are made to be downloaded. In the future I hope to have more block lists that will be downloaded and appended to block.dynamic to generate even more comprehensive block lists.
@alynna thanks for the list.
@aussocialadmin part of the list is my static list from my own recommendations and also ones from foxiepa.ws, and the other comes from the "blockchain" block advisory board.
The main reason for making the script as it is, is so that we can form some more lists that instances will automatically update to (mine does once a day).
If we get enough sources then eventually the relays will be pretty clean of toxic content (it will never be totally clean as long as there are toxic people, but we have a hope of staying ahead of it)
I don't think there's any standard format for these blocklists, but as long as a format can be reformatted to 1 instance per line in quotes, it will work.
@aussocialadmin well one of the reasons I went with "one instance per line in quotes" is its easy, even with a shell script, to get the list into any other format that might be required.
I don't have any current system to "tag" why an instance is being blocked, but this is mostly because I have no idea what the tags would be called, but if I did, we could just have a second field making the format:
And then you could just grep in (or out) what tags you wanted to exempt or include, and use cut -d' ' -f1 to get the instance name.
Welcome to thundertoot! A Mastodon Instance for 'straya