@benhamill for opaque identifiers, my preference is a short Crockford Base32 number <https://www.crockford.com/base32.html> with checksum to catch transcription errors, but i can’t recommend tooling for keeping track of this (or a longer correct-horse-battery-staple kind)
if you’re namespacing these identifiers with domains and dates (as tag: / urn:fdc: requires), the problem of preventing collisions can at least be made pretty small
@benhamill don't make a pseudo-URI, make a tag: URI or urn:fdc: URI, which is the same thing but not pseudo-
Administrator / Public Relations for GlitchCat. Not actually glitchy, nor a cat. I wrote the rules for this instance.
“Constitutionally incapable of not going hard” — @aescling
“Fedi Cassandra” – @Satsuma
I HAVE EXPERIENCE IN THINGS. YOU CAN JUST @ ME.
I work for a library but I post about Zelda fanfiction.