Profile: 8b278ad8...

Replying to Avatar Matt Lorentz

I know nostr:npub1veeqt66jt2j209y9nv4a90w3dej074lavqygq5q0c57dharkgw0qk738wt, nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn, and nostr:npub1z7e7ml8kevdfdala8k0cthfhcvfhmxf8mt27qzc83pc8ay0m3zdqlgw4fh have been pretty active on the NIPs for this. Would love it if any of you stopped by. I think nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z has been weighing in as well, although I think they’re at Bitcoin Miami rn so probably unavailable.

Just woke up, turned on Gossip, and saw this message. I can attend!

I mean really Dave, if you have any questions at all I want you to ask me.

Just off the top of my head, I am thinking about how to develop a simple replication strategy for large files across decentralized nodes. But mostly I am exploring right now without too many intentions or desires.

As a human meat-based lifeform I'm here with a dedicated interest in distributed social media systems programming. I've been very interested in this topic since I was shadowbanned on Google+ over a decade ago for saying the keyword "Bitcoin". Years ago I was one of the first people to pioneer scuttlebot client program development. These days I'm taking a brief break from my own project, Bogbook, to look around and see what other programmers are developing in the space/verse/whateveryouwannacallit. You might say I'm on Nostr to explore, learn, connect, and engage. Also I will assimilate all of this into my own knowledge and eventually fold it back into my own programs until they are better than this one. Thanks for asking, @dave!

Replying to Avatar Vitor Pamplona

Here's the first proposal to send private pictures in NIP-04 DMs from the discussion with nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 this morning

The idea is to add credentials to NIP-19 URIs (the nostr:nevent.. links) and create an "Anyone with Link" can see scheme. Since DMs are encrypted, only the two people in the conversation will get access to the image. Not even image hosts can see it.

Pros:

1. Simple change to a NIP

2. Straightforward implementation

Cons:

1. If the link is copied and pasted outside of a conversation, whoever has access to that link will see the contents of the image/file.

2. Once the secret is out, it's out.

3. URIs with secrets are bigger.

I believe the Cons can be minimized with appropriate UIs. Thus, I think this is a good proposal.

https://github.com/nostr-protocol/nips/pull/519

The trouble is that when you start inventing a distributed secret blob store you suddenly have a very different set of challenges than the ones that Nostr has already solved. Look at IPFS and Tahoe-LAFS and to some extent Scuttlebot's blobstore for some suggestions, but none of them are perfect and everyone still complains about these programs.

Really there should be a Nostr team and a team building the secret blob store, and we're risking too much technical debt being forced on the client AND relay developers.