Jack Dorsey skipped ActivityPub, built AtProto, lost Twitter, funded Bluesky, watched it become a company with VCs and a board, said it was "repeating all the mistakes," left, and now funds Nostr.
-
@quillmatiq @dansup I know you and I appreciate your work.
Coalitions exist when different factions and players share some common goals. But they don't have to share *all* the same goals to work together.
I think there's a good case to be made that the ATProto community and the Fediverse can be a coalition to work together on the Open Social Web.
That doesn't mean we can't talk about our differences, or advocate for our own protocols and technologies.
@quillmatiq @dansup And, absolutely, I'm really concerned about how we get more of those companies re-engaged.
It wasn't the only factor, but having multiple protocols in the space makes it more likely that implementers take a wait-and-see approach and don't use either.
-
@evan @dansup @quillmatiq Evan, perhaps spend some time introspecting why ActivityPub didn't get more adoption and why developers love AT Protocol.
@thisismissem @dansup @quillmatiq This is my number one area of interest!
-
@evan @dansup What's hurt it more is not working together on a unified strategy and putting up walls every time there's a chance to do so.
There are folks on the atproto side who have shown an intent to bridge with services like Pixelfed and Loops, *including* adding the logo on the posts to help promote services. We can either move together, or we can continue to push each other away and fall to trillion-dollar companies building their own ecosystems, some of whom the Fedi bet the farm on.
@quillmatiq I like your vision of peace and collaboration. But when there is a working protocol and a team builds a completely new one that is not compatible with the existing. Who is building a wall? When I want to build a new "open social web" service or client, how many protocols should I need to implement? This is not about if mastodon or pixelfed could be Atproto compatible, it's not about services it's about the protocol. @evan @dansup
-
@evan @dansup The number of developers and communities who've been pushed out of the Fedi because of this elitist mentality should be alarming to any builder in this space. Are we ever going to learn to do better, or are we going to continue pushing more people away?
The vibes aren't good, Evan, and I really hope you're aware of that, because vibes make or break a community.
@quillmatiq @dansup I don't have a lot of examples of this, honestly.
I can think of a few great ActivityPub implementers who dual-stack, like micro.blog and Friendica, but I don't know of ones that stopped supporting ActivityPub because someone said Bluesky was started by a billionaire.
I think it's *great* when servers and clients support AP, regardless of what other protocols or services they support.
-
@quillmatiq @dansup @thisismissem Friend, what's your goal here?
@evan What is the goal of calling out the history of atproto when the majority of the current community, including Bluesky, wants to collaborate? I'm trying to show that throwing stones is unproductive because there are stones lying everywhere.
-
@quillmatiq @dansup I don't have a lot of examples of this, honestly.
I can think of a few great ActivityPub implementers who dual-stack, like micro.blog and Friendica, but I don't know of ones that stopped supporting ActivityPub because someone said Bluesky was started by a billionaire.
I think it's *great* when servers and clients support AP, regardless of what other protocols or services they support.
@quillmatiq @dansup I do know how toxic the response was to Bridgy Fed when Ryan first announced the Bluesky bridge, and I think his ability to weather that storm will go down as one of the most heroic efforts in the history of the social web.
-
@quillmatiq @dansup I do know how toxic the response was to Bridgy Fed when Ryan first announced the Bluesky bridge, and I think his ability to weather that storm will go down as one of the most heroic efforts in the history of the social web.
@evan @dansup The storm has not died down, Evan. The hate doesn't just flow to Ryan, it also flows to anyone involved in that work or promotes it. There is a cultural problem that large voices in the ActivityPub space need to reckon with, and I think that work should've started months ago, if not years ago.
-
@evan @dansup The storm has not died down, Evan. The hate doesn't just flow to Ryan, it also flows to anyone involved in that work or promotes it. There is a cultural problem that large voices in the ActivityPub space need to reckon with, and I think that work should've started months ago, if not years ago.
-
@quillmatiq @dansup I don't have a lot of examples of this, honestly.
I can think of a few great ActivityPub implementers who dual-stack, like micro.blog and Friendica, but I don't know of ones that stopped supporting ActivityPub because someone said Bluesky was started by a billionaire.
I think it's *great* when servers and clients support AP, regardless of what other protocols or services they support.
@evan It's not about the comments around billionaires, I'm talking about a culture that pushes communities out, even ones that want to collaborate - both technical and non-technical. I really hope you're aware of the numerous instances of this, it's really important if you want to make this space welcoming.
-
@thisismissem @dansup @quillmatiq This is my number one area of interest!
@evan @dansup @quillmatiq interest is great and all, but understanding the social and power dynamics at play is more important.
Every time some leader of an ActivityPub project goes on a tirade against another protocol or project, all it does is hurt the entire ecosystem. It prevents productive partnerships, it creates friction and fights.
We've seen this countless times, and meanwhile majority of ActivityPub applications are not striving for ActivityPub interoperability, but for Mastodon interoperability.
There is so much power centralization in ActivityPub it's not funny, let's not forget that the protocol was left to rot by the W3C for the longest time, when it could've continued on-wards. The amount of infighting and politics here drives people away.
I've talked with folks who have really great ideas, and I've been like "come bring this to a standards meeting, this is really cool" and the response time and again is "I don't want to be involved with those people", because they've seen countless negative interactions.
Meanwhile, in AT Protocol, it's extremely common place to get different application developers and organisations to come together to standardise things, the best example is https://standard.site — I'm also helping a few developers work on interoperability for other things within the Atmosphere, because they realise that they're stronger together.
In ActivityPub there's been constant division "this software is better than that software", and petty little fights about "this isn't really activitypub because it doesn't do what mastodon does, so it doesn't interoperate fully" — Dan was the target of one such hit piece.
The office hours that the bluesky team run every two weeks? They basically entirely focus on sharing and promoting the cool work by other people in the ecosystem, here's some notes from the latest: https://bsky.app/profile/thisismissem.social/post/3mere5l7knk2n
I've mentioned it before, but I've stopped actively contributing to Mastodon because the lack of respect that they show other contributors is so dire that it's not financially viable for me to contribute.
-
@evan What is the goal of calling out the history of atproto when the majority of the current community, including Bluesky, wants to collaborate? I'm trying to show that throwing stones is unproductive because there are stones lying everywhere.
@quillmatiq @dansup I think you do great work in providing a literal and organisational bridge between those two communities.
I'm wondering, how do we get to a point where we actually feel like we're on the same side? And what side is that, even? Because it doesn't feel that way for anyone.
-
@evan @dansup @quillmatiq interest is great and all, but understanding the social and power dynamics at play is more important.
Every time some leader of an ActivityPub project goes on a tirade against another protocol or project, all it does is hurt the entire ecosystem. It prevents productive partnerships, it creates friction and fights.
We've seen this countless times, and meanwhile majority of ActivityPub applications are not striving for ActivityPub interoperability, but for Mastodon interoperability.
There is so much power centralization in ActivityPub it's not funny, let's not forget that the protocol was left to rot by the W3C for the longest time, when it could've continued on-wards. The amount of infighting and politics here drives people away.
I've talked with folks who have really great ideas, and I've been like "come bring this to a standards meeting, this is really cool" and the response time and again is "I don't want to be involved with those people", because they've seen countless negative interactions.
Meanwhile, in AT Protocol, it's extremely common place to get different application developers and organisations to come together to standardise things, the best example is https://standard.site — I'm also helping a few developers work on interoperability for other things within the Atmosphere, because they realise that they're stronger together.
In ActivityPub there's been constant division "this software is better than that software", and petty little fights about "this isn't really activitypub because it doesn't do what mastodon does, so it doesn't interoperate fully" — Dan was the target of one such hit piece.
The office hours that the bluesky team run every two weeks? They basically entirely focus on sharing and promoting the cool work by other people in the ecosystem, here's some notes from the latest: https://bsky.app/profile/thisismissem.social/post/3mere5l7knk2n
I've mentioned it before, but I've stopped actively contributing to Mastodon because the lack of respect that they show other contributors is so dire that it's not financially viable for me to contribute.
@thisismissem @dansup @quillmatiq Are you working on ATProto projects now? EDIT: I reread, saw that you are. I'm glad to hear that!
-
@quillmatiq @dansup I think you do great work in providing a literal and organisational bridge between those two communities.
I'm wondering, how do we get to a point where we actually feel like we're on the same side? And what side is that, even? Because it doesn't feel that way for anyone.
@evan It feels that way every time I talk to atproto developers, and some Fedi ones too (I was just on a call with WordPress, Leaflet, Offprint, and pckt last week about longform bridging). It feels that way when I have face-to-face 1-1s with atproto short-form apps that want to bridge with cross-promotion in tow. I can go on.
It's posts and threads like this that get visibility and skew the conversation in an unproductive direction.
-
@thisismissem @dansup @quillmatiq Are you working on ATProto projects now? EDIT: I reread, saw that you are. I'm glad to hear that!
@evan @dansup @quillmatiq yes, I am actively working on several AT Protocol projects.
-
@dansup Nostr is a good idea, unfortunately nobody is talking to each other and everyone wants funding from the same wallet.
-
@evan It feels that way every time I talk to atproto developers, and some Fedi ones too (I was just on a call with WordPress, Leaflet, Offprint, and pckt last week about longform bridging). It feels that way when I have face-to-face 1-1s with atproto short-form apps that want to bridge with cross-promotion in tow. I can go on.
It's posts and threads like this that get visibility and skew the conversation in an unproductive direction.
@quillmatiq @dansup That's great! I'm glad to hear that you're having some positive interactions where people have a sense of shared goals.
What's making that work well? How do we do it better?
I hope the upcoming Fediforum conference will be another chance to have that kind of conversation.
-
@dansup @quillmatiq while I agree on your take on bluesky, the existence of Blacksky and others show that atproto is a viable decentralized protocol and is beyond the control of bluesky, the company. Im hopeful there will be more bridges that will connect activitypub to atproto like Bridgyfed or services that have interoperability built in like Wafrn
@adamtewodros @dansup @quillmatiq
blacksky should build on activitypub
if they build on atproto, ok
good luck to them
but they seem to be choosing a sinking ship
-
@quillmatiq @dansup @thisismissem @evan
How many Anuj?
And, what constitutes an AT Proto "independent service"?
@mastodonmigration @quillmatiq @dansup @thisismissem @evan I'm curious to know as well. I'm not dead-set against ATproto, and I like some of their ideas on paper, but i only really know of one public full-stack reimplementation that could exist if Bsky disappeared overnight - BlackSky. But last I read (admittedly been a minute), they're still dependent on Bsky for the plc directory, right? I'd like to be better informed if this is no longer the case, or if there are other fully independent full stack implementations!
-
@quillmatiq @dansup That's great! I'm glad to hear that you're having some positive interactions where people have a sense of shared goals.
What's making that work well? How do we do it better?
I hope the upcoming Fediforum conference will be another chance to have that kind of conversation.
@evan What's making it work is not acting as if a specific standard or technology is the only choice everyone has to bet on or is some ideological choice. It's about opening doors, building bridges, and seeing where we can bring people together. It's not that complicated, it's just kindness and openness.
-
@evan What's making it work is not acting as if a specific standard or technology is the only choice everyone has to bet on or is some ideological choice. It's about opening doors, building bridges, and seeing where we can bring people together. It's not that complicated, it's just kindness and openness.
@quillmatiq @dansup I agree. Like I said, coalitions don't always share 100% the same goals and values, but we can still work together towards what we do have in common.
