Closed phaseOne closed 10 years ago
Excellent idea. I didn't realize URLs were still case sensitive...
I'll start working on this now.
I'll probably help out with a couple of things around here when I have time in the coming weeks. It's a cool project.
So I have 87 collisions for moving everyone to case insensitive names. How should I handle these?
I could send a message to all of the conflicting names and ask one of them to change it, I suppose. What do I do when neither person responds? Delete the account that hasn't been used the longest?
Maybe the best idea would be to let them know that their URL would be changed to a temporary URL in 2 weeks, and they could then change it (first come, first serve) after the switch. I suspect that some of these are actually duplicates that people made when they realized that it was case-sensitive.
-- Evan Bovie
On Monday, November 11, 2013 at 4:21 PM, Christian Genco wrote:
So I have 87 collisions for moving everyone to case insensitive names. How should I handle these? I could send a message to all of the conflicting names and ask one of them to change it, I suppose. What do I do when neither person responds? Delete the account that hasn't been used the longest?
— Reply to this email directly or view it on GitHub (https://github.com/christiangenco/dbinbox/issues/49#issuecomment-28240066).
All usernames, with the exception of 139 special cases of collisions, are now case insensitive.
For those cases, case does matter (lol puns). I'll be building a better admin panel that will allow for changing of username/display name as my next task. After I get that done I'll be sending a message to each of these accounts recommending they change their name.
Aside: my production code has now diverged significantly with the code on Github, primarily in preparation for handling financial data when I start charging for increased upload size and pro features. I'd like to make this public fork easier to set up as a single instance on Heroku by just changing the dropbox API key in a config file.
Since URLs are case-insensitive the majority of the time, it would probably be a good idea to make that the default here. It can cause confusion for users (especially the less-technically inclined).
Perhaps a checkbox in the settings to make the URL case-sensitive could be added, but it's probably at least a good idea to keep case-_in_sensitivity the default for new (and depending on how you've written the database) old accounts.