Mayel de Borniol
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee
  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Bonfire federated groups - NLnet grant application ### Abstract: Can you explain the whole project and its expected outcome(s). (1200) Project: Bonfire federated groups The fediverse enabled the sprouting of a new wave of online communities, that chose it as their home for its promise of an internet free from the monopoly of profit-driven centralised social media platforms. The fediverse relies on the core tenet to build a more inclusive, open and safer web for anyone to join, interact and feel part of in a meaningful way, according to each user's preferences and needs. True to this concept, we believe that it's crucial to move beyond the limits of "each instance is (sort of) a community"; by empowering users to create, join and manage federated groups across instances, with their own set of rules and customisable governance. Federated groups on Bonfire will leverage the flexible foundation we've recently released, circles and boundaries: https://bonfirenetworks.org/posts/introducing_boundaries/ Using those building blocks we will ensure that groups have the possibility to define a fine grained set of roles and permissions, with the possibility for each group to define a multitude of roles that fit with how they want to manage membership and participation, and distribute power and responsibility. Groups will be a crucial feature in the fediverse and we will ensure that our implementation will follow open standards and document all implementation details so that it will be compatible with Mastodon's ongoing efforts, and any other apps that implement groups. ## Have you been involved with projects or organisations relevant to this project before? And if so, can you tell us a bit about your contributions? - Recently the bonfire team attended a Sociocracy (a form of decentralised governance) facilitation course, organized by the Sociocracy for All foundation, and from there we've started a series of meetings with other fediverse participants to brainstorm about the intersection of sociocracy and the fediverse (notes here: https://notes.zo.team/fediverse-sociocracy-meeting). - We've collaborated with the Co-op Cloud team to test their tool "abra", and we wrote a bonfire recipe (https://recipes.coopcloud.tech/bonfire) to radically ease the deployment of bonfire instances using cooperative or self-hosted infrastructures. - As part of our work supported by the Culture of Solidarity fund, we've built the circles and boundaries extension (https://github.com/bonfire-networks/bonfire_boundaries). These are the foundational building blocks upon which we will develop groups, roles, and many other features in a flexible and safe way. ## Explain what the requested budget will be used for? Does the project have other funding sources, both past and present? (If you want, you can in addition attach a budget at the bottom of the form) We will use the 15k to fund the development of the following milestones (which will overlap over about 3-4 months total): - **Group UX research & testing** (1mo) - We will co-produce with users a list of requirements and mockups that will guide us through the development of groups. Research will be done through user interviews and discussion with our community on the bonfire platform. - **Group design & development** (2mo) - We will implement the features defined by the Group UX research & testing milestone. We will release groups on the bonfire playground instance, to test and iterate together with our community. - **Group federation implementation and testing with other relevant platforms** (3mo) - We will add federation support for groups, so that our implementation will be compatible with other efforts (such as mastodon, mobilizon, lemmy, guppe), while preserving the flexibility we've implemented in bonfire. - **Communication and documentation** (3mo) - During the duration of the development, we will publish blogposts and write docs to share our progresses and to involve the community into our work. ## Compare your own project with existing or historical efforts. - Mastodon, Mobilizon, Peertube, Lemmy, Pixelfed are some of the fediverse apps who are at the early stages of implementing groups and which we will coordinate with to establish and test interoperation. - Facebook Groups is the first choice for lots of virtual or local groups. They're easy to setup and have the advantage of network effects. But they dont offer a comprehensive set of governance tools, and they're dependent on centralised and profit-driven facebook policies and data management. - Tribe / MightyNetworks / Circle / Amity / Hivebrite are ad-hoc community platforms and most of them include the possibility to create groups. They typically have the value proposition of monetising specific niches, offering group admins features to charge for membership and only a subset of permissions to implement the most basic roles. They are all proprietary SaaS services, with prices ranging from $40 to $600 per month (while others charge per-user). - Wordpress's BuddyPress / Open Social (Drupal-based) are modular (open source or open core SaaS) frameworks to build and manage online or local communities. Their main limitation is their centralisation. Each community is a silos and cannot connect with the others; each user is forced to create and monitor as many accounts and feeds as the amount of communities they belong to. - Telegram / Whatsapp / Signal / Element / etc: Chat-base groups are the most used alternative. They have the lowest UX entry barriers and they are ephemeral enough to setup, use and delete in few clicks. But chat groups are mostly limited to real time or linear text-based conversation and hardly allow users to perform other kind of activities, such us creating events, publishing offers/needs, coordinating tasks, etc. ## What are significant technical challenges you expect to solve during the project, if any?) We will implement groups so that users can granularly configure roles and permissions, invite users and moderate the content published, all while ensuring that bonfire groups can interoperate with other fediverse efforts. We will foster discussions to agree on clear and documented specs so all platforms can implement compatible federated groups and roles. ## Describe the ecosystem of the project, and how you will engage with relevant actors and promote the outcomes? We are using our playground instance (https://playground.bonfire.cafe/local) to co-design features and spot bugs together with our community. We will involve our community from the very first stage: from brainstorming the most relevant features together, sharing early mockups, spotting bugs on the released features, etc. We're partnering with UXDI, the biggest "user experience and inclusive design" course in south america, helping to mentor a team of design students, that are using the bonfire platform as a case study, and helping to improve the user experience and accessibility of our main features. We will keep a monthly blog diary to share the relevant news and work done.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully