Nostr Web Client

Do you also detect blossom links and find the file elsewhere if it's no longer there? Want to do this for chachi and was wondering if I could yoink the code from somewhere.

https://github.com/hzrd149/nostrudel/blob/master/src/components/note/timeline-note/components/share-modal.tsx#L46-L57

Here is the code that gets all the "imeta" blobs and any blossom compatible URLs in the content

and here is the code that sends off the /mirror requests https://github.com/hzrd149/nostrudel/blob/master/src/components/note/timeline-note/components/share-modal.tsx#L63-L96

That's great but I'm asking if when displaying blossom media and the URL is broken do the links "self heal"?

https://github.com/hzrd149/blossom-client-sdk/blob/master/src/image.ts#L12

oh yeah, codes here https://github.com/hzrd149/blossom-client-sdk?tab=readme-ov-file#handling-broken-images

Awesome! Thank you!

Freakoverse 11mo ago

Would this also work for any file/blob (not just media)?

The code is written for HTML image elements, but it wouldn't be hard at all to convert it to a simple "download" script that would try to download a certain blob from a list of servers

I built something similar here https://github.com/hzrd149/nostrudel/blob/master/src/views/files/components/download-button.tsx#L28-L75

Have you looked into the WARC and CDX file formats? Webarchiving staples. WARC collections with fallbacks is a thing

Interesting, I need to look into this

If you wait [just a bit] I'll have something to show you.

I'll definitely be talking about it on Nostr, but if you want to drop your email at https://opfn.co that would work, too

Yeah, at some point I want to integrate it into the https://archiveweb.page/ extension

Wouldn't you prefer a decentralized solution that got the web archives from your peers..?

😎 Stay tuned

nostr:nevent1qqsgt9a6dcukuhw96ep24ngm30xmnetkyrcwjmywk2zgx37wqzp3tkspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygpxdq27pjfppharynrvhg6h8v2taeya5ssf49zkl9yyu5gxe4qg55psgqqqqqqsaxsawt

Yes!!

We should talk soon. About webarchiving.

Liberating/rehoming _media_ is excellent. Now apply the same idea to entire web pages.

ponymontana💜⚡ 11mo ago

really cool! Last time I tried it, there were some features I really missed:

- giftwrapped chat messages, like the one uses amethyst, 0xchat...

- upload of any kind of media. I saw only buttons to add photo or video to notes, a .txt file was not suppported I dont know if its something more related to the mediaservers used, but I didnt been capaple to even try the upload in the client.

gitwrapped messages will come... at some point. I don't like spamming the user for decryption requests so I have to find a way to safely cache things

non-media uploads should be pretty easy to enable though 😀

spamming would imply that they can't accept them always, and you not giving that option implies you don't trust yourself to write mostly secure code

have a little confidence in yourself ser, your code is great, really, and i say that after having read a bit of it

i recommend you start thinking about the idea that people may not agree with your viewpoint that privately decrypting messages is not dangerous

i mean, you seem to think that there is some privacy risk in decrypting messages, could you explain that to me?

Its not a privacy risk, its that its bad UX to ask the user to decrypt 10+ events as soon as they load the app

you are essentially stopping users from being able to use DMs properly with this "security model" of yours, you know that, right?

and yes it is a privacy risk... the data gets decrypted into the app's memory and some XSS breach would allow cleartext of messages to leak

yes, it is!

but by proactively preventing people from doing this by refusing to do stuff like - not encrypting the configuration, you make it really hard for users to have another choice than the one you have forced on them