Would using the various GitHub repositories not work for references?

f'ck them, it's easier to put a 'wiki' on my own domain, than waste time with them..

apparently, they review every new submission (there is strict rules when submitting) and there is queue..

"To qualify for a Wikipedia article, a subject must meet Wikipedia's standards of notability. Articles whose subjects fail to meet this requirement will be merged, redirected, or even deleted. "

I'm the author of gossip, a desktop client not a mobile app, but I have someting to say on this. Gossip downloads only about 4MB when I start it in the morning and run it for an hour. Since that is several orders of magnitude less than some other clients, I thought I'd make a list as to why:

1. Duplicate Events - many clients subscribe to the same filters on all of the "read" relays. So if a person has 10 read relays, they get each event 10 times. They could subscribe in a way that only gets N copies, where N is set in some setting somewhere (gossip defaults to 2 or 3).

2. Not Dynamically Connecting to Relays - when clients don't dynamically connect to the 'write' relays of whoever you follow, users are incentivized to add lots and lots of relays as a hack to try to get that content, aggrevating issue 1. If clients smartly went to the write relays (based on relay lists), all of the content a user has subscribed to would arrive (in best case scenario) and users would no longer feel the need to add massive numbers of read relays.

3. Counting how many followers you have is expensive. Kind-3 contact lists are long, and you need to pull one for each follower to make such a count. Especially if done across many relays (where the same ones are pulled multiple times, once per relay), this could be 10-20 MB on it's own. Then how often is the client triggered to recount?

4. Downloading of avatars: gossip caches these so it doesn't have to re-download them. Any client that uses an IMG tag and doesn't have a browser caching is probably downloading these over and over, at worst case every time a post scrolls into view.

5. Content images and content web page pre-rendering: This can be very expensive, but is probably unavoidable on rich UI clients. Gossip is a "poor" UI client, without any images or prerendered links (it just shows links that you can click on to open your browser). But with caching, repeated downloading of the same thing can be avoided.

6. Re-checking of NIP-05 could be done periodically, perhaps daily if it failed or every 2 weeks if it passed, probably the worst strategy is every time a post scrolls into view.

There are probably others.

That’s why I think we need fair sampling.

You can actually do that for the past to a certain extent.

Books used to be expensive to create, and the most important ones were made to be even more expensive.

Before print you if you just focused on the most beautiful books (in terms of cover, illuminations, illustrations) you’d focusing on the information people thought valuable enough to spend resources to attach huge amounts of proof-of-work to it.

You could read just 20 books in your whole life and be very well informed abou all *relevant* events of history— and you didn’t need to trust your social graph.

People usually get it completely wrong about the Church restricting knowledge during the Middle Ages — it was the other way around, they were tirelessly working to preserve information, in a mostly decentralized manner.

It was just *after* the printing press that censorship become a relevant problem — because they tried to keep the world from changing by fiat, which was doomed to fail and end in corruption.

Looks like you are not in the correct folder. Change into the nostream directory

I spoke too soon. In nostream setup so in tmux ./sripts/start

no such file or directory. Google only suggests that no tmux is running. hmmmm

#[0] ?

All I'm saying is zaps are a step backward re privacy.

Compared to LN by itself (LNURL or LN Address) which is more private by default.

I think that’s sad.

The Internet can connect all humans on Earth. It was supposed to.

Yet we keep looking for ways to be live in our tiny little echo chambers.

If people have to go out of their way to hear from those outside their circle they won’t.

And if they see all info filtered by a group — that group will eventually use that fact against them.

Instead of finding solutions we keep inventing new ways of reproducing the same old problems.

Yes, relays are confusing. For example, if I am part of just one relay and that some members are part of another relay, does that mean that we cannot communicate?

What about spam? Why would some spam be on certain relay only? Does that mean that non-spam messages are also limited to certain relays?

🤔

Let the user know what relays are being used and for what, let the user decide, make it not a hassle.

No, they have the power to publicly cryptographically document who is supporting dissent

Zaps on Nostr have the power to monetize dissent.