phil

we don’t got resolveDid because i’m not storing the complete did document a

we got `com.atproto.identity.resolveHandle` slingshot.microcosm.blue#tag/comatpro...

always bi-directionally verified (optional according to atproto.com lexicon)

still need editing but slingshot docs are shaping up

ooooooh this is cool

clockwatch has some bite to it. tardis is annoyingly compelling.

chrono (dull)
carbon (earthbound)
nucleo (nah)
atomic (as in clock)
isotope (stretch)
ante (for “not after”, ehh)
crater (cool but confusing)

whatever, more important: vole clock.

“Nucleocosmochronology”. ship it?

ooh i like that! and it wouldn’t be the first time lightyear gets used wrong ha

“gyrochronology” is a way stars are dated. nice but a bit of a mouthful and the spinning aspect doesn’t feel quite right.

the timestamps are “first observed” so it also feels like there should be something there but i’m not sure what. i haven’t found a satisfying term for celestial cataloging

still seeking a nice name for a microcosm record-trusted-timestamping thing

redshift is nice but probably too confusing with the aws service. blueshift is bleh and makes less sense (we’re in an expanding dataset, blue would should be for contracting)

config.json containing enough info to index statusphere statuses from jetstream to an elastic search instance

the elastic search query response for "query": { "match_all": {} }

tried doing something today
esav.whey.party/xrpc/com.exa...

this is so cool

Skyblurで表示時や投稿時に稀にエラーが発生する場合があるようです。
必ず発生するものではないようで、再現ができおりません。
もし発生した際は、お手数ですがスクリーンショットを提供いただきますと大変助かります。

i always wondered what the signing key in the stream place records was for. neat!

had a minute to look more into the (verifiable) commit blocks on the firehose vs `com.atproto.sync.getRecord` and found good good things. CARs all the way down, atproto is cool, verifiable(!!) fast pre-cached record endpoint coming to slingshot soon.

You can now look at the PLC operations history directly from PDSls in the DID document tab of a repository

maybe just a config option to either host the pds+lexicon, or not and use the default/main-instance prefix.

then if a third party forked the code they could also just go ahead and modify the lexicon kind of painlessly.

tempted to host a small xrpc query lexicon from a tiny embedded pds/ did:web of the service itself. the did:web itself already exist for service proxying.

a third party instance would have a separate nsid prefix even though it’s the same lexicon. that feels slightly off for interop idk.

I’ve added a new feature to the ATProto Dashboard: Lexicon Browser.
It allows you to view and search third-party collections gathered by the dashboard in a tree format.
You can access it from the "Browser" link on the left side, or directly via the link below:

selfhosted.social is live for business for mutuals! So, let me know if you are a mutual and would like an invite code!

Not required, but if you'd like to help out with server costs, you can become a GitHub sponsor. I put a $2 a month tier for it.

github.com/sponsors/fat...

aw thank you!

a large bunch of green basil and four green chilis underneath on a wooden table

first chilis and a little basil from the garden

also unlike `com.atproto.identity.resolveIdentity` it actually exists 😇

still pre-launch but a few queries are up and public and should be working at slingshot.microcosm.blue, feel free to send some requests at it.

just added com.bad-example.identity.resolveMiniDoc, which is like com.atproto.identity.resolveIdentity but more convenient and doesn't require auth

another, appschool.me

what were this IP's past lives

ok and we're back: slingshot.microcosm.blue

(thanks to this one weird trick: blah.slingshot.microcosm.blue)

(imagine how easily you could hit this if your app got into a bad state and its supervisor put it into a restart loop. not matter how quick your fix is, you might be down for 34 hours 😬)

i'm still in letsencrypt rate-limiting purgatory woof. i thought i would only need to wait for the 202-minute reset, but looks like it's the 34-hour reset.

gonna PR some warnings to the poem acme docs since it only takes five app restarts in seven days to hit this with default settings.

i didn’t think my first published lexicons would be xrpc queries, not record types.

com.bad-example.repo.getUriRecord Ergonomic complement to com.atproto.repo.getRecord which accepts an at-uri instead of individual repo/collection/rkey params

it's the little things