haha, dang, I ended up posting the same-ish thing twice. ah well.
the short answer is: when it's ready
the less rude, slightly longer answer is: asap. I can release the pubkey by day graph in it's current form, but I can do a lot better.
thank you #[0] for upping the game here. your business looks promising.
the bar for making the top 50 leapt from ~50 a few weeks ago, to just under 1,000 now.
the top 50 is no joke. in the last two weeks the cutoff to get on the list has raised from ~50 followers to just below 1000.
and thank you for upping the game here. #[1]
the part where it started growing more in the middle of the graph is about a year ago. I do recall a bunch of publicity happening then. with "a bunch" being about 10x less than this season's growth
that's no joke, thanks #[1] !
there could be a different answer for each app. a post, a message, an event, a payment, an item.
makes sense, but I think you proved the point. however the client handles it, you have at least made the world aware of the IPFS address, which is itself signed by your private (nostr) key.
no need if you're on a web client, it should be recognized as a URL, and if the browser handles ipfs, as brave does, it should just work
I assume that there are some relays operating that haven't shared a kind 2 message to announce, and some that have been announced that are no longer operating.
a listing of relays: https://nostr.io/api/v1/relays
I'm looking at kind 2 messages, relay recommendations
I read it the same way I read c variables about strings, with the "stir", as you say. no-stir
totally agree. at least for me, the point is not to pretent that twitter doesn't exist, but simply to remove it from the upstream position of routing attention.
nostr is a strangeloop. we will use nostr to build a better nostr.
I started "we are legion" as well, based on suggestions from nostr. a first for me. also rereading "Gödel, Escher, Bach"