Wait, is @rabble saying what I think he's saying? That's there a central moderation power in BlueSky that you can't opt-out of? Even if you use an ATProto stack totally independent of BS services? Or does he just mean you can't opt-out if you're using the BS AppView, Relay, or either?
https://wedistribute.org/podcast/s2e3-rabble-from-nos-social/
#podcasts#WeDistribute#Decentered #moderation#BlueSky
@76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa
Thinking about how Rabble could get notifications of @mentions of his mastodon.social account, without me having to remember to @mention his Nostr account using a SPoF bridge. That got me wondering.
(1/2)
Is it possible to get an RSS feed of all posts that @mention you? On Mastodon or any other fediverse app.
If so, I was wondering if a Nostr or BlueSky app could follow that RSS feed, and ingest the posts to add them to your notifications there. But to do that it would have to be able to identify itself as an agent approved by the owner of that fediverse account.
Could this be a use case for the AP C2S API or a vNext?
"[Nostr] has the Zap Lightning payments and stuff ... we haven't built into our own app, because it's not a priority, and in some ways we're positioning ourselves as the non-Bitcoiner Nostr folks.
But ... easy micro-payments between users, and from users to services, gives us a economic model that's not advertising."
@rabble, 2025
https://wedistribute.org/podcast/s2e3-rabble-from-nos-social/
@76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa
(1/2)
"It's very hard to build on top of the fediverse as it is now. It's easy to build *part* of the fediverse, but you can't build a layer on top of it."
@rabble, 2025
https://wedistribute.org/podcast/s2e3-rabble-from-nos-social/
What about the FEP process? It's already documented a range of protocol extension proposals and more are in the works. If we can get reps from a critical mass of app teams, then mass adoption gets much easier.
@76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa
(2/2)
My understanding is that work done in FEPs informs the SocialCG task forces working on various aspects of social web applications. I imagine they're also watching Nostr architecture and NIPs for ideas, as well and ATProto and wherever their protocol experimentation happens.
Then the work done at SocialCG will feed into getting a charter for an updated version of ActivityPub itself. Locking in a bunch of experience from practice, and moving experimentation to new frontiers.
"That's the irony of what Blaine did when he created WebFinger. It was supposed to support multiple! It wasn't supposed to just be this is your fediverse address, it was supposed to be, here's how you find all the different account of information about me, and different things."
@rabble, 2025
https://wedistribute.org/podcast/s2e3-rabble-from-nos-social/
So ... WF is meant to facilitate something like Libravatar, where all roads lead back to a canonical profile? Hmm ...
On October 2, 2013, GNU social developer MMN-o (Mikael Nordfeldth) published a blog piece announcing that they'd rolled out a change to their WebFinger implementation, adding backwards-compatible support for the RFC7033 version;
"Plus of course the former RFC6415 (Web Host Metadata), which StatusNet supports (but only XRD format)."
For those who don't know, masrodon.social was created to federate with #GnuSocial servers.
A space for Bonfire maintainers and contributors to communicate
