Hardcoded Synonym relay nodes? Default 'admin' password for homeserver operators? Rofl.

GitHub

pubky-core/pubky-homeserver/src/data_directory/config.default.toml at main · pubky/pubky-core

An open protocol for per-public-key backends for censorship resistant web applications. - pubky/pubky-core

line 24: admin_password = "admin" line 34: dht_relay_nodes = ["https://pkarr.pubky.app", "https://pkarr.pubky.org"]

GitHub

pubky-core/pubky-homeserver/src/admin_server/auth_middleware.rs at main · pubky/pubky-core

An open protocol for per-public-key backends for censorship resistant web applications. - pubky/pubky-core

Users of pubky.app have zero access to any of this. They're on Synonym's homeserver, Synonym's config, Synonym's relay nodes. Self-hosters can change it, that is if they are aware. Every homeserver deployed with default config routes DHT traffic through Synonym-controlled servers. A sovereignty protocol with Synonym as the default DHT relay is a structural centralization point baked into the defaults. Again, happy to be wrong or mistaken here. Just easy to spot issues at first glance.