look on github?
That's so cool, nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z! I'm curiousl to see how the json event looks like! Maybe I will have a look using gossip from nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c
In case that someone/government/hacker takes all of the image servers down and someone find an alternative with backup images, what should a regular user do to see all images again?
query a dht
unnecessarily complicated, just hash address in the note
torrent is banned wtf lol?
distribution is less important as long as we hash address the files, we can distribute any way then
i wonder if blake3 would allow fetching a lower res from the same data? is there any image formats that allow that?
ridiculous that we have a distributed social protocol but only for text
and when nost.build goes down? goes woke? goes fed?
not sha256 use blake3
https://www.youtube.com/watch?v=nk4nefmguZk
and check out iroh which is ipfs using blake3
a picture is a thousand words
memes are most of social
no this is what caused ipfs to suck having too many options, just use a single hash function have a version so you can change it later, bittorrent only went to version 2 recently
with blake3 you can verify any chunk size from 1KB denominations
not needed, just hash address the media inside kind1 notes and let clients and relays decide where to fetch it
There's the possibility of censorship on media or any other external content (governments take down links to fotos, Videos, audios, etc, or the serves themselves delete it). On the current model, our external content storage is the weakest link in the chain of our censorship treat model. As a lot of the communicaton is thru images or videos, that's a very serious issue.
Proposal is to add hashes to our external contents and possible serves to download the content from, so it's easy for clients to search for content elsewhere.
Sha256 might be not enough in future (imagine in 10 or 200 years, quantum computing, etc), so could be better that there's the link, the hash, and the algo used, so that in future it's easy to change the hash algorithm.
If you want to use multiple media, make that a list structure.
If you want to preserve this media position inside the text, you can put a pointer indicating where's the media supposed to appear inside the text, say after character 100, or after byte 800 (I don't know if it's better byte or character.
Puting all together,we have the following structure:
{externalcontents:[{
positionontext:100,
possiblehashes:{
sha256: 0x eeafb2,
sha1024:0x ffeabc4438,
etc},
possiblelinks:[
server1.com/link1,
server2.com/link1,
torrentsite.com/magnet/link1,
ipfs.io/link1, newstorageparadigm.com/link1]},
{
positionontext: 200,
possible hashes: ...
..}]}
/Link can be a traditional link or something that tells the server to fetch a content with the specified hashes. Then you could use torrent, magnet, ipfs or whatever new technology that comes on the future.
If on the future we have a user, say, Snowden, and all his possible media were taken down by government or the server itself he could:
a) do nothing and the clients will go to list of serves he put on his original message and try new ones. If all are down, then B)
b) the user/client developer might specify additional servers to search into
C) Snowden publishes news Servers where his mídia can be found
D) Snowden makes a new event with reference to the original and ask to update the list of sources
D) if Snowden has not the originals anymore, but have something equivalent, he can send a new event asking to update the hashes and the servers (I actually don't know if it's a good idea because someone might steal his key and break havoc with past messages).
Like this, we stop being prone to censorship on external content, which currently is a very high and unmitigated risk.
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub10qk5zpmhv7rspp87shajf7d24yrf4lyr7w0m25wv9w78grs4k0sq0gq8pc
#nostr #amethyst #damus #nostrproposals #censorship
this is too complicated just use a versioning scheme and blake3 hash, look into iroh
iroh which is an improved version of ipfs, uses blake3 hash which unlike bittorrent v2 and ipfs will allow direct hashing of the file for addressing ie we can address media like we do notes
its a narrative, like if they are so smart why do they have all the issues they have? they have explained it all with stories involving god but reality is they cant objectively view their behavior and ideas for what they are and why they will bomb a hospital, something anyone with a slither of humanity would not do