i mean... there's no new people and not much keepin em here aside from ideology. there's only so long a digital square can last with that yk?

skepticism is very important and i appreciate your efforts to shine light on this stuff! thank you, have a good one :skype_sun:

i have no choice but to follow my heart. i do not wear my heart on my sleeve, I Am My Heart. and if I don't follow her we shall both cease to exist

reticulum 🤞

Everything is on the DHT so can't you just have your own indexer/aggregator? Like sure even if the Nexus phones home and can filter stuff, what's stopping someone from forking and making their own for use with a client?

Yes, the nexus can act as a point of censorship, but so can any Nostr client too, they just need to filter certain pubkeys or content or whatever.

Even if the flagship Pubky app is censored to shit, you can still use other clients with other independent indexers, no?

Please let me know your thoughts :)

I do really like the ideas Pubky brings to the table like having full control of where your data lives with homeservers and PKARR, having the ability to index the global state with DHT, being able to use files instead of events, etc. Cool stuff!

But also things do feel a bit opaque. Seeing the homeserver code for a Google bucket config is a little worrisome, just because it is not stated if your data on the official Pubky homeserver you sign up with on the Pubky App is really just stored on Google or how that's managed.

The docs cover PKARR a lot but there doesn't seem to be many details about the PKARR relays that are needed to run the system. Are those censorship resistant even?

I am excited about decentralized protocols and I want to build with tools that give people the most freedoms and control over their data. I feel Pubky does right on a lot of Nostr's shortcomings, but I don't want to commit to building on Pubky without being confident in its direction and current standing.

What do you think?

Public stuff gets the most attention! also given network effects, it makes the most sense to get every user in one place, especially at the beginning.

Looking forward to what Pubky does for private stuff and how E2EE stuff on Pubky will work, esp with Pubky Noise https://pubky.org/explore/technologies/pubky-noise/

pretty sure the friction is just to sign up for Pubky's homeserver, not the protocol itself. Unfortunately, the homeserver implementation is just a rust package at the moment, but like john said, that is in the works!

he's spitting facts lowkey 😭😭