for the most part the plc tool is done, unsure of unleashing it to the wild yet
urgh this is annoying, atproto/crypto relies on uint8arrays@^3.0.0, at this point i might as well just fork it so i can have an esm build
oh i'm an idiot, signPlcOperation will always grab the last operation from PLC [◌]( ) https://porcini.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:ia76kvnndjutgedggx2ibrem&cid=bafkreiaovjbjkywo62ns3pdgyep3fa2nag4r4tshrwfrllpvc3tlogthnm
hmmm this is wrong, but i'm not sure how to fix it https://porcini.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:ia76kvnndjutgedggx2ibrem&cid=bafkreieu6di6bpojva23uwh6xfwfdby5xqiv3fl22dwvtqhhb66f7j3eau
testing nullification but i forgor i haven't added the ability to push ops with your own key 1sec
wowow it works https://porcini.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:ia76kvnndjutgedggx2ibrem&cid=bafkreifoywbiu4a2o7zde566fbx2rkxaqyrcqzqkajh6zdcrrxtlrfxcwu
smtp... smtp...
find it unfathomable that you would need to verify the new york times account despite it clearly going with the "nytimes.com" domain handle https://porcini.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:ia76kvnndjutgedggx2ibrem&cid=bafkreie7qmcoikaxwqhwz7if2u6icsrtkfe3vja3llbo37wd3jbbqsftma
am i providing enough warning https://porcini.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:ia76kvnndjutgedggx2ibrem&cid=bafkreihe7ow3f76lz5lsgssg35ft4du7cge2sehsnsgp34w2evlpajnaiq
not where the payload input will be but hrmmm, i wonder if i should have wrapping here https://porcini.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:ia76kvnndjutgedggx2ibrem&cid=bafkreih3bb6vticuewoqwt5jzkzhp6tckujcduyagdarluhmajkjwk6qke