Nathan of Guardian: > > > On Mon, Jul 11, 2016, at 08:46 AM, Hans-Christoph Steiner wrote: >> >> I'm implementing media support for F-Droid now, and one question I have >> is what we should use for the unique ID for each media file. With >> Android apps, it is easy: the "package name" is a requirement for being >> an Android app. A couple of quick thoughts: >> >> * use the hash of the media file as the unique ID, that guarantees >> uniqueness, but is not human readable and might hide when the same file >> has really tiny modifications like date metadata or something > > NameCoin / NameId attempt to address this, though it might be overkill: > https://namecoin.info/ https://nameid.org/?view=faq > > IPFS also has the Interplanetary Naming System: > https://github.com/ipfs/examples/tree/master/examples/ipns > https://ipfs.io/docs/ > >> * something else generated from some combo of >> title/filename/hash/creator/etc. > > I do think name + hash, or at least hash final octet of some sort, would > be a good in-between. > > ABCD1234.MyCoolPicture.jpg
To summarize our discussion in the Bazaar scrum, by default we can use the hash of the file as the unique ID. Then someone can optionally manually create and manage a unique ID for media as well as a version ID so that the media file will enable F-Droid's automatic handling of updates. .hc _______________________________________________ List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To unsubscribe, email: [email protected]
