Public
- Public
- Network
- Groups
- Featured
- Popular
- People

screenshot from the linked FSEP plan which reads: Onboarding The administration onboarding process can be enhanced by leveraging the additions to the back end detailed in the Service Feature Integration. 1.1 At setup time, administrators should be able to upload a deny list or select a default to deny list provided. For MVP, only one deny list provider needs to be supported in this list (The Bad Space). Ultimately, the goal is to allow users to choose from one of several vetted tier 0 lists.

Download link

screenshot from the linked FSEP plan which reads: Onboarding The administration onboarding process can be enhanced by leveraging the additions to the back end detailed in the Service Feature Integration. 1.1 At setup time, administrators should be able to upload a deny list or select a default to deny list provided. For MVP, only one deny list provider needs to be supported in this list (The Bad Space). Ultimately, the goal is to allow users to choose from one of several vetted tier 0 lists.
https://kolektiva.social/system/media_attachments/files/111/054/411/087/410/975/original/60a27382bc528313.png

Notices where this attachment appears

Embed this notice
ophiocephalic 🐍 (ophiocephalic@kolektiva.social)'s status on Wednesday, 13-Sep-2023 17:45:28 JST ophiocephalic 🐍
in reply to

@TheGoodSpace
Something that lots of folks in this convo are probably not aware of is that the Bad Space isn't just another blocklist or website. It's at the center of a plan called FSEP which (at least initially), during the setup of a new fediverse instance, would load the Bad Space blocklist, and only that blocklist, by default. If the scheme is deployed the instances on that list could end up being defederated from most of the fediverse. Agreement from only two "trusted sources" is required to affirm an entry on the Bad Space.
https://nivenly.org/docs/papers/fsep/

In conversation about a year ago from kolektiva.social permalink