Discussion
Which client is this one? look at this nostr:nprofile1qqs89qlxtkn8lmvn5pdc3d5tpy3jy7v8jd2ypecrcnzy9vep3u99a8s9ugt9u
A social client design for Android (Amethyst redesign/upgrade basically) that I'm drawing out for:
- nostrdesign.org
- my own use of these components in "other stuff" clients
- my own overview + understanding of all the new opportunities in the nostr design space
Feel free to copy, steal anything: https://www.figma.com/file/cVMpSIFQKYzlVLkWK48eZW/Android---Social-Nostr-Client?type=design&node-id=0%3A1&mode=design&t=sZx02bhNPt7AP0Jk-1 (Work in Progress)
Gotta beat the final boss nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z 😆
I am going to copy the + button on profile 😁
That alone would help me (as a daily user now) a lot!!
Is there already a way to quickly add users to profile lists on Amethyst btw? For now I keep switching to nostrudel for this.
Not yet. I initially left it out to get people using listr. Similar strategy on community clients. But it's time to gat back to it.
Too bad I am in the middle of a large refactoring. But we will get there in time.
I see. No urgency there.
In my mind it comes down to having the quick actions in the Everything App (Amethyst) and the specialised tasks in separate apps (Listr, ...).
For example:
👉 Add to Lists VS Managing your Lists in detail (deleting users, notes you don't interact with, ..)
👉 Add an article to bookmarks VS Reading/Listening to that article in Highlighter
👉 being part of a community VS Being an administrator and needing a large dashboard for curation, payments, ....
Thats nice prototype, something like this would be cool. I imagine that can be a local feature, like you save you stalked/subscribed conversation locally and your client check if there are new things when open it, so you don't expose your stalks, and you can do it by now since doesn't need a new nip or whatever
Exactly! And for now it can be something non-interoperable within just one client. (we'll need general local nostr databases or things like spring browser to make it interoperable).
Devils advocate:
Making this a public feature though would make the "amount of stalks" a very high signal metric. You can see how many of your peers basically chose to spam their notifications with it.
Yes, definitely, can be interesting to have this metric, or be interoperable in some way, maybe it can be done using the existing nips, but for sure its gonna need or active checking by the user or a server that check it for you