What an ideal #Nostr client would enable me to do: I want to be the CEO of my attention span. I want to decide how much attention to give to each npub or feed or whatever other concept we'll come up with. What the UI to my attention span would look like, I don't know exactly, but I have a few ideas. For instance, I would like to be able to specify: - I have mental bandwidth for about 45 minutes of #nostr today - for this list of people, show me everything they post - for this other list of people, show me the highlights, giving each roughly equal screen real estate - mix in 5% of posts from people I don't follow directly (say, the people followed by the people I follow) #nostrdev @jb55 @Kieran @miljan

"Trending" on snort / nostr.band / primal could be renamed to "What the biggest accounts wrote yesterday". Not much serendipity mixed in.

People complain about Arch being unstable, but Ubuntu LTS about once a year be like

I'm not sure an ETF will be bullish for #Bitcoin price in the short term. I suspect that some whales have been patiently waiting for big "exit liquidity" to dump their huge stacks on. If this indeed plays out, it may be the last big opportunity to stack cheap sats.

We all know (or believe) how things would be better under a #Bitcoin standard. What is the flip side of the (bit)coin? Which things would get worse? #asknostr #nostrplebs

If the money is unsound, things that are somewhat durable and scarce store value better than money itself; it makes sense to hold on to them, and to get rid of the money asap. If the money is ultrasound, it makes no sense to hold on to anything other than money, except for those things from which you gain high utility/benefit. I think this is what @`Jeff Booth` means when he says "Scarcity in money = abundance everywhere else". #Bitcoin

Idea for account recovery, in case you lose your nsec or it gets compromised: 1. Right now, set up a "failover" nsec/npub pair. Store the information separately from your current nsec/npub pair, and publish the failover npub on #nostr. 2a. In case your current nsec gets compromised (i.e. someone else is also able to post from your account), switch to the failover nsec/npub and disavow the previous npub as compromised, pointing to the message that you published in 1. 2b. In case you lose your current nsec, locate and start using your failover nsec, and announce that you are migrating to the new npub. In both cases, it would be beneficial if people were *already* following your failover npub. Perhaps this logic could be integrated into #nostr directly, so that the failover npub can specified as part of the protocol, and that a client knows that when you follow someone you automatically follow their failover npub as well. @fiatjaf #nostrdev #asknostr