Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?
General Discussion
47
Post
8
Autori
7
Visualizzazioni
-
@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
-
@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
@wjmaggos @evan @chris @blaine @anewsocial
I agree with you there! But often it's not about *how* public things are, it's more about *where* they're public. In other words, many users I've spoken to who are either not bridged or are straight-up anti-bridge have chosen that route because they don't (yet) trust the entities on the other side to have that much ownership over their data. There's also a cohort who don't want to have to depend on *us* to bridge them either.
It's a lot more complex!
-
@wjmaggos @evan @chris @blaine @anewsocial
I agree with you there! But often it's not about *how* public things are, it's more about *where* they're public. In other words, many users I've spoken to who are either not bridged or are straight-up anti-bridge have chosen that route because they don't (yet) trust the entities on the other side to have that much ownership over their data. There's also a cohort who don't want to have to depend on *us* to bridge them either.
It's a lot more complex!
@quillmatiq @evan @chris @blaine @anewsocial
they're public on the internet! screenshots?
I think the complexity is mostly about having so few people here and thinking it will stay that way. that being here is safety through obscurity. that a fedi server is a community instead of much more a portal to a possibly universal social media network. they built and maintained this place (huge kudos!) to get away, but actually made the best network not to.
they need a fork that's default opt in.
-
@quillmatiq @evan @chris @blaine @anewsocial
they're public on the internet! screenshots?
I think the complexity is mostly about having so few people here and thinking it will stay that way. that being here is safety through obscurity. that a fedi server is a community instead of much more a portal to a possibly universal social media network. they built and maintained this place (huge kudos!) to get away, but actually made the best network not to.
they need a fork that's default opt in.
@wjmaggos @evan @chris @blaine @anewsocial
Huge difference between screenshotting vs always being a part of another network and another organization's infrastructure by default.
To be clear, I don't agree with Fediverse platforms depending on a blocklists, I much prefer approve-lists, but I don't think that's a popular opinion either.
-
Sistema ha condiviso questa discussione
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@heiglandreas there is an auto-approve, but in the current version it can take some time to be synced with all platforms.
-
Congratulations! It looks really nice on Mastodon, hopefully I can add support to NodeBB soon :)
-
@pfefferle I am just not sure this is really worth the effort TBH....
When the originla author needs to approve the embedding that can take quite some time and when it is done, it's already out of my timeline....
Perhaps it'd be better to show the link to the post until it is approved?
-
RE: https://activitypub.blog/2025/10/01/7-5-0-follow-the-feed-quote-the-lead/
Version 7.5.0 of the #ActivityPub plugin for #WordPress is out, and it now lets you quote posts! 😍
-
Stick around, there are potentially dozens of implementors that do just that.
There are also dozens who don't 😅
-
The more I work on #ONI, which is basically a web components frontend for an as basic as possible #ActivityPub client to server service, the more I realize I'm just not built for JavaScript programming.
Despite having put in the hours every day for a number of months, the whole Promise paradigm just doesn't seem to click for me.
Now I'm struggling to create a throbber component (easy) while fetches happen in the background (easy) and then have it replaced (not easy) by actual content (easy).
😱 Gaaah!!!
-
@sanity most ActivityPub implementation treat the JSON-LD part as simple JSON.
-
@reiver @silverpill @helge @badrihippo
@julian@activitypub.space @julian@community.nodebb.org
@by_caballerofull ack.
We are working heavily towards a generic server and in deed it is super important what Helge decribes but anyway, we need to come together.original:
„the client APIs necessary to make this a reality haven't seen much development“But many people want this.
We should change that now and meet.
After organizing the first official Confs https://conf.tube/c/apconf_channel/videos (tons of videos) I advised the EU for DMA and DSA and then Client To Server was eye-opening for them.My last Talks (e.g. together with funder at fediday) and those after had been in German but when we showed the AP Client2Server boardgame at Public Spaces it was english https://video.publicspaces.net/w/9USsJ37cHVy4tY9Pn7DX2X :)
So, if anyone is interested in a nice dev. meeting about this topic apart from the new taskforces, please comment here !
