Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?
-
-
-
-
-
-
@julian @wjmaggos I also think that the difference between open protocols and proprietary protocols matters. Open protocols level the playing field, while commercial protocols concentrate power in one entity. Other players in the space have an incentive to focus on open alternatives to commercial protocols, and sometimes this can begin convergence. Having active or dominant commercial protocols in a space is a source of instability.
-
@julian @wjmaggos I also think that the difference between open protocols and proprietary protocols matters. Open protocols level the playing field, while commercial protocols concentrate power in one entity. Other players in the space have an incentive to focus on open alternatives to commercial protocols, and sometimes this can begin convergence. Having active or dominant commercial protocols in a space is a source of instability.
-
-
@evan @wjmaggos it's not my message. My message to technologists was "the key piece of interop for humans is identity" and I was told "webfinger isn't part of activitypub" and "domain names are how we do identity on the internet" (despite the idea that paying $25/year to get to manage DNS isn't an end-user-achievable thing in the world we live in) and after years of this I gave up. It makes me sad that Bluesky went with domain names because consistent format really matters, but 🤷♂️
@blaine @evan @wjmaggos on a tangent to this, it took me 10 minutes each to get a working instances of OSSN & Piwogo up on my website hosted on Bluehost servers, using Softaculous scripts, simply because they can be installed in directories on existing domains. Meanwhile, I have failed to date in self hosting Fediverse instances, limited by needing to register yet another domain name (which I've done anyway), and not figuring out secure port forwarding for a home Yunohost server.
-
@julian @wjmaggos I don't know if there is a good book about how SMTP won, by the way. It would be a great read. In hindsight, it seems inevitable, but in the late 1980s and early 1990s it was far from a sure thing. There were dozens of commercial network email protocols already in use, and a few interoperation standards, like X.400.
-
-
@julian @wjmaggos I don't know if there is a good book about how SMTP won, by the way. It would be a great read. In hindsight, it seems inevitable, but in the late 1980s and early 1990s it was far from a sure thing. There were dozens of commercial network email protocols already in use, and a few interoperation standards, like X.400.
-
@blaine @evan @wjmaggos on a tangent to this, it took me 10 minutes each to get a working instances of OSSN & Piwogo up on my website hosted on Bluehost servers, using Softaculous scripts, simply because they can be installed in directories on existing domains. Meanwhile, I have failed to date in self hosting Fediverse instances, limited by needing to register yet another domain name (which I've done anyway), and not figuring out secure port forwarding for a home Yunohost server.
@TotalSonic @blaine @wjmaggos you're right; that is a tangent.
-
@chris @blaine @wjmaggos it's funny that you say "without bridges" and "however that may happen" in the same breath. If we don't care how it happens, why rule out one particularly powerful technique for interoperability?
BridgyFed works GREAT. It's fucking amazing. Is there room for improvement? Absolutely. But it's a really good service.
-
@chris @blaine @wjmaggos it's funny that you say "without bridges" and "however that may happen" in the same breath. If we don't care how it happens, why rule out one particularly powerful technique for interoperability?
BridgyFed works GREAT. It's fucking amazing. Is there room for improvement? Absolutely. But it's a really good service.
-
@wjmaggos @chris @blaine one of my big problems with it too. I think @anewsocial are aware of that limitation and are working on some solutions.