fyrfli/fediblock
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

added to README

Browse Source
This commit is contained in:
Camille Frantz 2025-01-27 15:33:18 -06:00
parent 17822fb013
commit cc30ff7144
Signed by: fyrfli
SSH Key Fingerprint: SHA256:anc9kpwB26LKDnZerjcRFNSnp4JSd+rX62ouDLrh46o
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@ -13,12 +13,21 @@ i wanted to envision something less opionionated. now, granted, blocks are inher
for example: an instance may want to remain open to places like mastodon.social for the purposes of exposure, but they don't want to open to places like kiwifarms... many instances block mastodon.social because it is one of the largest instances with arguably the least amount of moderation oversight. if you've been on the fediverse for any length of time, you know how CSAM and spam can get through their moderation team real easily. for example: an instance may want to remain open to places like mastodon.social for the purposes of exposure, but they don't want to open to places like kiwifarms... many instances block mastodon.social because it is one of the largest instances with arguably the least amount of moderation oversight. if you've been on the fediverse for any length of time, you know how CSAM and spam can get through their moderation team real easily.
my idea is categorising blocks (and receipts) by tags. each instance (and receipt) can be assigned one or more tags to describe what that instances existence on the tool. my idea is categorising blocks (and receipts) by tags. each instance (and receipt) can be assigned one or more tags to describe that instance's existence on the tool. it will also make searching easier - you can find all the latest entries for ... say ... harrassment.
i am including a set of tags to begin with in json format.
i do include a users structure because it may make sense to lock some functionality behind verified accounts - adhoc adding of new entries, for example - so having that included from the start made sense. and since i created the project, my user is likely to be hard-coded into the project at almost all stages. (if you are cloning this project, please keep that in mind). later on, this will change but for now ... this makes it easier for me.
further, folks can request a customized list based on tags to use wherever they want. further, folks can request a customized list based on tags to use wherever they want.
now this is a nascent project. i don't promise to have code ready for proofing any time soon. it is also highly dependent on the platforms we currently have at our disposal. as of this writing, i intend to start by customising for GoToSocial and Mastodon (and its flavours/forks). now this is a nascent project. i don't promise to have code ready for proofing any time soon. it is also highly dependent on the platforms we currently have at our disposal. as of this writing, i intend to start by customising for GoToSocial and Mastodon (and its flavours/forks).
ultimately, i expect this to live online somewhere ... but i will also keep in mind that it is open source and someone else might want to clone and take it in a different direction.
finally, i will likely move to github if this gets off the ground and invite collaborators. but that's a ways off.
___ ___
anyway - that's the begining spiel for this project.
for more information, dm me @fyrfli@diaspora.im - let's talk. for more information, dm me @fyrfli@diaspora.im - let's talk.