honestly if you're putting it in your password manager you should probably just store the hex of the privkey but like if you're writing on paper then it's good

or u can do RYOW on the client and have no delay and still have the PDS be the primary write sink

feels much less ulysses pact feels much less locked-open when the app server can just go "yeahhh well im gonna keep ingesting this data u give me but i wont keep writing records to PDSes because i got a competitor trying to adversarial interop me"

just doesn't feel like skipping one header on the client and targeting the url straight at the app server is a DX benefit big enough to justify ceding control from infrastructure the user controls to opaque (unchangeable!) territory of the future adversary, even if u do get to do serverside RYOW

i have an alt but i won't tell you where it is. collect my pages

oomf mentioned

i just did sync.listBlobs, repo.uploadBlob, and sync.getBlob :)

my sync.getBlob implementation also differs from the vanilla implementation in that it supports the HTTP Range header and can return partial responses

i did sync.getRecord and now PDSls can verify the carslices ^-^

da real answer is i have a follow record where the subject is myself ^-^

i did putRecord :)

im my own fan

im swag

things it has this Tuesday night:
- OAuth authorization_code flow
- repo.getRecord

things it doesnt have:
- putRecord
- sync.getRecord
- getRepo
- subscribeRepos

mu >.<

it happens ^-^

netdevConfig not netDevConfig