Hello #[1] and #[2]. Testing some mention improvements on Gossip.
Hello #[0] and #[1]. And #[2]. This is a test.
No, he won't like these.
Batchman!
Try Jorge Ben.
It is pinned at the top of my feed! #[1], help!
This basically solves the key management UX for normal people, doesn't it? Can we stop talking about key revocation and whatnot now?
Many times when I think of possible attack vectors on Nostr "unfollow that dumbfuck" is the obvious answer.
Relays could accept these and store, but only release them to queries when their date comes. Scheduled posts.
We have yet to see giant leaps in client optimization. The current paradigm of fetching everything from all relays is very bloated and should have never happened.
https://github.com/mikedilger/gossip is doing it differently, but other client makers are also conscious of the necessity of being smarter with the subscriptions.
member.cash is doing a mixed approach: keys on the client, but a special backend processes all data and serves it in a more efficient format.
It will be sad, but as long as they interoperate and a giant provider doesn't take control of the protocol it should be fine.
I like it.
These can be trick to implement due to abuse concerns, but I'm sure there are solutions available in your imagination.
I had started a proof-of-concept of this for Astral. Wasn’t sure if the community wanted this. Can pick it back up. Devs, check out https://webtorrent.io ...
My main concern is whether it’s feasible to implement a torrent client inside a Swift app (Damus). Any iOS devs know / have an educated guess?
It probably wouldn't be good for performance in a phone app, that's why I suggested the other more indirect approach of using a third-party image provider.