How do sites prevent vanity URLs from colliding with future features ?
13th October 2010
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
- llamafile is the new best way to run a LLM on your own computer - 29th November 2023
- Prompt injection explained, November 2023 edition - 27th November 2023
- I'm on the Newsroom Robots podcast, with thoughts on the OpenAI board - 25th November 2023
- Weeknotes: DevDay, GitHub Universe, OpenAI chaos - 22nd November 2023
- Deciphering clues in a news article to understand how it was reported - 22nd November 2023
- Exploring GPTs: ChatGPT in a trench coat? - 15th November 2023
- Financial sustainability for open source projects at GitHub Universe - 10th November 2023
- ospeak: a CLI tool for speaking text in the terminal via OpenAI - 7th November 2023
- DALL-E 3, GPT4All, PMTiles, sqlite-migrate, datasette-edit-schema - 30th October 2023
- Now add a walrus: Prompt engineering in DALL-E 3 - 26th October 2023