5 ms·
But it's the same problem all over again, spammers would get an id, auth, then spam. Anti spams are about detecting whether activities are spam. Binding an id
by hirako2000 3y ago
But it's the same problem all over again, spammers would get an id, auth, then spam.
Anti spams are about detecting whether activities are spam.
Binding an identity, is the naive mechanism that makes us think spam wouldn't happen. All it does is say ok we know it's pug35372 that teared the linens apart.
We can put all measures to authenticate users, won't makes them not potentially bots running havoc right after a manual authentication.
There are even farms, manually created accounts by gig seekers who would fill forms, email and phone number verification for less than a dollar.
- worldsayshi 3y agoAs I mentioned the exchanged token could include a number of policies, like rate limits. But I expect there could be more sophisticated policies as well. The service could send ban or lockout requests to the eId authority so that a misbehaving real life user could be locked out from the service even though the service doesn't know who they are (irl). I would guess it could even be designed so that the authority doesn't know which services a given user has been banned from either. And all the service would need to know is "This user has violated policy X at <timestamp>".
- hirako2000 3y agoI see how issuing a token has its advantages, thanks.