Nostr Web Client

Latest PR for #blossom

https://github.com/hzrd149/blossom/pull/13

This defines the the k:10063 event and how clients can use it to repair broken URLs

If your a nostr client dev id like to get your feedback on this one, since its something that needs to be implemented on the client side

Slipstream 1y ago

Why not define a blossom:// url instead of having clients try to extract the hash?

Reply to this note

Please Login to reply.

Discussion

hzrd149 1y ago

That would work just as well for blossom, but using the servers domain + sha256 as a URL allows it to be backwards compatible with any web browser or client that renders images from URLs

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

eliminates the additional changes that would otherwise be required to render files that are normally recognised by .jpg/.png/.webp/.webm/.etc

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

also, slicing up strings is retardedly easy stuff

Rand 1y ago

Slipstream 1y ago

Makes sense. That is how I've already implemented the blossom integration in my app (just with a different 'kind' for server list - I'll switch it to standard)

Slipstream 1y ago

Oh wait I've already used the right kind... has this bud been around longer? Somehow I've already implemented this exact flow in my app

hzrd149 1y ago

Its been a thing since I first wrote the spec. I just haven't written it up in a BUD yet

hzrd149 1y ago

Make sure its using the "server" tag and not the "r" tag. The first version of the event used the "r" tag and I changed it to something that made a little more sense

Rand 1y ago

hzrd

hzrd149 1y ago

What app are you working on?

Slipstream 1y ago

Not quite ready to release yet, but it's a writing platform similar to Obsidian or Logseq. Also supports serving up your content on your own domain as a "blog" of sorts

hzrd149 1y ago

Cool, can't wait to test it