Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?
General Discussion
47
Posts
8
Posters
1.5k
Views
-
-
-
@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.
-
@evan @julian @wjmaggos what would you consider to be the "application domain" of HTTP, and what needs to be built above it? ironically, i think if you look at the OSI model, then HTTP is already at the uppermost "layer 7", the application layer -- and attempts to build networks on top of HTTP are in effect virtualizing lower layers! so instead of a virtual 3-7 on top of HTTP's 7, why not use HTTP's 7 directly? how many nested virtualized app layers do we need?
-
@evan @julian @wjmaggos what would you consider to be the "application domain" of HTTP, and what needs to be built above it? ironically, i think if you look at the OSI model, then HTTP is already at the uppermost "layer 7", the application layer -- and attempts to build networks on top of HTTP are in effect virtualizing lower layers! so instead of a virtual 3-7 on top of HTTP's 7, why not use HTTP's 7 directly? how many nested virtualized app layers do we need?
-
-
@trwnh @julian @wjmaggos I am taking Computer Networks right now, and I asked the very same question. If we have application-layer protocols, what do we call the things like SOAP or ActivityPub that work on top of those protocols. The answer I got was that those are also layer 7. Once you get to layer 7, it's just 7 all the way up. Inverted turtle structure!
-
@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.
@evan @wjmaggos @chris @blaine @anewsocial
Appreciate all the kind words in the thread! That said, I still strongly believe opt-in is a feature, not a bug. The right solution isn't to force people onto networks they don't want to be a part of; it's to clean up the rough edges of unbridged interactions and content so it makes less of a difference.
-
@evan @wjmaggos @chris @blaine @anewsocial
Appreciate all the kind words in the thread! That said, I still strongly believe opt-in is a feature, not a bug. The right solution isn't to force people onto networks they don't want to be a part of; it's to clean up the rough edges of unbridged interactions and content so it makes less of a difference.
@evan @wjmaggos @chris @blaine @anewsocial
I understand the instinct of "make these work together", but there are technical and cultural differences that make it more than just two standards talking to each other. A couple of simple examples are "I don't want to be in a public, auditable firehose" or "I had a bad experience there, I don't trust them with my safety."
-
@evan @wjmaggos @chris @blaine @anewsocial
I understand the instinct of "make these work together", but there are technical and cultural differences that make it more than just two standards talking to each other. A couple of simple examples are "I don't want to be in a public, auditable firehose" or "I had a bad experience there, I don't trust them with my safety."
@quillmatiq @evan @chris @blaine @anewsocial
I understand if you don't want to have the conversation but these are public systems like blogging with your email address available, we just don't think of them like that. it's old school twitter, not even your network of friends and family on facebook. not having algos/ads doesn't mean everything isn't boostable to the world by default. maybe people want to use something designed to be inherently private, but that's not fedi etc. IMHO
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@developerjustin yup, itโs been federating for a couple of weeks and it seems to be picking up a bit of steam!
-
-
@evanprodromou@evanp.me This is amazing to hear, and I wish you all the best!
It goes without saying that I expect great things from you and from AP starting next year ๐๐
-
@evanprodromou congratulations, and thank you!
-
@evanprodromou Congratulations! This is excellent news.
I'm very much looking forward to what you and SWF will achieve.
-
@evanprodromou Great news! The Open Social Web will get even better. 2026 will be an excellent year.
-
@evanprodromou love this and happy to see you leading the charge!
-
@evanprodromou Congratulations! ๐ฅณ
