18·
1 year agoPersonally I don’t have any problems with it (if that was directed at me) - I’ve added 418 as “unhandled exception code” response to a bunch of applications, so I can easily differentiate whether my application is throwing an error, or whether it’s some middleware gateway AWS io-thing
I was just curious what OP thought about it, since in the early days it wasn’t uncommon to add goofs or easter-eggs into software, but nowadays not done so much… and apparently the “HTTP Working Group” doesn’t like it either… So I was curious whether OP though in hindsight whether it should’ve been added or not
[From the github comment]
If the tags are just kinda “plain old hashtags” - and not something cool like I mentioned in the previous post 😉 -
Possibly you could have a look at how Gazelle handles tags, where it’s just a voting system. For example, this is “Kanye West” https://i.imgur.com/adTe4t8.png - then tags are no longer a boolean yes/no system, but a user-voted system. And then it’s no longer a moderation concern to have to correct tags, and you don’t need “User privileges” to manage the tags either.
It’s just a pretty chaotic system though - you might still want moderators to remove bad tags and/or ban users from creating tags if they’re always adding nonsense.
Could be some point based system like Stackoverflow - users with n points can vote on existing tags, users with n+ points can add their own new tags