Beaker support for DEP-0005: DNS

[benhylau]

Using the hyper:// scheme in Beaker, it currently does not resolve my DNS TXT record. What is the expected behaviour?

I have this TXT record set according to DEP-0005: DNS:

$ dig staging.compost.digital TXT +short
"datkey=12429c38e6a0f8938328763bcbc34a3b8129d21083a67b6be7e6f96cf26e2f97"

The value of 12429c38e6a0f8938328763bcbc34a3b8129d21083a67b6be7e6f96cf26e2f97 is a hyper key, not a dat. In Beaker:

• hyper://12429c38e6a0f8938328763bcbc34a3b8129d21083a67b6be7e6f96cf26e2f97/ loads fine
• hyper://staging.compost.digital -> 500 (this loads fine on Agregore)
• dat://staging.compost.digital loading forever

What is the expected behaviour? My suggestion is either to behave the same as Agregore, or read a hyperkey in the same TXT record.

[benhylau]

Didn't realize this is already being discussed here. Feel free to close.