@quillmatiq@mastodon.social @quillmatiq@threads.net @quillmatiq.com

I'll also say, it grinds my gears when people talk about downsides of the ActivityPub ecosystem, especially when they weren't designed in. It's hard to move from one server to another. It's hard to build a new kind of application. It's hard to bring your own domain to an account on someone else's server.

@evan love this 🤝🏼

@quillmatiq@mastodon.social @quillmatiq@threads.net @quillmatiq.com I'd also say, ATproto exists and isn't going away. So, what's best for everyone is for it to be as open and decentralised as it can be. That's why I went to IETF to speak out in favour of an ATproto working group.

@quillmatiq@mastodon.social @quillmatiq@threads.net @quillmatiq.com

I think if I were trying to thread the needle, I might say this: I think that ActivityPub provides the best developer platform for people interested in building on the social web. But I'd rather people build on ATproto than not build at all! And if they do build on ATproto, staying bridgeable, using shared lexicons, and other practices can make it easier for all of us to feel like we're in one big network.

@evan I love the work you do, too.

I'd rather see the community focus on demonstrating the ways AP is better rather than talk about it in the lens of why other things are worse, especially when cooperation is possible both socially and technically.

I'd argue mass bridging would actually boast the benefits of each much more to people, but that's a whole other conversation.

@quillmatiq sorry, I meant, it's *my* assumption! "If we only had one protocol, all those developers would be working together, generating value in one ecosystem." It's probably not true.

@evan Ah yes, that is a very sensible approach I should probably adopt as well. One more [last] domain name to rule them all? :)

@quillmatiq@mastodon.social @quillmatiq@threads.net @quillmatiq.com

I love the work I do, advocating for the ActivityPub network, building software and services to make it work better, and developing our protocol and extensions.

@evan that's not my assumption! In fact, one of the main reasons I care so deeply about bridging is to let people who build choose the technology they're comfortable with/excited about, and helping tap them into other networks. It's why we're getting more focused on bridging more lexicons, and why everyone I spoke with at AtmosphereConf is ready to bridge their lexicons where it makes sense.

@quillmatiq@mastodon.social @quillmatiq@threads.net @quillmatiq.com

I think it's also unlikely that the current ATproto developer community is going to disappear just because ActivityPub advocates point out that governance story on our ecosystem is much better, and the independence of our nodes is demonstrably higher.