@starrwulfe Agreed and well said. Still seems like early days of federated social networks, still have much to work through. But it's great to see progress.
@Denny Thanks! I'll pose the same question I gave in another thread:
There's an interesting spin in between all this with us here on micro.blog: We're kind of our own deal here. If basing it on technologies, I believe Webmentions and RSS is at the heart of what makes this place tick. But we also speak ActivityPub and ATProto (and a few more) thanks to bridging. Does that mean we also should be sounding the alarm anytime another ship comes along that has "strangers that speak the same languages" aboard because of the unknown threat or just welcome them and ourselves into the new fold?
I'm really curious as to what most micro.bloggers think about all the dust-ups surrounding impending federation of disparate social media networks and some of the extreme "hometeam hooligan" protectionism behaviors seen in some spots. What's a good way to foster good discussions about both the technology aspects as well as the developed communities within an instance/site while trying to advocate for federation?
@starrwulfe I couldnt find my bridged account on bluesky. Have you found yours? I also havent found my personal blog on Bluesky.
@fromjason I don't t think @snarfed.org will use a "bridged accounts" type of implementation on his bridge. Right now nothing like that exists on Bluesky/ATProto. You could be seeing people like me who've changed their handles to URLs? I changed my original Bluesky account name to my website URL starrwulfe.xyz
(I think it was starrwulfe.bsky.app
or something like that) because ATProto uses your DID number as a portable identity and your handle is just a pseudonym. One DID actually supports a few handles I think but that hasn't been turned on yet.
@starrwulfe Interesting discussion! Personally I was a bit taken aback at the level of vitriol the Bridgy developer copped from Mastodon users. Personally I always felt that the syndication of public posts (which is, after all, what we're talking about) was a good thing... if people really don't want that, they're going to need to grapple with their privacy settings, because not all developers will actually be reasonable people like the Bridgy guy.
I'll admit the furore gave me second thoughts about "backfeeding" Mastodon replies onto my own site, though. Just because I think it's OK, clearly doesn't mean everyone agrees, so I decided to be more respectful of that. Now I have replies displaying as reactions, so it's required to click through to see the original comment (I don't think these people can actually object to their comments being linked to... surely). If there was a way to filter out "true" webmentions, including Micro.blog replies, to continue displaying those in full, I would, but I don't think I can with webmention.io. In the longer term, though, it makes me unsure whether I should bother continuing to display webmentions at all. What is the risk-benefit ratio? I don't really want to get attacked by people because they don't know how to change the privacy setting on their reply posts to "Unlisted", lol. And I'm also not sure how much I care any more about interactions being preserved with the posts themselves (especially cos often the display gets a bit mangled, especially with emojis). Argh, it's an annoying one.
@jayeless I’m not worried so much about it. I’m treating the comments section of my blog like a personal mastodon/bluesky/microblog instance insofar as I’m hosting the public replies to my content. At some point there should be something that periodically sends a 401 Gone status to delete posts from their remote locations Webmentions style. But for now I have no problem taking down comments for people. And I have no problem reminding them they posted a public reply to both their instance and mine in fitting with expected behavior.
Linking to the original post is a good compromise but I’m looking at being able to functionally reply inline to a comment and have it filter back to the poster, just like this one hopefully does! 🤞🏾
@fromjason @jayeless looks like things are starting to work here: fed.brid.gy/docs