Discussion

@spencer yeah you could add extensions or even easier you can seamlessly switch flavours

@berniethewordsmith if you are looking for a standard microblogging experience with some focus on safety and moderation, the Classic flavour (https://bonfirenetworks.org/app/classic/) should do it :)

🚀 Our website just got a major update with new resources for communities and developers:
📚 Enhanced documentation & brand new tutorials section ( https://bonfirenetworks.org/courses/ )
🌐 Explore our apps ( https://bonfirenetworks.org/apps ), extensions ( https://bonfirenetworks.org/extensions ), and themes ( https://bonfirenetworks.org/themes )
🔍 Learn about our pilot communities
( https://bonfirenetworks.org/pilots )
🌿 Join our journey to build an open cooperative hosting ecosystem ( https://bonfirenetworks.org/hosting )

@jorge @UlrikeHahn @niboe@red.niboe.info FYI a topical recent mailing from Free Software Foundation Europe: https://notes.bonfire.cafe/E3IYMud-TpiXHN_T_hrJ0Q?view which mentions this presentation: https://media.fsfe.org/w/cLSKf9oReoxLPj8CpNarHV

@jonny sounds good! we'll set up a dedicated discussion space soon and share it here! @UlrikeHahn @niboe@red.niboe.info

@UlrikeHahn sounds great, we're up for a call to share our plans and discuss how we can follow up together @niboe@red.niboe.info

@UlrikeHahn this is super interesting, together with @niboe@red.niboe.info we've started co-designing a federated digital space focused on open science. We're building it in public (you can see the current status here https://bonfirenetworks.org/open_science/ ) and it would be great to include your thoughts and improve the document together :)

@tess @jenniferplusplus @randulo @smallcircles @cheddarcrisp Great points, thanks! Have opened an issue about trying to re-use the collections approach from groups for addressing replies to an activity with custom boundaries/circles as well: https://github.com/bonfire-networks/bonfire-app/issues/804

@jenniferplusplus @tess @smallcircles @cheddarcrisp I think that’s how Mastodon and Pixelfed are implementing groups instead, so actors can see/follow/address a group/collection, comparable to mailings lists (or usenet).

A circle in our case is private to its creator, who alone can see their circles and who’s in them, and can address a circle when posting, like defining a group/list in your address book, and addressing it as BCC in an email.

@tess @smallcircles @cheddarcrisp granted both of those two features are more focused on privacy (which puts authors/posters in control) than information overload/segmentation, for which we’re thinking about another approach (which puts readers/followers in control): https://github.com/bonfire-networks/bonfire-app/issues/646

@spencer we’re working on the last few milestones towards 1.0 at the moment https://github.com/bonfire-networks/bonfire-app/milestones?direction=asc&sort=title&state=open and hope to have the RC1 (release candidate) ready soon, but the honest answer is “when it’s ready”

@tess @smallcircles @cheddarcrisp while protocol-level support would be ideal, both of these features can work fine (and have been implemented in Bonfire) without it:

- personas (multiple profiles per account) appear as separate users to everyone else, and can be followed individually

- when you address a post to a circle(s) it’s usually not a public post, so we basically bcc the circle members so their servers know who to show it to (similar to a group DM)

@smallcircles @tess @cheddarcrisp that's a different project, our website is at https://bonfirenetworks.org

@lawik @ex_06 I am considering adding a write buffer similar to this though, to batch DB operations when an instance is being hammered with incoming federation: https://github.com/plausible/analytics/blob/master/lib%2Fplausible%2Fingestion%2Fwrite_buffer.ex

@lawik @ex_06

We have DB-backed queues using https://github.com/sorentwo/oban to avoid dropped activities

@zabbeer@floss.social thanks 😊 @dynamic you may want to have a look also at https://bonfirenetworks.org/design

@triptych awesome! that sure sounds like the kind of projects we want to help build and support :)

@triptych As you wish! We already have “flavours” in the architecture with which you can package up the app with a set of extensions and configs (including app name/icon/etc).

@triptych great 😊 any question let us know!

To implement federation, all you need is to declare in your context what Activity and/or Object types you want to handle, eg for posts:
```
def federation_module,
do: [
"Note",
{"Create", "Note"},
{"Create", "Article"}
]
```

and implement these two functions:
- for outgoing: `ap_publish_activity(subject_struct, verb, object_struct)`
- for incoming: `ap_receive_activity(subject_struct, activity_json, object_json)`

@triptych