But then it is the developers fault, never management
Tanoh
Only issue I see is that the 8 chars required is very short and easy to brute force. You would hope that people would go for the recommended instead, but doubt it.
Re: Downvote bots. I can't say they're necessarily bots, but my instance has scripts that flag accounts that exclusively give out downvotes and then bans them. That's about the best I can do, at present, to counter those for my users.
It is usually not a good idea to specify what your exact metrics are for a ban. A bad actor could see that and then get around it by randomly upvoting something every now and then.
The same goes for pretty much everything in life, not just games. It might suck in the short term, but just don't put up with friends/partners/jobs you don't like. Make a change
There is also the risk of homograph attacks. The link below is for domain name encoding via IDN, but the same applies to usernames. You could easily impersonate another user by having chars that look similar.
Sure, but even if they started tomorrow it would probably be years before it even could be considered experimental outside of the most daring early adaptors.
Having a combability layer is not ideal but it would mean they could have something worker for more users faster and at the same time see which modules/drivers they should focus on.
Sometimes they can be challenging or overgrown, so you have to know what you're doing and be prepared to turn back if necessary, but I owe a lot of truly incredible experiences to this app.
Since it uses OpenStreetMap you should consider updating it for others later. Don't think you can do it in Organic, but it can be as simple as in a browser adding a note to a trail about what state it is in.
And ethernet port!
Recruiters can't see the difference! (Ok, not all but a worrying high percentage)
"Thread closed due to inactivity."
Subscription based teeth?
Simple answer: length.
Two chars look a lot better than something with more chars, and all two chars TLD are ccTLDs.