@fediforum@mastodon.social

Non-Centralized Social Media Protocols: When to Use What and How They Work Together?

/2024-09/session/1-a/

Convener: Johannes Ernst, Dazzle Labs (@j12t@j12t.social)

Participants who chose to record their names here:

Notes

A broad discussion with implementors of the above protocols.

  • How people decide which protocol to implement?

  • Who maintains the protocol life-cycle? W3C was an important factor for Threads.

  • Are we building one Federated Network? Will users have to keep choosing what “protocol” will they use?

    • Well, the users go mainly where their people are…
    • Best case scenario: let us focus on creating apps that provide integration…
    • It seems that ActivityPub is getting to be the interop protocol…
    • It is an exciting time for experimentation…
    • it is super valuable that we are not being “pushed” to be under the same “protocol”…

Difficulties:

  • Bridges and moderation.

  • Bluesky approach: separate moderation from the architecture of the network.

  • Helps with having teams focused on each moderation aspect.

  • Proposition is clients/brands are the ones people are installing and they should be able to make the decisions of moderation approaches… they will likely need to hire services…

  • JL: broght up how emails do things… the platform provides SPAM and users can tune them up…

  • What people seem to need:

    • Defaults that cover basics.

    • Who said what about X (that is the labeling system in BlueSky tries to implement).

    • How can a user understand any of this? Even if an app posts into multiple networks, the comments/reactions will not merge.

  • RB: “It’s a good point “copying” posts between networks vs. natively understanding each network. As an example, when Micro.blog copies posts to Bluesky, it also automatically checks Bluesky for replies so you can have conversations back and forth… But that is a lot of work for every platform to implement.