Awesome Fediverse apps part 1 (Emissary and beyond)


Convener: Ben Pate

Notes-taker(s): Ben Pate (probably?)

Participants who chose to record their names here:

Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:

? Interesting Protocols that might work side-by-side with ActivityPub

? Micro-communities with specific needs that are almost-but-not-quite met by Mastodon et al.

Unnamed: ATProto was more difficult than AP / docs needed work

bridgy vs emissary

docker containers, single binaries, yunohost

single static binary

pipelines / step based things

emissary has group based ACLs for special actions, but not cross-server federated actions group membership or external oauth group membership

reminds me of homeassistant yaml vs the core python, so the trust relationship

a UI for a builder could be nice, like scratch or SOAR or https://www.home-assistant.io/docs/automation/editor/

Ben - more details on Emissary, starting at docs site What are the isolation layers between users - there are some ACLs questions about malicious UI plugins and mitigation

testing cross instance groups test instances for folks

this reminds me of some kind of click and drag code blocks

Other tools that aggregate protocols:

Tapestry from IconFactory just jumped into my mind. https://www.kickstarter.com/projects/iconfactory/project-tapestry


Shannon - this would be amazing if it enabled me to manage and manipulate my Twitter archive (as an example, or another fedi service, that would let me manage data from other fedi-adjacent services)

combine Bonfire with Emissary / hybrid of server side Bonfire plugins and Emissary workflows/UI markup Check out Bonfire - they are building apps from micro-services, focusing on some specific user communities (mutual aid, scientific, etc) https://bonfirenetworks.org/

phase of henry ford’s every car is black vs differentiating

Gath.io, meetup, eventbrite

middleware layers

itterative process, make a few plugins and get feedback on the pain points

e.g. like how IAM on AWS vs Google vs Azure works, or Cedar vs OPA, and whether the plugin verbs are limited.

common base format / the lossyness between base formats

e.g. two conversions between your plugin -> ActivityPub -> RSS

not much loss between RSS and ActivityStreams