Paul Frazee

> The main problem is that the draft spec is broken by design. Please respect the positions of other people during a disagreement. We're discussing tradeoffs and it's clear that...

@dnebdal My resistance to the spec change isn't just the switching cost. I'm not super excited about the aesthetics and UX of prepending special subdomains. Given that the `.well-known` solution...

> For me, personally, setting up DNS records are somewhat easier that dealing with the .well-known stuff most of the time, since most DNS providers have simple interfaces you can...

@da2x okay appreciate that write-up. I've been talking about this with @mafintosh and we're going to give it another look. > No one sees these DNS records, though. A publisher...

Well let's see... The wire protocol exchanges hypercore blocks, not files. As a result, peers don't explain what files they're trying to fetch when they communicate with each other. They...

@martinheidegger Correct me if I'm wrong, but I think, for the most part, that's how my one-way-mounts solution works.

@martinheidegger What's the upside of introducing a different hypercore datastructure than hyperdrive? If you stick with hyperdrive, you avoid having to create a niche solution.

@martinheidegger You're free to build any data structure you want on hypercore, but you're going to have to get that structure adopted widely if you want it solve the problem....

@karissa you're just losing wider ecosystem compatibility. If the situation really is niche, then you can do that, but I think you're losing some of the benefits of dat. In...

@karissa You could probably do that via a wire-protocol extension message. It's got some extra overhead but if it was only turned on for dats doing this style of on-demand...