How do sites prevent vanity URLs from colliding with future features ?
My answer to How do sites prevent vanity URLs from colliding with future features ? on Quora
For wildlifenearyou.com and djangopeople.net I used the same trick as described by others in this list—an enormous blacklist of everything I could possibly want to use for a future feature.
Lanyrd.com uses Twitter screen names for profile URLs, which means this trick doesn’t work—I don’t have any control over what Twitter allows people to register. As a result, our profile pages are http://lanyrd.com/people/simonw/—but we do redirect http://lanyrd.com/simonw as a shortcut, assuming it doesn’t collide with a URL already used by the site. We’re not really promoting that feature though as we don’t want people to link to it when we can’t guarantee that it will always work for their account (if you have a username that’s unlikely to clash with a site feature you should be fine though).More recent articles
- Lawyer cites fake cases invented by ChatGPT, judge is not amused - 27th May 2023
- llm, ttok and strip-tags - CLI tools for working with ChatGPT and other LLMs - 18th May 2023
- Delimiters won't save you from prompt injection - 11th May 2023
- Weeknotes: sqlite-utils 3.31, download-esm, Python in a sandbox - 10th May 2023
- Leaked Google document: "We Have No Moat, And Neither Does OpenAI" - 4th May 2023
- Midjourney 5.1 - 4th May 2023
- Prompt injection explained, with video, slides, and a transcript - 2nd May 2023
- download-esm: a tool for downloading ECMAScript modules - 2nd May 2023
- Let's be bear or bunny - 1st May 2023
- Weeknotes: Miscellaneous research into Rye, ChatGPT Code Interpreter and openai-to-sqlite - 1st May 2023