Some ideas that would be interesting to explore:
- A file provider like https://nostr.build but offering torrent seeding instead of direct downloads
- A platform for turning torrent magnet links into images (caching them briefly)
- Nostr clients uploading stuff (small images) to these torrent providers and inserting the magnet links in the notes
- Nostr clients that download render magnet links as images (if file size and content-type are applicable)
- Nostr clients that don't want to download torrents directly can turn the magnet links into normal image links from the aforementioned platform
I think this enables somewhat decentralized image-hosting:
- The torrent metainfo/magnet is derived from the file content for each image doesn't change, so even if one provider (or yourself) goes offline it can be in multiple others
- Since the magnet link doesn't change even if the provider that turns magnet links into HTTP images dies, the clients can just replace it with a different one, the notes do not lose their content
- Each of these steps can be done by different people, with different degrees with redundancy, cost and pricing
Some ideas that would be interesting to explore:
- A file provider like https://nostr.build but offering torrent seeding instead of direct downloads
- A platform for turning torrent magnet links into images (caching them briefly)
- Nostr clients uploading stuff (small images) to these torrent providers and inserting the magnet links in the notes
- Nostr clients that download render magnet links as images (if file size and content-type are applicable)
- Nostr clients that don't want to download torrents directly can turn the magnet links into normal image links from the aforementioned platform
If not that, at least turn them into clickable links to some platform that does that for us.
BitTorrent is the only p2p protocol that has ever worked besides Bitcoin.
An easy win would be to include magnet links on Nostr notes (with trackers) and hope clients implement a way to automatically download these and display.
*sheds tear* I am honored and humbled to be on this list on [Snort](https://snort.social) with these legendary Bitcoiners. Previously, I was on the *Suggested User List* for Google+ many years ago. I don't know if I deserved that back then and I don't know if I deserve to be on this one now, but I am absolutely grateful. 🤙
Meanwhile I am disgusted of having been included in the same list as Jack Mallers.
Clients should definitely not be trying to fetch everything from all relays all the time.
Oh, in that case I am sorry for you. It is sad to see cool proposals not getting activated ever.
If someone can generate public keys from a known xpub, then any private key that leaks from that xpub will also allow the other person to derive all the other private keys.
Welcome to BIP32.
If SMS supported Markdown then Twitter would have been a failure.
Email is a really bloated protocol, you know.
About what?
Sure, I agree. I think we should have other standard formats, but in other contexts (and probably other apps dedicated to them -- not that they couldn't be merged into "social" apps too if client developers wanted), using other event kinds, not the basic most simple Twitter-like kind-1 notes.
Hello, #[4]! How are you #[5]? Good evening, #[6]! Arrivederci, #[7]!
It seems to be working.
Yes, we do. https://github.com/nbd-wtf/go-nostr is a very small library that uses LND Schnorr libraries (although it has a bunch of micro packages for various NIPs).
But you probably don't even need this, could go much smaller depending on what feature exactly you want to support.
An invasion of cash.app people: 
This will be amazing if you manage to do it.
That RSS bridge was a very half-baked product, it could be better with some caching. but I still stand by it and its approach to bridging: bridges should act as their own specialized custom relays, not as spam-producing machine that produce junk and send to other relays.