Avatar
Andrew
b17c59874dc05d7f6ec975bce04770c8b7fa9d37f3ad0096fdb76c9385d68928
Software Engineer by day, aspiring beet farmer by night. ☦️💻⚽🏥📷📈💪☕️🇺🇸🇪🇬 Things I like: - #P2P/#decentralized/#opensource stuff - #History (esp Rome/Greece/Egypt) - #Transit oriented city design - #Gadgets/#ElectricVehicles/#Solar Power - #Space exploration - #Videogames (especially #GTA) Things I've Built: - Agora: Follow your favorite topics across Mastodon, Bluesky, Nostr, and Threads https://agorasocial.app - Chronicl: Decentralized web archiver that distributes archives across Nostr relays https://chronicl.vercel.app/ “Egyptians are twisted and bitter people with a sense of humor” - Roman poet Theocritus

Sweet! Yeah I'm super intrigued by the caching service, lots of room for improvement when it comes to the performance/efficiency of the nostr network of relays.

Given the clarifications, I'd now classify it as Medium Decentralized only because of the (by definition) centralized caching service in place of NIP-65/Gossip. Although I can definitely see the performance advantages of going with the caching route.

All of the above! Yellow was my favorite

NordVPN library and client code open-sourced, good stuff! #opensource #vpn #privacy

https://github.com/NordSecurity

Replying to Avatar Susiebdds

I do, that stuff gives me the heebie jeebies

Agreed! It’s in the best interests of the ecosystem to continue to improve the protocol so that centralized solutions are less necessary and even inferior to the decentralized solution to whatever problem is being solved.

Creating NIP-65/Gossip was the first half of the equation for keeping the relay load evenly distributed. Clients implementing it is an equally important second half!

That's why I left out Plebstr and Current, though I was conflicted with Nostrgram because of that

If you were to include censorship resistance in the definition, which would you say are currently the most *decentralized* Nostr clients, and the least *decentralized* clients?

If I were to break up the clients into different "classes", this is how I'd group them:

**Most decentralized**

(direct connections to relays, no algorithmic filtering, uses NIP-65/Gossip model to prevent bunching up of users in a handful of major relays):

- Gossip

- Coracle

- Snort (gossip feature being tested here: https://relay-lb.snort-social.pages.dev/posts)

- Nostros

**Medium decentralized**

(direct connections to relays, no algorithmic filtering, but prone to bunching up of users in a handful of major relays)

- Damus

- Amethyst

- Iris

- Nozzle

- Blockcore Notes

- Nostrid

**Less decentralized**

(Indirect connections to relays through a centralized aggregator and/or mixed with direct connections, no algorithmic filtering, prone to bunching up of users in a handful of major relays)

- Nostrgram

- Broadcstr

**Least decentralized**

(Indirect connection to relays through a centralized aggregator, algorithmic filtering of some feeds, prone to bunching up of users in a handful of major relays)

- Primal

- Member.cash

- Minds

It's because from what I can see, https://coracle.social is the landing page while https://app.coracle.social is the actual webapp client. Makes your life easier to change your bookmark to that 2nd url.

You were probably called a troll because of your weird obsession with mentioning your hatred of Jews in every other thread 😂

Especially as more and more clients reach feature parity for the fundamentals and differentiate themselves on more niche/specific features and qualities.

Though the open nature of the protocol makes the switching costs of changing clients significantly lower than with a centralized model, or a semi-decentralized model like ActivityPub.

Replying to Avatar isabella

🧸

Here I am trying to figure out what country this is, since the US usually calls them "restrooms" or "bathrooms" and UK labels it WC. 😂

As in a list of which NIPs each client supports?