💾 Archived View for ix.cyb.red › wiki › fediverse-embassy-protocol captured on 2024-06-16 at 12:41:30. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-09-28)
-=-=-=-=-=-=-
BEWARE : THIS IS A DRAFT AND SUBJECT TO MY WHIMSY
the very first steps towards decentralized cooperative moderation. the embassy protocol is meant to be flexible and is inhernetly multi-polar. the goal is really to create reasonable tools for handling the complexity created by pluricultural federation.
join the private beta (ETA/TBA) for access to both the hosted instance and testnet. developers are free to start their own constellations using the available source code. beta access is provided by the nascent IX / heropunch cooperative.
the embassy protocol tries to address the various challenges of content curation, moderation, and remediation in a proactive manner. there is no singular "mastodon culture" or "fediverse culture" that this project aims to preserve. cooperation and diplomacy are not code-words for assimilation. the success of the fediverse is a huge opprotunity to rethink how online communities function. the goal of this protocol is to enable users and admins to create permeable fractures in the federation graph, based on consent and mutual agreement rather than naive discovery.
shift the focus from policing the network to finding common ground, friendship, and trust.
these are the seeds of community that are often left by the wayside in favor of the pressing need to defend and carve out a space. rather than thinking about what is "good for the fediverse" consider what is good for your community. federation should be a value add and way to knit related websites together into a greater whole.
allow list federation reduces the necessity for extensive block lists, but these are still available for peace of mind and added control.
block lists are an important tool for creating safe communities, especially if they are populated by vulnerable groups. even with good lists, you still run the risk of new servers harming community members before their instance can be identified as malicious. depending on the community, the severity of this limitation varies. using an allow-list to control federation can be a safer option, but managing an allow-list manually is a lot of work if you want mostly permissive federation.
designed with small instances and distributed communities in mind. mod delegation allows the mods from a constellation of instances to cooperatively moderate many independent instances all together. the embassy protocol embraces the multi polar nature of federation. instances can exist in multiple spheres of influence at a time.
instance constellations have the option of creating a pact to signify an agreement to long term collaboration. these are used to generate a join mastodon type of experience centered around the pact members.
various projects have been created on the fediverse to provide a safe baseline for new communities to adopt. this is important and underappreciated work. these authorities are available for instances to adopt. further moderation decisions may override the base weights applied by authority lists.
https://docs.joinmastodon.org/methods/admin/domain_allows/
MRFs with allow in pleroma/akkoma
ask for a PR to add misskey support
basically a hosted admin client with specialized capabilities
publish & share moderation data
trust-based cooperative moderation
runs on testnet during beta to practice decentralized protocol switching
build on offsystem & relax.js primitives EZ hosting mode