I promise you that it’s not. Maybe I’ll rethink this somehow, I just am trying to protect against bot traffic. Tying activity to a specific user makes it easy to ban access is all.
[1] I'd go as far as to say I don't think "bots" are a thing worth worrying about at all early on because "bots" are a reaction to an opportunity to extract value from a service. For example, if a million people use your website, then spammers have an incentive... if nobody uses your website (or very few people) then there's no incentive. Spam is a problem you can deal with in future, if it ever happens, it's not something to worry about today, as long as you design your system such that if spam does happen, it's a headache for you, not users (i.e: a moderation queue). If you make the user experience bad to prevent hypothetical spam, well, the bots have ruined your website without even knowing it exists!
For write-access, some kind of identifier is sensible.
Also the View Rates pages fucks up the back button — that’s not very considerate of you
Fixed the back button, I think. Sorry all - one man show here, really not trying to be malicious and iterating as fast as I can!