nostr:nevent1qvzqqqqqqypzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qyw8wumn8ghj7umpw3jkcmrfw3jju6r6wfjrzdpe9e3k7mf0qyf8wumn8ghj7mn0wd68yat99e3k7mf0qqsgt9a6dcukuhw96ep24ngm30xmnetkyrcwjmywk2zgx37wqzp3tks60c76u

Now that the cool feature is done, time to get back to work on refactoring...

nostr:nevent1qvzqqqqqqypzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qyw8wumn8ghj7umpw3jkcmrfw3jju6r6wfjrzdpe9e3k7mf0qyf8wumn8ghj7mn0wd68yat99e3k7mf0qqsw8hlee762e8pnqc88f58zht5l3e9y6lcw7aqpt6n8dm9ek9n2tys59zk02

Reply to this note

Please Login to reply.

Discussion

How do you know if a url is a blossom server? Or do you just copy all images regardless if their host is a blossom server?

its looking for "imeta" tags first, then guessing on the URLs in the content. if the URL ends with a 64 length hex string it guesses that its a blossom compatible URL and tries to copy it

worst case it fails and the user isn't any worse off

Can't we just specify a ping to the server that all blossom servers can reply with ack + the filetypes they support?

I'd like to avoid adding any "meta" endpoints to blossom servers, since that introduces and extra step for clients to intact with them and then the client needs to ask the server how to interact with it before it tries... things get messy

The /mirror endpoints works kind of similar though. the client makes a PUT /mirror request with the url and sha256 of the blob the user wants to mirror, then the server either mirrors it and returns 200 or refuses and returns 400 or 401

relax, it's friday... I'll leave my wayland pile of shitty C code behind for a beer

What's the status of accounts and signer packages? Has the relivant nostrudel code been moved into applesauce?

thanks for the reminder, Ill try to finish it up now that I got the nostr-connect signer finished

Thanks

Done. https://hzrd149.github.io/applesauce/accounts/accounts.html

Its completely untested but the typescript is happy... so that means it works?

you should be able to install it with "npm install applesauce-accounts@next"

Thanks. I'll check it out on Monday

Nudge: Do you need to run `pnpm release`?npm registry is still at v0.10.0 but your last commit bumped to v0.11.0.