3 ms·
> The owner can reassign any names they want. Then maybe they should include that in ToS, See how many signup.
by qazpot 7y ago
> The owner can reassign any names they want.
Then maybe they should include that in ToS, See how many signup.
- edent 7y agoAs I point out in my post, they often do. For example: Telegram - https://telegram.org/faq#usernames-and-t-me https://telegram.org/faq#usernames-and-t-me NPM - https://www.npmjs.com/policies/disputes https://www.npmjs.com/policies/disputes Github - https://help.github.com/en/articles/name-squatting-policy https://help.github.com/en/articles/name-squatting-policy Most sites have similar wording.
- fxleach 7y agoIt's strange that you link to these articles to somehow justify the shitty thing you did, and they're straight out saying that you should _not_ be doing what you're doing. The first paragraph of your post... "I quite often sign up to things just to snag the name." GitHub: "GitHub account name squatting is prohibited." Telegram: "we reserve the right to recall usernames assigned to unused bots and channels, as well as openly squatted usernames" NPM: "Don't squat on package names, user names or organization names." Dick move.
- TheCraiggers 7y agoI would be shocked if something as mundane as that would be the top of any sane person's worries after reading the average ToS (and actually understanding it). They often already claim ownership over every single byte you send them, disavow any responsibility for their actions, and in the cases where local laws force them to be responsible, will force arbitration on you. Half of my digital life would be lost right now if I did a $1 chargeback against Google and there is literally nothing I could do about it aside from proactive things like leaving their platform beforehand.