Tag: atprotocol

🚀 Decentralised "Strava" on AT Protocol?

Thinking about building a "Strava"-like app on AT Protocol, where users store their activities (runs, rides, etc.) in their own PDS

Leaflet, Pckt, Offprint, And The Rest Of The Atproto-verse Of Platforms

The workings of all these platforms running atproto is a headscratcher.

W Social Isn't New. It Isn't Truly European. It Isn't Even Theirs.

Another rant on this “European” alternative

Permissioned Data Shapes: Notifications

A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.

How to design a Lexicon Community lexicon

Publishing and resolution

How community.lexicon.* NSIDs resolve: DNS to DID to schema record. Plus how to verify the chain and pin an offline copy your SDK can trust.

Reintroducing Lexicon Community

Nobody Cares About Your Protocol

And That's the Problem

Some considerations on the AT Protocol

If you’ve been following the discussion around Bluesky even just superficially, you’ll have heard this mantra repeated: “your data is yours, you can take it with you whenever you want, no lock-in”. It’s a wonderful promise that is also, at least for now, only half true.

hi gay

hey! look! listen!

inkwell-website

Landing page and OAuth metadata host for the Inkwell iOS app.

zola-standard-site

A Zola theme with standard.site support — 96 colour themes, syntax highlighting, and AT Protocol verification.

inkwell

A native SwiftUI reader and writer for the Standard.site publishing ecosystem on AT Protocol.

inkwell-android

Experimental Android client for the Standard.site publishing ecosystem on AT Protocol — Jetpack Compose + Material 3.

faol-website

Website for faol, a digital person. Published with Sequoia.

In the beginning there was the protocol

A primer for why I think AT Protocol is the future of decentralized publishing

Un deuxième test de ATmosphere

Florian a testé avec succès le plugin WordPress ATmosphere pour s’assurer qu’il fonctionne bien avec le protocole AT. Après avoir vérifié la configuration de l’extension pour BlueSky, il a confirmé que tout était en ordre et que la connexion était établie. Ce petit billet marque une étape importante dans l’intégration de son site avec le réseau social décentralisé.

atpkt

Professional-grade modular AT Protocol SDK for Kotlin.

#oneaday Day 722: Entering the ATmosphere

I read yesterday that several blogging platforms are integrating the "AT protocol" or whatever it's called that powers services like Bluesky and the like, and one of those was WordPress. So today's post is primarily a big ol' test to see whether or not that functionality, implemented via the ATmosphere plugin, actually works, and whether...

Social Sync v0.5.0

Rebranded to Social Sync, implemented new consent-based preferences system and improved security.

Moon Tracker Rust Rewrite

Rewrote Moon Tracker in Rust using atrium-rs, adding multi-source API with local fallback and Ollama LLM generation.

Here's a little test

Trying out Leaflet.

Atmosphère ! Atmosphère ! Est-ce que j’expérimente ?

Après ActivityPub installé ici j'expérimente l' extension ATmosphere 1.0.0 qui permet de diffuser en direction de Bluesky et de recevoir les interactions sur les posts dans WordPress

Permissioned Data Diary 5: What’s in a Name?

In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.

Payments on Protocol

atprotofans.com was a proof of concept for payments on ATProtocol built at Graze Social. This post is about what we built, why proof of payment on protocol matters, and what it makes possible.

Graze Social and the IETF

Graze Social sponsored my first in-person IETF meeting in Montreal last November. This post is about what it was like to be there and why standards participation matters for small companies.

Astro6.1

Astro6.1がでていた

If This Then AT: Automation on Protocol

IFTTA is an automation platform built on ATProtocol at Graze Social. It started as a hack-day idea and became a working system for event processing on protocol.

Building AIP: An ATProtocol Authorization Gateway

OAuth is the first challenge developers face in the atmosphere. This post is about AIP, the authorization gateway we built at Graze Social to alleviate some of the pain.

Spaces as Layers

Public anchor records paired with sidecar records in permissioned spaces give ATProtocol apps a composable pattern for blending open discoverability with controlled access.

Permissioned Data Diary 4: The Big Picture

A special edition of the data diary that sketches out the rough shape of where we're heading.

Permissioned Data Interlude: Spaces

In which I retcon the naming of everything.

Publishing Without the Platform: What Leaflet.pub Does Differently Than Substack

Leaflet.pub builds on the AT Protocol to give you something Substack never will: content you actually own. Here's what that means for European marketers.

Permissioned Data Diary 3: Your Bucket, My Data

The third in a series of posts building up a solution to permissioned data on atproto. We look at two different models for where buckets live and why the simpler-looking one doesn’t work out.

greensky: what does permissioned data feel like?

At @habitat.network, we're working hard to launch something at ATmosphereConf. We're building a platform for user data agency: giving users full and transparent control of where their data flows on the internet. Naturally, building a privacy-first platform, we're thinking about permissioned data.

Powerful communities from simple sites on the Atmosphere

ATProtocol allows you to build powerful communities with in-built reach, while massively simplifying your website code.

ATProtocol Patterns: Record Elicitation

Record elicitation is a pattern where a client asks an AppView to construct a record from the user's intent, rather than building it locally. This lets the AppView handle business logic, validation, and schema complexity while the client retains full authority over what gets written to the user's repository.