You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When looking-up dns-entries-over-https (DOH) we are running into the issue that we have to trust the servers, which are hosted by google/cloudflare at the moment as they can handle any load (more servers can be found here - though they may not support json).
With this in mind I am wondering to "offload" the name lookup for decentralized names to a federated service that behaves equally but reduces complexity by doing things like the .well-known lookups, conflict resolution (multiple entries) and decentralized lookups (etherns, ...).
This way we can serve the same (possibly better) performance than we can get with a simple DoH lookup, while at the same time supporting decentralization.
The text was updated successfully, but these errors were encountered:
The upkeep of the service(s) is conceptually equal to dns-over-https, aka. google/cloudflare. This would not change that particular problem. It should work in a way that it would only work as optional speed-up for operations that can happen on your device as well. (like: shared cache, which is what dns-over-https is to me as well in a way.)
When looking-up dns-entries-over-https (DOH) we are running into the issue that we have to trust the servers, which are hosted by google/cloudflare at the moment as they can handle any load (more servers can be found here - though they may not support json).
With this in mind I am wondering to "offload" the name lookup for decentralized names to a federated service that behaves equally but reduces complexity by doing things like the
.well-known
lookups, conflict resolution (multiple entries) and decentralized lookups (etherns, ...).This way we can serve the same (possibly better) performance than we can get with a simple DoH lookup, while at the same time supporting decentralization.
The text was updated successfully, but these errors were encountered: