so, i assume i can't just run a pubky relay and serve a client from some website, but need to bend the knee to the carvalho entity to be permitted to use his exclusive fucking gay not self sovereign or particularly open, consensus containing retardation
how about, go fuck yourself, i don't need anyone's permission to run a relay and host a fork of jumble.
It's just more complex than that. There's no relay model for the events, because it does not prescribe atomic events, but rather leverages pkdns (a separate application) to assign keys in place of DNS. So like you can host your website at a long string that is published to DHT. That is the censorship-resistant aspect to the PK ecosystem. This part also requires a browser or OS allowance to resolve PKDNS websites.
Then, you're correct in that "the live version of Pubky" is invitation-only, but that extends to the application. So anyone running an instance of the Pubky app can provide invite codes to their own instance and users.
I haven't gotten my instance running yet but there is at least one other instance of the Pubky app running from someone who doesn't work for Synonym.
Part of the PK Stack includes a Nexus which handles routing and indexing if I'm not mistaken.
I would be interested to hear your real opinion on its architecture. At this point I want to shove a nostr relay inside of Pubky just to fuck with people. But priorities.
i already said:
relay model solves the routing problem of the internet in the simplest way
a DHT is a consensus that limits what i can do with the protocol
and apparently, the consensus allows you to exclude people from using it
what's not to love?
DHT is not a consensus, but if they can exclude references from the DHT then they have a consensus using the DHT.
the benefit of nostr's simple protocol is it doesn't lock you into a consensus. different tasks have different requirements. a private, business server doesn't have the same requirements as an open, spam-protected public server.
Because you are conflating PKDNS with a DHT-driven protocol. The events published in a homeserver don't populate across DHT at all. I haven't even looked at Pubky's protocol because it doesn't really matter in the context, since it doesn't operate like nostr in that capacity. The protocol is a modular piece of the stack.
You can also just run Pubky without pkdns and then boom you're dht-free and also just operating on clearnet DNS.
98% sure about this.
right, so why bother when there is so much nostr code already written to do this?
Nostr fails me lots but I use both and will continue to use both until I find something or create something that adequately meets my demands. I want to integrate NWC into Pubky if not a whole nostr relay so my homeserver can actually serve me instead of me trying to juggle a bunch of nostr relays.
NWC is a nostr protocol and is built around the use of a nostr relay as a rendezvous point between the wallet service (connected to the LN server), the relay, and the NWC RPC client which talks to the wallet service. your proposed integration won't work with a home service unless you have a VPS tunnel from an internet routable address with the wallet service to your home relay (like cody's pigeon service, or like how i have wireguard and lerproxy to run wss://test.mleku.dev on my dev box
Homeserver is a Pubky term. 😃☁️
