We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use https://github.com/jbenet/js-multihash to generate ids.
Shortening to 128 bits provides 2^64 possible hashes, so should be safe for avoiding collisions:
blokdust.com?c=QmbqZNSUkf99BxpY
Use https://github.com/hildjj/node-cbor to compress the files for storage as it will be compatible with IPLD.
Use IPLD syntax for the Parent property:
"Parent": { "@link": "QmAAA...AAA" }
Q: If shortened ids are used, how do you access the full id for the parent property? Can't store it in the json itself as this alters the hash!
A: Redirect to the full id.
Q: Keep using LZW to compress over the wire? Browser CBOR implementation is problematic due to needing to send a byte array instead of a string.
The text was updated successfully, but these errors were encountered:
Look at using S3 prefix filtering http://docs.aws.amazon.com/AmazonS3/latest/dev/ListingKeysHierarchy.html
Sorry, something went wrong.
No branches or pull requests
Use https://github.com/jbenet/js-multihash to generate ids.
Shortening to 128 bits provides 2^64 possible hashes, so should be safe for avoiding collisions:
Use https://github.com/hildjj/node-cbor to compress the files for storage as it will be compatible with IPLD.
Use IPLD syntax for the Parent property:
"Parent": { "@link": "QmAAA...AAA" }
Q: If shortened ids are used, how do you access the full id for the parent property? Can't store it in the json itself as this alters the hash!
A: Redirect to the full id.
Q: Keep using LZW to compress over the wire? Browser CBOR implementation is problematic due to needing to send a byte array instead of a string.
The text was updated successfully, but these errors were encountered: