• 25 Posts
  • 62 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle



  • AT protocol doesn’t federate the way ActivityPub does. There are separations between how your dat is stored, how it is aggregated, how it is filtered, and how it is displayed. Each part can be hosted separately and federate differently with separate instances of each part. The aggregation part is the thing that is most critical and there are probably some limited independent instances of that, but BlueSky has offered no support in facilitating this beyond making their peices AT Protocol compliant. You van take what BlueSky built and try to run your own instance of the aggregation service but they provide no documentation or support. You could also build your own, but that’s difficult and I don’t think anyone is trying.

    So it is federated, but pretty much no one is interested in doing the work to federate with the primary infrastructure.









  • I’m not here to score points. I’m expressing my thoughts and reservations about the article. I’m not even taking much of a position on what developers should do. It’s more of an exploration of the landscape.

    Unfortunately, skipping past a legitimate point doesn’t address the point which remains unresolved. It’s a nice rhetorical trick though. I’d rather discuss the point. (Even though others have had discussions, that doesn’t help me understand and learn.) There’s no urgency for me to reach a conclusion, so a bit of rehashing of “tired” perspectives isn’t offensive to me.

    Reasonable doesn’t always mean appropriate or best for the situation. It doesn’t always lead to good or better outcomes. Shutting down and dismissing legitimate concerns is not a good way to build a consensus and and will often lead to adverse outcomes. It is ironic that this person’s approach is making the same mistakes they are trying to warn against.

    There’s a clear conflict that literally can’t be ignored. It must be considered by all participants, else those participants will be unexpectedly unsatisfied with the outcomes.





  • They all seem reasonable suggestions:

    • Consent matters, even for public posts
    • Get broad feedback before launching – and listen to it
    • Honor existing opt-in and opt-out mechanisms
    • Include an additional opt-in mechanism for your service if it’s not just a search engine or profile discovery (or something very close to them)
    • Make sure to communicate that you’re taking an opt-in approach and honoring existing mechanisms
    • DON’T say the things that developers who ignore consent typically say
    • Be extra careful if you’re a cis guy
    • Look at opt-in as an opportunity for a potential competitive advantage

    I’m conflicted over the fact that using ActivitiyPub necessarily implies consent for other people to collect the data you send through it. It seems that many people using ActivitiyPub connected services want something different than ActivitiyPub or different default settings on many ActivityPub services.