These seems like strongarming other clients to implement some spec they may not want to implement. Now we have broken images from a major nostr client. Are you implementing images this way #[5]​ ?

Reply to this note

Please Login to reply.

Discussion

The idea is to not stop at images. PDFs, music, APKs, etc. Everything will be hashed.

420 buy signal folks.

Agree, we need backwards compatibility until consensus is reached. Breaking functionality to force a change is not cool.

Normally it’s fine but this completely breaks a core feature in most clients (images). Doing this in a backwards incompatible way is just way too much. Good to hear he’s switching back to urls.

I want to use the magnet links so probably, damus can continue to use the url. But it's not optimal

I already implemented nip94 on snort but only for parsing other clients didn't implement it yet som I'm just waiting

I think magnet links should be built on https://webtorrent.io instead of a non-browser-accessible protocol.

Yes im talking about webtorrent, this is what i want to use, void.cat already supports this kind of magnet links with wss trackers already added

Is running Torrents over WebRTC part of any Nostr nip standard?

I am sure somebody can make a relay bridge into the torrent system.