Paul Frazee
Paul Frazee
@Frando yeah I think that's a fair point, we should give that some thought. Hypercores are having data structure identifiers added to them (DEP on the way) so it should...
> 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....
I appreciate the spitballing, but I'm a hard no on that idea. Adding other protocol mounts is a ton of added complexity we dont need to consider right now. Each...
@bnewbold you just articulated everything I've been thinking, including the potential approach of having the swarm-manager decide to join the swarm on not-found, or just prioritizing the subfeeds lower once...
We'll have to see what the performance looks like if we bubble the events.
> So, this would be at the hyperdrive level, not hyperdb, right? It appears that's the plan for now.
@mafintosh has been working on "strong" links with https://github.com/mafintosh/hypercore-strong-identifier which might be what you're looking for
@RangerMauve depends on whether you're just looking for a guarantee about what data you receive, or if you're also trying to get deduplication
@andrewosh that's a good observation about versioning. I suppose it's not too different than package.json. If you consistently put `@latest` on your deps, you'd get the same kind of issue...
Yeah this is an interesting idea. @mafintosh has been exploring similar kinds of information in the Hyperswarm DHT to help with connection priorities. For this spec I'd be curious to...