Rejected Autoconfirm IPs Instead of Accounts

[burgablob]

Hi! While I don't understand the technicalities of PS! too well, I understand that PS! works more with IP addresses than accounts. For example, roombans ban an IP instead of just the account (obviously a good thing) and this feature is also used to prevent double-dipping in giveaways in the Wifi chatroom. However, this isn't applied to the autoconfirming of accounts. It can get really annoying when you create a new account but have to toggle to another one to speak in a chatroom. It'd be awesome if IP addresses were autoconfirmed instead of individual accounts. I'm not 100% sure if this is viable, please let me know why if it isn't. Thanks in advance!

btw this is my first suggestion, please take it easy if I screwed something up :)

 

[Hecate]

It's viable, but it would be extremely annoying and I see little benefit.
It'd be annoying in that currently autoconfirmed status is stored on the loginserver - we'd have to do a db migration or store it elsewhere to tag ips.
It'd also be difficult to deal with in that spammers could use it to become autoconfirmed much more easily (only wait once instead of per account, which, given the point of autoconfirmed is to stop spamming, would defeat the purpose.)

 

[Annika]

If you truly own the second account, you can log in on your autoconfirmed name and then use /nick to switch to the new name while maintained autoconfirmed status.

We can't autoconfirm IP addresses because IPs and users don't have a 1:1 correlation: mobile data carriers typically give a user a new IP every few days, and someone who uses PS in multiple locations (home, work, school, mobile) will have a new IP in each one. Also, spammers could just use a public internet connection (which someone else would likely have autoconfirmed) to bypass autoconfirmed requirements.

(Mia's post speaks to the technical issues in implementing this, which I view as secondary to the fact that autoconfirming IPs just doesn't work.)

 

[burgablob]

It's viable, but it would be extremely annoying and I see little benefit.
It'd be annoying in that currently autoconfirmed status is stored on the loginserver - we'd have to do a db migration or store it elsewhere to tag ips.
It'd also be difficult to deal with in that spammers could use it to become autoconfirmed much more easily (only wait once instead of per account, which, given the point of autoconfirmed is to stop spamming, would defeat the purpose.)

I understand. I just thought that if a spammer was banned from PS!, it would ban their IP anyway, so getting autoconfirmed in a second account wouldn't help them at all.

 

[HoeenHero]

I understand. I just thought that if a spammer was banned from PS!, it would ban their IP anyway, so getting autoconfirmed in a second account wouldn't help them at all.

Bans don't last forever, autoconfirmed does though which is a major issue here.