Check out the new Bonfire release and boost the announcement ..
Some truly fabulous work went into this, with much care given to the release notes and documentation. In particular I’d like to reference the documentation on fediverse interoperability:
Very thorough. Delightful also to see a list of implemented FEP’s ..
FEPs and Extensions
Bonfire implements and/or experiments with several Fediverse Enhancement Proposals (FEPs), including:
Partial support or conformity to-be-confirmed (help needed!):
- FEP-f1d5, FEP-eb22, and/or FEP-0151 (NodeInfo)
- FEP-2277 (ActivityPub core types)
- FEP-4adb (Derefencing identifiers through webfinger)
- FEP-521a (Representing actor’s public keys)
- FEP-5feb (Search indexing consent for actors)
- FEP-268d (Search consent signals for objects)
- FEP-d8c2 (OAuth 2.0 profile for the ActivityPub API)
- FEP-7628, FEP-73cd, and/or FEP-e965 (Move actor)
- FEP-8967 (Generating link previews for attached links)
- FEP-c0e0 (Emoji reactions)
- FEP-9098 (Custom emojis)
- FEP-f228 (Backfilling conversations)
- FEP-a974 (All Actor types should be followable)
- FEP-1311 (Media attachments)
- FEP-b2b8 (Long-form text)
- FEP-76ea (Conversation threads)
- FEP-7458 (Using the replies collection)
- FEP-c16b (Formatting MFM functions)
- FEP-eb48 (Hashtags)
Work-in-progres, planned, or exploring (suggestions/feedback welcome!):
- FEP-1b12 (Group federation)
- FEP-67ff (FEDERATION.md)
- FEP-2677 (Identifying the Application Actor)
- FEP-d556 (Server-level Actor Discovery using WebFinger)
- FEP-8a8e (A common approach to using the Event object type)
- FEP-efda (Followable objects)
- FEP-9967 (Polls)
- FEP-fe34 (Origin-based security model)
- FEP-0499 (Delivering to multiple inboxes with a multibox endpoints)
- FEP-6fcd (Account export container format)
- FEP-3264 (Federated work coordination)
- FEP-c5a1 (Todos)
Support for additional FEPs and experimental features not listed here may be implemented and enabled by extensions.