How can a lottery not be inclusive? It is the most inclusive of all methods.
Why should you move your ass?
"Election activity" is just scams, lies, corruption and money wasted. Why do you like that?
The FNF has just deployed microbounties to #[0], #[3], #[2] and #[1] for their arduous work in advancing the cause of Nostr.
See all the information at https://docs.google.com/document/d/10xKQIO969GoNnAEnoMgJky69lG-_TslnqO4uIfioi1Y.
I've been talking to some Nostr software developers about setting up a global board for bounties to specific contributions to these clients at https://github.com/orgs/nostr-protocol/projects/2?query=is%3Aopen+sort%3Aupdated-desc, so that could be the next step.
Kinda like https://github.com/users/Reckless-Satoshi/projects/2/views/5, which I am told has been working very well.
I am not fully convinced this will work, but maybe it is worth trying. What do you think?
There were many instances of representatives being selected by lot in Ancient Greece. It is definitely a much better idea than voting.
There is also that story of the Napoleon of Notting Hill.
The FNF has just deployed microbounties to #[0], #[3], #[2] and #[1] for their arduous work in advancing the cause of Nostr.
See all the information at https://docs.google.com/document/d/10xKQIO969GoNnAEnoMgJky69lG-_TslnqO4uIfioi1Y.
I believe it also doesn't show in the feed. Put since everybody is replying to that deleted note it is easy to navigate to it.
I think this is all happening because of that Nostr November sacrifice we collectively did (by "we" I mean a group of 5 or 6 weirdos).
Send the commit link or id too, please!
Deleted note view on https://github.com/mikedilger/gossip: 
#[0]'s public key POW: #[1]
I think he is intending to keep this key for a long time.
What was the NIP system introduced for?
#[1] #[0]
What is that?
fake
It is down right now, but would that work? Most clients are not reading from it. And the ones that were, https://astral.ninja/, I think, were not doing it in a smart way.
In fact it is down because it was getting hundreds of queries per minute all day every day even though it only had a dozen posts from a handful of pubkeys in it.
Each relay can have a different approach, the possibilities are endless.
https://github.com/nostr-protocol/nips/issues/177#issuecomment-1396842744
My old client only included the last 4 "p" tags from the previous notes, I think, it didn't copy all to prevent this kind of flooding.
NIP-10 (https://github.com/nostr-protocol/nips/blob/master/10.md) tell us how to manage replies. If a post is a reply the client can clearly identify the event and so the author; in my view only this one should receive a notification in the "strict feed".
The open feed could include all notification related to the root or, if the client is smart, only from the post I replied to, so the sub branch.
A tagging mechanism require users attention, and users are lazy (I daily struggle with users that cannot use email carbon copy properly...), I dubt it will work. Perhaps a personal mute thread/branch function can be useful, but would be a pure client implementation.
#[3] #[4] #[5] #[6] #[7] #[8] #[9] #[10]
ideas?
Each client has to decide their own policy. Each user will have different preferences.