bnewbold
bnewbold
The session and ephemeral messaging extensions are mostly what i'm responding to, but here are some more specific use cases: - requesting write-access to a public multi-writer hyperdb feed (eg,...
A couple notes: - does the "don't use apex domains" wisdom hold for `.well-known` static files, or is it oriented towards high-traffic services redirecting to a third party? - what...
As a weakly held, somewhat subjective opinion, I think we should err on the side of "keeping it simple" by not specifying maximum lengths for every string and field at...
I think it would be good to leave a mention (sort of a learning and context pointer) that higher-level formats make use of multiple hypercores, not just one. I know...
An appealing possible feature of this would be that multi-writer permissions could be scoped to prefixes, without needing to make the multi-writer implementation more complex than it already is. Eg,...
A spitball thought: if we had an excellent fuse (userspace filesystem mounting) implementation, would we even need this? or, staying in some non-operating-system API, should we explode the generality here...
Another thought: re-using the existing connection for additional hypercore feeds (instead of doing a separate swarm) could result in discovery and history problems in some cases. Eg: 1. hyperdrive ABC...
> I feel like there are various recommendations missing from the dat project This was intentional. I don't think we should be over prescriptive; folks should be able to adapt...
Maybe "widely used" On March 20, 2018 2:29:29 PM PDT, Martin Heidegger wrote: >martinheidegger commented on this pull request. > > > >> + >+Type: Standard >+ >+Status: Undefined (as...