4 ms·
I guess I don't find: "just use a permalink" without a weighing the pros and cons. I guess I weirdly find descriptive links valuable. I could easily do both, b
by scoofy 4y ago
I guess I don't find: "just use a permalink" without a weighing the pros and cons.
I guess I weirdly find descriptive links valuable. I could easily do both, but I think just recording old links is probably an option in the long run. I just think people should be able to click on a URL and know where they're probably going.
This still doesn't explain what to do when DB entries are destroyed.
- Aachen 4y agoNeither of the examples I gave obfuscate links when making permalinks. https://de.m.wikipedia.org/w/?title=Valheim&oldid=231146307 https://de.m.wikipedia.org/w/?title=Valheim&oldid=231146307 page title is still in the link, in addition to the revision ID https://github.com/git/git/blob/d15644fe0226af7ffc874572d968598564a230dd/block-sha1/sha1.c https://github.com/git/git/blob/d15644fe0226af7ffc874572d968... also says exactly where you're going, it just replaces the branch master or whatever with the commit. You still see the repository and file path. Permalinks don't have to be obfuscated. The downside I would rather mention is that the link doesn't update to newer revisions if improvements are made. It's not like an LTS version where fixes are still applied but no changes (I guess because every change is supposed to be an improvement to the topic, but yeah, not always).
- scoofy 4y agoHuh... yea, i haven't really thought about doing urls via argument. I guess i just much prefer a single path. You've really given me something to think about though.