iiinova — where your digital self keeps evolving

Willem Dantuma @willem.dobs.nl · 22/09/2026

I do, but only as an internal implementation detail (to be able to reuse the low level stuff ), nothing exposed

120

Willem Dantuma @willem.dobs.nl · 08/09/2026

Does anyone know how many plc replicas there are ?

010

Willem Dantuma @willem.dobs.nl · 01/09/2026

@dholms.at What are your thoughts about a requirement that spacetypes should be published?

010

Willem Dantuma @willem.dobs.nl · 01/09/2026

Fair, but I do think spacetypes should be published because they are part of a granted scope, so my PDS will not allow it ( it expands all permission before granting). To make check.cirrus.earth more usable if would suggest to use a published spacetype

210

Willem Dantuma @willem.dobs.nl · 01/09/2026

This works only for PDS implementations which have the bluesky lexicons stored locally because the lexicon app.bsky.group isn't published yet at @bsky-lexicons.bsky.social

120

Willem Dantuma @willem.dobs.nl · 31/08/2026

Logging in doesn't work the mentioned document (mu.social/oauth-client...) should be public available. It is from a browser, but isn't from the server ( 403 ) so the PDS oauth server refuses the PAR request ( can not validate the client )

300

Willem Dantuma @willem.dobs.nl · 31/08/2026

@sebastian.eurosky.social , @mu.social Does mu.social only support selected PDS instances ? curl mu.social/oauth-client... results in a HTTP 403

110

Willem Dantuma @willem.dobs.nl · 27/08/2026

@knmi.nl waarom staat code geel voor vanavond wel op de site, maar niet in jullie app ?

100

Willem Dantuma @willem.dobs.nl · 20/08/2026

Great looks like what I had in mind when posting this bsky.app/profile/will... , but please keep multipart upload lexicon mimetype agnostic so properties like durationMS, width and height are something I would place in a supporting lexicon I guess

010

Willem Dantuma @willem.dobs.nl · 17/08/2026

@ngerakines.me is the lexicon/proposal of community.lexicon.service.describe available somewhere ?

121

Willem Dantuma @willem.dobs.nl · 11/08/2026

@matthieu.bsky.team @divy.zone Should DidDoc not be removed from the com.atproto.server.createAccount response in case of a migration ( did set and service auth ) ?because there is no new identity created

000

Willem Dantuma @willem.dobs.nl · 06/08/2026

@bmann.ca Is the content of the lexicon.community forum still accessible somewhere ?

100

Willem Dantuma @willem.dobs.nl · 01/08/2026

It would be great if this code could be integrated in the PDS "compliance" test tool ( check.cirrus.earth ) @mk.gg made.

check.cirrus.earth

☁️ check

Verify your AT Protocol PDS.

140

Willem Dantuma @willem.dobs.nl · 31/07/2026

Another example why I like the flexibility of the space proposal github.com/bluesky-soci... so far.

020

Willem Dantuma @willem.dobs.nl · 29/07/2026

I guess its time for a new blob upload API for the PDS with support for pre registering the upload (quota/limit check) and upload resume

130

Willem Dantuma @willem.dobs.nl · 13/07/2026

"Verify your age" Walks over to the tv to push a button to switch to a new channel and to previous chosen button (channel) pops out.

150

Willem Dantuma @willem.dobs.nl · 12/06/2026

Why then does @mu.social need control over youre identity and handle if migration is not needed ?

100

Willem Dantuma @willem.dobs.nl · 26/05/2026

This is great, something much needed by the atmosphere.

010

Willem Dantuma @willem.dobs.nl · 14/05/2026

Yes it should. Proving possesion of a registered rotation key (signing a jwt) should be the preffered method for authentication (plc wallet/ atmosphere wallet )

010

Willem Dantuma @willem.dobs.nl · 22/04/2026

App views can always implement a single view over multiple PDS's that where they intented for

030

Willem Dantuma @willem.dobs.nl · 22/04/2026

I agree with this, the user did -> PDS ( user ID -> data location) relation sould be 1:1, this simplicity is part of the beauty of atproto. If users want to split their sara they can always create another ID ( did) maybe linked by alsoknownAs.

130

Willem Dantuma @willem.dobs.nl · 21/04/2026

Well it's my interpretation of how it should be working and how I implemented it in my PDS i'am not sure how the reference PDS implements it , maybe @bnewbold.net can clarify

100

Willem Dantuma @willem.dobs.nl · 21/04/2026

No problem I think, you can express an any aud in the permission when the client does its request it specifies the real aud in the atproto-proxy header, that gets validated against the permission and used in the service token aud.

