💡 What's your dream Nostr client like?
What features should it have? 🤔
💡 What's your dream Nostr client like?
What features should it have? 🤔
Help builders, shill your ideas, show the demand! 😉
nostr:note1w86c4x4vrrx62ydh3mfzcl8celdcg8ehzug2q8dlx0kzyqtfwx2s3ndn7n
Not doxx my IP address to relays
That's impossible by design unless you use Tor on Nostr exclusively.
You can also do relaying similar to tor using wrapped events see https://github.com/motorina0/nips/blob/republish_events/705.md I coded up a rough version in Python a while back https://github.com/monty888/republishstr
vpn?
Marketplace of plugins:
- WALLETS (alby, mutiny, nwc, lndhub)
- SUPERFEATURES (markets, geotagging, etc.)
- BROWSERS (nostrgram, streams, etc.)
nostr client thats like mona for mastodon, fast, customizeable, nice UI
Extensive caching, high visibility into relay performance, clear controls around additional relay comms. Look at noStrudel for its handling of relays.
Drafts and scheduled sends.
I want more clients for different aspects of nostr.
1. A calendar app using calendar types and cross filterable by lists
2. A Hot or Not app for swiping left/right on just images referenced in posts, and have that create +/- reactions.
3. Audio streaming/Podcast app that uses Text notes for comments, Zaps for boosts, and Statud updates to inform what im listening too
I want todays popular mobile apps like Damus and Amethyst to treat lists like first class citizens. Be able to create and modify them just as one can do with communities
I also want either client side, or to-self encryption of labeling and associations. For example, I want to assign both the name "Alison" and the context "neighbor at 833 Wilshire Lane" to a pubkey whose name and nip05 doesnt reflect any of reality as they seek privacy. This meta information I assign is intended solely for me, and shouldnt be shared with the public at large
You should apply to nostr:npub1s0veng2gvfwr62acrxhnqexq76sj6ldg3a5t935jy8e6w3shr5vsnwrmq5