What is Nostr?
constant / Constant
npub1t6j…ksrw
2025-01-28 00:17:18
in reply to nevent1q…rmg6

constant on Nostr: The problem is not the nostr event/note, that already exists on multiple relays; and ...

The problem is not the nostr event/note, that already exists on multiple relays; and even if it were removed completely, it could be reuploaded at some later time. This is because nostr events/notes are self contained things, and people can verify them because they are signed and hashed.

To illustrate: lets say some archieologist digs up a harddrive with this thread on it, but the original post is not there, yet there are all these responces to this original post. And then 100 years later, someone digs up a clay tablet that has this particular OP written on it; this means they can solve this age old mystery because the event ID (which is a hash of the post itself) matches; They can verify that this was what everyone was responding to.

Now, the issue arives with the video. Because this event contains a link, and obviously that link will be broken, primal servers dont exist anymore in this far far future. In other words, we dont know what that video file is supposed to be, we only know where we were supposed to find it, and that place no longer exist; hence there is nothing to verify, even if you'd find the correct video in some other place.

We have a standard that adresses this (in theory for the most part, in practise its a bit of a different story due to lack of development/implementation), called blossom, which hashes files such that that is now how we reference them. I was just pointing out that this is not being used here, and therefore when the link dies, the nostr event might still exist but it became useless; if it referenced the hash of the video, the same "dig up a random clay tablet in some random place on some random time" principle would apply.

I.e. its the fundamental difference between referencing a thing directly, or referencing a location. The old web relies on location ; your email adress is @ (get it? "At") some domain, your instagram post is an instagram post because it 'comes from' instragram dot com etc. Nostr flips this on its head, puts the thing itself central using hashes as a naming scheme, and subsequently relies on 'hints'/'suggestions' as to where that thing may or may not be found; and if you can't find it, you can always go and look to see if you perhaps find it elsewhere, because you know what you are looking for and can verify that you found it.

Hope all of this makes some sense :)
Author Public Key
npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw