There will be signs 
The rarest move in chess
pov you run your own lightning node 
nostr:note1vrf4avyx2nwm4zcmlsc5xrntzfx4ku6a2t5juqwgdzv5265hedfqefds93doesn’t do it for me
Building out Logarithmic Zaps 🤗
https://cdn.satellite.earth/78df1fa6e85eb98862ad6bc183c8fe4e80dee9378810811905cb136084cdc338.mov
Flutter is so perfect for this kind of complex UI's (and for designers like me that are new to coding this sort of stuff).
I'm learning how to turn my prototypes into a full flex design package at a very satisfying speed. For me, at least, as the designer that wants near-full control and guarantee over every pixel. Still too slow probably for the devs and users!) that want to use all of this three months ago 😜.
awesome
zaps can’t shut down nostr:note13xwz2pa2h6guhf8evvpvxh8m5zaf85aazz7r50yfgekdjfx6frlsye8z49
how to nostr effectively 
nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m is not a bad artist! 
change DEFAULT_QUEUE_SIZE to 1000000
High praise 🙏 thanks! i spent a long time on nostrdb to make sure its as fast as possible
I personally would make it a notedeck app but I’m biased
No lists yet, but now that we have multi-deck support you can make decks of individuals. Never miss a post from people you find interesting! notedeck wouldn’t be right without list support though, working on it!
nostr:note14l5vkhrckl460s0jg3dkcrrp549ddamw34l7ujpan393f2l26vys77a5zw
Hmm. Would nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpzpmhxue69uhkummnw3ezumrpdejqz9thwden5te0dp5hxapwdehhxarj9ekxzmnyqyv8wumn8ghj7un9d3shjtnwdaehw6r9wfjjucm0d5eechmk like this or does this still get his jimmies all justled?
It doesn’t have any ratcheting, also if you want to reroll your device keys you have to resend it to all your contacts which kinda sucks, so maybe you would want to do that opportunistically… you would have to keep around old device keys. A little messy but directionally better than only sending to your root key.
Unsolicited giftwrap DMs could be ignored except for “chat requests” which is a giftwrap of that users device pubkeys and inbox relays. This would get rid of the remaining receiver metadata on giftwraps, and enable “device keys”, where each DM gets encrypted to each device. If your root key leaks, the messages are still protected.
Cool work being done in this area by nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z and nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 :
Yeah this has always been the plan with the Damus Work set of tools. Just had to build the tech platform first to make this possible.
Yeah we definitely need to add more advanced filters. I also just want a mode where i can see all of the conversations between two people and filter further on that. Should be easy to do
test post please ignore
Random thought: what if each device you use creates a device key, you then update a key list that you publish from your root key. Then giftwraps could send to each key on that list instead. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
If your root nsec leaks then your messages aren’t compromised? and you would never be copying around these keys so maybe they could be more resistant to people pasting them somewhere and leaking them.
You have issues with needing to send many giftwraps though… but maybe not an issue once inbox relays are more widely used.
Im slowly catching up to nip17 and giftwrap stuff so pardon if this idea has already been discussed and is bad.
Random thought: what if each device you use creates a device key, you then update a key list that you publish from your root key. Then giftwraps could send to each key on that list instead. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
If your root nsec leaks then your messages aren’t compromised? and you would never be copying around these keys so maybe they could be more resistant to people pasting them somewhere and leaking them.
You have issues with needing to send many giftwraps though… but maybe not an issue once inbox relays are more widely used.
But i feel like the application should be choosing which relays to target for different types of queries, which is a part of the subscription manager api… that would be lost on a relay
just a mail app within nostr for managing async communications (really just a design thing with pinning notes in an inbox and having archival states, etc), but a bridge to email would be cool
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s you used to show a list of relays on a users profile? Whats the thought behind now showing it anymore?
we still show it, but it onlys shows the kind3 relays which is old. someone just needs to update the code to use proper relay lists
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s compared my day-after make up and hair to day old pizza…I’ll take it. Love that leftover pizza. Lol. Thanks hun 🤣
i was saying how day old pizza is still good
