Volker Mische

@Ericson2314 This PR has been stale for a while, so I want to make sure you're not blocked. As the discussion at https://github.com/multiformats/multicodec/issues/204 shows, there still need to be things...

Thanks @Ericson2314 for being so patient and working together on that. I really hope we find a good solution for maximum interoperability for all systems involved.

Sorry for the last comment. I wasn't fully concentrated and though we are about to merge this PR, but the e-mail I got was about https://github.com/multiformats/multicodec/pull/207, which I already approved...

And even more confusion, so I'd prefer merging #207, but not merging this one as mentioned above.

Finally there's a recording of the talk I gave at the global FOSS4G 2018: https://youtu.be/rpx3kmpUwQI It contains a demo of storing raster tiles in IPFS.

@am2222 If you want to store only points which are lat/lon then you could also look into https://en.wikipedia.org/wiki/Geohash. I personally prefer using R-trees for every geo related thing I do...

@am2222 So far I haven't spent much time thinking about how to store R-trees in IPFS/IPLD. Coming from the database world, I currently think that local secondary indexes would be...

@JoranBeaufort I agree that those predefined hashing could make sense. Though I don't really have much experience with those as they were too limited for the use cases I had.

Thanks @rvagg for digging into previous PRs and showcase the discussions we had there. For me what those cases have in common is "I want to distinguish things without looking...

> Unless there's a bug, it first loads the already-assigned numbers. Then, for all _new_ mime types, it assigns increasing (unique) codes. Oh I missed that when I read the...