Mastodon's cross-instance following is clunky. I propose a solution using the web+follow URL scheme, like mailto, to streamline following users on ActivityPub platforms. A user's home instance registers as a handler for web+follow. Clicking a web+follow link opens the home instance, redirecting to a /follow request on the target instance. This page uses a meta refresh tag to redirect to /resolve-app, which redirects back to web+follow: with the user's ID. This triggers the registered handler (if available), creating a seamless follow experience within the user's preferred app. If no handler is installed, the user remains on the target instance's follow page, preserving existing functionality.
ActivityPub
Connect your site to the Open Social Web and let millions of users follow, share, and interact with your content from Mastodon, Pixelfed, and more.
NEAR Intents | Simplifying Web3 Interactions
NEAR Intents let users and AI agents define what they want to do—NEAR handles the rest. A new framework for seamless, multichain execution without complexity, powered by solvers and Chain Signatures.
ActivityPub Client API: A Way Forward | Steve Bate
The ActivityPub Client-to-Server (C2S) protocol was envisioned as a cornerstone of the decentralized social web, along with the Server-to-Server (S2S) protocol. Standardized by the W3C in 2018, C2S defines how user-facing applications, such as mobile apps or web clients, and bots should interact with social servers using Activity Streams 2.0 and JSON-LD. In theory, it ... Read more
If This Then AT:// - Automation Platform for AT Protocol
Automate your Bluesky presence with powerful visual blueprints. Connect events to actions, schedule posts, and integrate with webhooks.
ActivityPub
ActivityPub is a protocol and open standard for decentralized social networking. It provides a client-to-server (C2S) API for creating and modifying content, as well as a federated server-to-server (S2S) protocol for delivering notifications and content to other servers. ActivityPub is the defining standard of the Fediverse, a decentralised social network of various social interaction models, and content types, which consists of independently managed instances of software such as Mastodon, Pixelfed and PeerTube, among others.
Protocol Handler Registration via Browser Extensions – make everything intensely
Custom URL schemes have traditionally served as an integration bridge between the browser and external capabilities. Schemes such as mailto: and tel: allow navigation to trigger actions beyond ordinary HTTP resource retrieval. The HTML Standard formalizes this mechanism through the Custom Scheme Handlers API, which enables websites to register themselves as handlers for specific URL schemes.
Lqm1/X-ActivityPub-Bridge
Bridge to allow X (Twitter) users and posts to be viewed externally via the ActivityPub protocol
Web dev is fun again with ATproto · Web Dev Challenge S3.E4
Followgraph for Mastodon
Find people to follow on Mastodon by expanding your follow graph.
Why ActivityPub is the future
We often tout things like “Mastodon is based on open web protocols” as one of its advantages. I want to elaborate why exactly that’s a good thing.
AT Intents proposal
I work on Skyreader and have recently been trying to improve the cross-app sharing experience (e.g. “send this article to semble/margin/etc”). The problem I’m running into is each app integration requires a bespoke implementation and the “save to” UX starts to get cluttered as the number of integrations increases. What would be nice is if the atproto ecosystem had a standard and generic way for cross-app sharing that was usage aware so you could filter by apps you actually used. So I’ve put tog...
ActivityPub
The ActivityPub protocol is a decentralized social networking protocol based upon the [ActivityStreams] 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and content.
ActivityPub
The ActivityPub protocol is a decentralized social networking protocol based upon the [ActivityStreams] 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and content.
Thinking about rebuilding @val.town / @smallweb.run on top of atproto, with an architecture inspired by @tangled.org. Every user can bring it's own runner, but the there is a federated appview for social stuffs (likes, follow, ect...).
Shipped a new thing on @airglow.run: social graph sync 🔄 Pick the apps you use (Bluesky, @tangled.org, @sifa.id, @grain.social, @semble.so), turn it on, and your follows stay identical everywhere. Follow someone on one app, you follow them on the others too
inspired by some project i saw someone post about this morning (i forgor, sorry), ever wondered what post made you follow someone? view interactions near your follow time at follow-context.cee.wtf
