Avatar
Chiarakaparos
f8bb809cec84e3f14159f77ef865dff21d3348bb22e09eb3c30eeb9c0b7a573e

How the hell is there already spaces type stuff up and running. This moves so fast i cant keep up, how the hell is there going to be any centralized social media companies left in a couple of years ๐Ÿ˜‚

Funny how twitter is a hostile environment and nostr is the complete opposite. How easily we are manipulated.

The beauty of it is if someone mines according to other rules they can mine all the want. The network will just ignore them and go on with the day.

Its like language almost. You are free to speak mumbojumbo but nobody will listen. Everyone who speak the same form the network

No. Miners are also nodes but they build blocks too. Nodes only check so everything follow rules. If not they ignore.

Like all other things its traded against goods and services

Replying to Avatar Derek Ross

**Welcome new Nostriches! How do you find people on Nostr?**

Over the past few days I've seen a lot of people ask this question. They join Nostr, because they near how it's the place to be, the hear it's where the signal is at, but when they get here, they don't hear anything! How do you find people on Nostr? How do you find the signal that we're always talking about?

**Use pre-built lists of power users and signal boosters.**

* https://snort.social/new - This Nostr client comes with a list of Nostr power users to keep your feed always busy and allows you to search for and easily follow all of your Twitter friends.

* https://bitcoinnostr.com - This website consists of Nostr Users that are Bitcoiners. You'll recognize them from Bitcoin Twitter.

* https://nostr.directory - This website contains a vast directory of Twitter, Mastodon, and Telegram users that have connected their Nostr public keys.

* https://nostrplebs.com/directory - On this website directory you'll find familiar faces from Bitcoin Twitter and plenty new faces from Nostr. (Shameles Plug: I founded this Nostr services provider.)

**Find users inside your Nostr client.**

* Hashtags - If your client supports hashtags, I recommend you take a look at #Plebchain. This hashtag comes with plenty of Bitcoin Plebs and Nostr Plebs looking to connect with one another.

* Global Feed - Many clients include the "Global Feed" which allows you to easily find people that you're not already following. (Beware of spam.)

* Global Channel - If your client supports channels, you can check out the Global Channel in your client and new find people looking to chat and learn about Nostr together.

Do you have another way to find Nostr users? Shill it below so that others can find one another. Thanks!

#[0]

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.

#[0]

03:00. Gn but hard to stop. ๐Ÿ˜‚

So exited i forgot to say. Thank you