110

Willem Dantuma @willem.dobs.nl · 21/04/2026

My choice would be a dedicated PLC mobile app storing the 'hot' rotation key, with an option to store higher-order 'cold' rotation keys completely offline (Shamir's?) to support the situation of losing your mobile. Social recovery would be my second choice.

030

Willem Dantuma @willem.dobs.nl · 17/04/2026

so not configurable by a third party ( the provider of the permission set)

000

Willem Dantuma @willem.dobs.nl · 17/04/2026

I agree, but I think the permission set icon's in the consent screen should be provided by the PDS ( the one you trust with youre data) and should be an indication of the risk you take agreeing with a certain permission set, possibly provided by some configureable policies on the PDS...

110

Willem Dantuma @willem.dobs.nl · 15/04/2026

It would, but you have the same problem if the domain name in your did expires. plc mirrors already solve this, just configure multiple mirrors in the did resolver

100

Willem Dantuma @willem.dobs.nl · 15/04/2026

I am locally using a ( virtual) plc directory which is a proxy to multiple plc directories

010

Willem Dantuma @willem.dobs.nl · 15/04/2026

Personally i'am against"polluting" the plc did with an domain name the did:plc not containing a domain name is its strongest characteristic if you ask me. Create the solution outside the persistent id...

200

Willem Dantuma @willem.dobs.nl · 07/04/2026

PPS ( Personal Processing Server )

020

Willem Dantuma @willem.dobs.nl · 02/04/2026

I'am planning a lot ( Farm data related ) but most of it is waiting for reaching consensus in the community about how permissioned data is handled. For the near future i was thinking about a generic geometry index ( index with backlinks to records containing a geometry type )

010

Willem Dantuma @willem.dobs.nl · 02/04/2026

just create an atgeo format dealing with this for openlayers and leaflet and you have most browser based geo covered

100

Willem Dantuma @willem.dobs.nl · 02/04/2026

picking the correct defaults in the lexicons would simplify things a lot, in this lexicon the default coordRefSys is EPSG:4326 ( lat long ) so could be omitted and if you choose a default float64exp value of -6 lat 52.156160 lon 5.387638 would be written as 52156160 5387638

110

Willem Dantuma @willem.dobs.nl · 02/04/2026

It's not about projections used in the geometries but about how to represent a float, ignore the projection. But for serious geo data you eventually need projections

210

Willem Dantuma @willem.dobs.nl · 02/04/2026

and a record using this lexicon here pdsls.dev/at://did:plc... then with some tooling you could create the floats on the fly

pdsls.dev

at://willem.dobs.nl/org.custorium.temp.jsonfg.testRecord/3me6siayjo42k

100

Willem Dantuma @willem.dobs.nl · 02/04/2026

Another way without changing the base atproto data model is introduce a float64 and float64exp lexicon definition somewhere in the com.atproto.lexicon namespace as used in this lexicon pdsls.dev/at://did:plc... ...

pdsls.dev

at://willem.dobs.nl/com.atproto.lexicon.schema/org.custorium.temp.jsonfg.geometryObject

100

Willem Dantuma @willem.dobs.nl · 31/03/2026

true, but it's not something we should pursue I think

010

Willem Dantuma @willem.dobs.nl · 31/03/2026

want, because you want to be able to use an app without installing lexicons first. A PDS can still use local versions of a lexicon which does override the dns lookup.

010

Willem Dantuma @willem.dobs.nl · 31/03/2026

Not really, the lexicon nsid ( reversed DNS id ) is used to resolve (dns lookup) the PDS where the lexicon's are hosted ( discovery ). This is needed if you want a PDS to be able to do basic lexicon validation, otherwise a lexicon has to be deployed at every PDS using it, something you don't..

210

Willem Dantuma @willem.dobs.nl · 30/03/2026

The party who defined a service interface (lexicon) differs from who implements it ( endpoint). I personally would like to reserve the com.atproto.* namespace for generic protocol level definitions ( domain agnostic ), feed is more a concept from a social app domain ( something build on atproto )

110

Willem Dantuma @willem.dobs.nl · 30/03/2026

like ( did:plc), lets just thust each other,and related see also bsky.app/profile/burr...

100

Willem Dantuma @willem.dobs.nl · 30/03/2026

Renaming / moving is not a solution, at least not for interoperability just use whats already there and add extra's you want in "sidecar" records, thrust the lexicon characteristic that its backwards compatible, maybe implement transparency logs to be sure ..

200