{"type":"rich","version":"1.0","title":" wrote","author_name":"npub1jxjzmmfxafzanf2kvnggrwqnd7jw8x6xrp7kggvpqdmkw0ldmv4suztxhc","author_url":"https://yabu.me/npub1jxjzmmfxafzanf2kvnggrwqnd7jw8x6xrp7kggvpqdmkw0ldmv4suztxhc","provider_name":"njump","provider_url":"https://yabu.me","html":"\u003e secrets in unencrypted MMKV storage\nThis could probably be improved. We're taking it up, thanks for the report.\n\n\u003e - Cloudflare binary downloaded at runtime with no checksum? Why? That's a supply chain risk for every Umbrel self-hoster. \nVery much work in progress, we haven't announced the Umbrel integration anywhere yet and are still in development. For now we recommend not to use that project yet until we release our first Alpha version.\n\n\u003e Neo4j shipping with hardcoded password\nUser is encouraged to configure his setup when self-hosting. Don't open up your machine to the internet without understanding what your doing. No big difference to many other systems. A password change could be enforced, there is room for improvement, yes.\n\n\u003e - GCS backend with no auditable configuration surface? \nGCS is an implementation detail of one hosted deployment (Synonym), not a requirement of self-hosting. Our vision is to have many independent operators to run instances on infrastructure they control, using whatever platform fits their needs. We can provide deployment guidance, but operators ultimately control their own configuration. Real self-sovereignty comes from the ability to self-host or choose a host you trust, not from visibility into any particular operator’s production config. We may explore additional transparency and deployment documentation in the future.\n\n\u003e - you said users have a choice where their data is hosted. True for the homeserver. But is there a credible alternative to Synonym's Nexus for discoverability? Without it, content exists but nobody can find it. Self-hosting a homeserver without an accessible Nexus isn't a real credible exit for most users. \nDiscoverability does require indexing. A homeserver can host your data, but an app still needs some way to aggregate and process the data. Simple apps can often do that on the fly; For more complex apps it's a good idea to externalize that work into an asynchronous indexer, otherwise the user experience becomes slow or incomplete. That aggregator / indexer can be run anywhere. It could be self-hosted (even though that's not yet as trivial as we'd like it to be). For pubky.app that aggregator/indexer is called Nexus. any users may choose a managed Nexus because it is convenient, while others may prefer to run or use an alternative operator’s Nexus.\nMany people run their own Bitcoin node, but for indexing they still rely on 3rd-party-hosted block explorers, even though they have all the raw data locally, but they don't want to run the indexer themselves. Offering indexing for self-hosting as well as providing a well-run default seems like a fair deal to users. Do you think it should be done differently?\n\n\u003e These aren't philosophical objections to the vision of 'your' protocol. \nExactly, you pointed out implementation details in young projects that are still under active development, so perfect stability is not expected. What is your view on the broader picture, the fundamental protocol and vision?\n"}