Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?
General Discussion
47
Posts
8
Posters
86
Views
-
-
@evan @wjmaggos you're making a category error, Evan.
People who aren't us don't give even the tiniest shits about which protocols they're using. 5G phones happily talk to 2G phones over SS7, and the only thing anyone knows about "5G" is that it's "fast" – and they don't even know what that means.
You just said approx. "that doesn't make any sense; it's like saying that you want NG-RAN and SS7 to be mutually intelligible" and people will care about as much as someone who literally says that.
-
@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 🤷♂️
-
-
@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 @wjmaggos Webfinger isn't part of ActivityPub, it's true. It is one of the key technologies that we use as part of the stack, though, which is why we have a whole Report about WF + AP.
I don't see any reason why you couldn't add someone's BlueSky account to a Webfinger descriptor. It would be extremely useful for lookup! Do you know if any work has been done on a link-rel for BlueSky addresses?
-
so don't we have to propose visions and see which ones make the most sense, are most popular, are compatible?
what's special about social media is the boost. virality. not community or the public square. making it decentralized without algos or ads puts the people fully in control. collectively we can determine what info, ideas and art gets the most attention. I think that's the revolution @rabble talks about. I call it #DemocracyOfReach.
which protocol makes that most likely?
-
so don't we have to propose visions and see which ones make the most sense, are most popular, are compatible?
what's special about social media is the boost. virality. not community or the public square. making it decentralized without algos or ads puts the people fully in control. collectively we can determine what info, ideas and art gets the most attention. I think that's the revolution @rabble talks about. I call it #DemocracyOfReach.
which protocol makes that most likely?
-
@blaine @wjmaggos The first question asked by the poll is "Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?"
The second question is "what's preventing this".
-
@blaine @wjmaggos The first question asked by the poll is "Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?"
The second question is "what's preventing this".
@evan @wjmaggos you're reading it as a technologist – I agree with you that making atproto and activitypub literally interoperable is ... weird (although, I have argued many times that I think the two protocols will converge in functionality and scope, and also separately that lens-based translation of data structures is basically the best thing and would smooth right over the lexicon/AS differences if we had good tooling).
-
@evan @wjmaggos you're reading it as a technologist – I agree with you that making atproto and activitypub literally interoperable is ... weird (although, I have argued many times that I think the two protocols will converge in functionality and scope, and also separately that lens-based translation of data structures is basically the best thing and would smooth right over the lexicon/AS differences if we had good tooling).
@evan @wjmaggos ... but that's not what the question is asking. It's intent, and the #atproto and #activitypub in the question aren't referring to specifications, they're referring to communities.
-
@evan @wjmaggos ... but that's not what the question is asking. It's intent, and the #atproto and #activitypub in the question aren't referring to specifications, they're referring to communities.
-
Do you want Bluesky and the Fediverse to just be able to talk to each other without 'bridges', however that might happen?
Yes please!!
-
-
There are a lot of application domains where multiple competing protocols prevent growth of the industry as a whole. I'd pick Internet of Things and instant messaging as two good examples.
-
There are others where a single protocol has become the overwhelming default, and agreeing on that protocol lets us move up the stack and produce incredible value for everyone. HTTP and SMTP are two good examples.
-
-
-
@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.
-
Gli ultimi otto messaggi ricevuti dalla Federazione
-
test refederation
-
josh@2tonwaffle.social :eyes:
-
7.6.0 — Command, Sync & Go. #activityPub #wordPress
Posted into THE FEDIVERSE VS. CORPORATE SOCIAL MEDIA @the-fediverse-vs-corporate-social-media-mobileatom
-
Testing out sharing from a #Discourse forum. I haven't installed the #ActivityPub plugin yet, was just seeing how the manual way looks first.
-
This release puts speed and control right at your fingertips. Whether you’re jumping between settings, syncing followers, or handling quotes in real time, version 7.6.0 makes managing your Fediverse presence faster and more intuitive than ever.
Navigate in a FlashSay hello to the quickest way to move around your ActivityPub settings.
In preparation for WordPress 6.9, which brings the Command Palette (Cmd/Ctrl + K) to the entire wp-admin, the plugin now adds its own commands, giving you instant, keyboard-driven access to your workflows anywhere in WordPress.
Type “ActivityPub” and you’ll see context-aware commands that adapt to your site setup and user role. Whether you’re managing a blog actor or a user actor, you can open followers and following lists, check blocked actors, jump straight to your settings, or even search and edit extra fields — all without ever leaving the Command Palette.
Every command includes the ActivityPub icon for easy recognition. Just press Cmd + K or Ctrl + K, start typing, and go — it’s the smoothest way yet to pilot your Fediverse setup.
Stay in Sync Across the FediverseYour follower lists now stay accurate wherever you connect.
With support for Follower Synchronization (FEP-8fcf), the plugin automatically keeps your followers collection in step with other servers — even when things drift out of sync.If differences appear, background tasks quietly reconcile them, keeping your lists clean and consistent. The result is a smoother, more reliable experience across the entire Fediverse — no manual fixes required.
Speed When It CountsQuoted posts and follow confirmations now move at the speed of conversation.
A new immediate Accept dispatch system sends responses as soon as they’re created, instead of waiting for the next scheduled queue.
That means faster follow confirmations and quicker quote acknowledgments, making interactions feel more natural across the Fediverse. Behind the scenes, those Accept messages go straight to the right inboxes — including mentioned and replied-to users — while a scheduled backup ensures full compatibility with slower servers.
It’s a smart balance between speed and reliability, helping your posts and follows appear almost instantly.
Privacy, Your WayWant to keep your social graph private? You can now hide your followers and following lists from public view while keeping all relationships intact. Your followers still follow — they’re just hidden when you prefer a little more privacy.
Full ChangelogAddedAdd bidirectional transforms between reply and embed blocks for improved user experience.Add Command Palette integration for quick navigation to ActivityPub admin pagesAdded a new ap_object post type and taxonomies for storing and managing incoming ActivityPub objects, with updated handlersAdded a privacy option to hide followers and following lists from profiles while keeping follow relationships intact.Added a scheduled task and setting to automatically purge old inbox items, helping maintain site performance and storage control.Added fallback to trigger create handling when updates fail for missing posts or comments, ensuring objects are properly created.Added immediate dispatch for Accept activities to speed up quoted posts while keeping scheduled processing for compatibility with other instances.Added new configuration options to better manage traffic spikes when federating posts, allowing finer control over retry limits, delays, and batch pauses.Added support for FEP-8fcf follower synchronization, improving data consistency across servers with new sync headers, digest checks, and reconciliation tasks.Add LiteSpeed Cache integration to prevent ActivityPub JSON responses from being cached incorrectly. Includes automatic .htaccess rules and Site Health check to ensure proper configuration.Add quote visibility setting for Classic Editor users.Add unified attachment processor for handling ActivityPub media imports from both remote URLs and local files, with automatic media block generation and Classic Editor support.Integrate Federated Reply block with WP.com Reader’s post share functionality, allowing users to reply to ActivityPub posts directly from the Reader.ChangedAdded support for FEP-3b86 Activity Intents, extending WebFinger and REST interactions with new Create and Follow intent links.Added support for the latest NodeInfo (FEP-0151), with improved federation details, staff info, and software metadata for better ActivityPub compliance.Extended inbox support for undoing Like, Create, and Announce activities, with refactored undo logic and improved activity persistence.Improved Classic Editor integration by adding better media handling and full test coverage for attachments, permissions, and metadata.Improved delivery of public and follower activities by expanding local recipient handling to include all ActivityPub-capable users and follower collections.Improved inbox performance by batching and deduplicating activities, reducing redundant processing and improving handling during high activity periods.Improved REST API responses with smarter context handling.Improved REST collection pagination by using explicit total item counts for more accurate results.Moved default visibility handling from the server to the editor UI, ensuring consistent and flexible ActivityPub visibility settings across both block and classic editors.Prevented self-announcing by ignoring announces from the blog actor, while still processing announces from user and external actors.Refactored activity handling to support multiple recipients per activity, allowing posts and interactions to be linked to several local users at once.Refactored avatar handling into a new system that stores and manages avatars per remote actor, improving reliability and preparing for future caching support.Refactored the inbox system to use a shared inbox, storing activities once with multiple recipients for improved efficiency and reduced duplication.Reorganize integration loader and move Stream integration into dedicated folder structure.Reply posts: do not display post title before @mentions in posts that are replies to somebody elseSimplified configuration by always enabling the shared inbox and removing its separate setting, UI field, and related logic.Simplified inbox storage settings, allowing certain activities (like deletes) to be skipped to reduce unnecessary database use.Simplify follow() API return types to int|WP_Error for better predictability.Updated inbox handling to support multiple users receiving the same activity and improve overall data consistency.Updated mailer hooks to send notifications only when activities are successfully handled, preventing emails for failed events.Update plugin short description to be more user-friendly.FixedReply block now properly validates ActivityPub URLs before setting inReplyTo fieldAdded a safeguard to ensure the plugin works correctly even when no post types are selected.Added a safety check to prevent errors when resolving comment author hostnames without a valid IP address.Fixed activity processing to handle QuoteRequest and other edge cases more reliably.Fixed an issue with post content templates to ensure the correct fallback is always applied.Fixed fatal error when transformer Factory receives WP_Error objects.Fixed HTML entity encoding in extra field names when displayed on ActivityPub platformsFixed typo in example, improve quoting description.Fix Following table error message to display user input instead of empty string when webfinger lookup fails.Fix infinite recursion when storing remote actors with mentions in their biosFix local inbox delivery to use internal REST API instead of HTTP, enabling local follows and proper boost counting.Fix logic errors in Move handler: remove redundant assignment and fix variable name collision.Fix public key retrieval for GoToSocial profiles with path-based key URLs.Improved actor resolution by prioritizing blog actor detection before remote actor checks and refining home page URL handling.Improved handling of empty fields for better compatibility with Pixelfed and more consistent fallback behavior across actor names, URLs, and related data.Improved hashtag encoding for consistent formatting.Improved Jetpack integration by initializing it during the WordPress startup process.Refactored Mastodon import handling to use consistent array-based data, improving reliability and compatibility across all import scenarios.DownloadsWordPress.org: activitypub.7.6.0.zipGitHub: tag/7.6.0Thanks, Crew!Big thanks to everyone who contributed code, feedback, and testing to make this release possible. You keep ActivityPub evolving with every version.
Version 7.6.0 is now live — update today and enjoy lightning-fast navigation, smarter synchronization, and smoother federation! ❤️
-
RE: https://ishii00141.stars.ne.jp/20251108-1916-3859/
#Mastodon #ActivityPub
これを投稿した時は、日本語のハッシュタグはデコードされて表示されていたはず。
今見たら…。
これまでの投稿も全てデコードされずに表示される？
-
@gugurumbe For ActivityPub in a more general sense outside of the fediverse, POSTing to the outbox should transmit the data as-is even if not understood, and POSTing to the inbox should preserve the transmitted data as-is even if not understood. There aren't really constraints on what the outbox and inbox do internally; they can store HTTP payloads, JSON payloads, or RDF payloads (as long as they preserve the context for reserialization).
-
@gugurumbe As far as interoperability is concerned, most fediverse softwares/servers actually don't transmit activities at all! They consume the activities almost like RPC, unwrapping them for their side effects then discarding the actual activity. Fedi devs might ignore the parts they don't understand (as they SHOULD), but they also might just ignore the activity entirely -- leading to a state desync.
This lack of interoperability isn't due to the context at all, since context gets ignored.
