Profiles with censored=1 should not be updated / unblocked by cron_sync.php
Quix0r opened this issue · comments
If cron_sync.php runs, all accounts got unblocked. This should not happen as this makes anti-spam measurements unpractical.
Where is censored set in the first place? What does it affect? Just display in the public directory?
Table profile, it will effectively hide the profile from the list.
Ok thanks.
Anyone could flag a profile in the directory, for being nsfw or dead, and then the directory admin could delete/censor those profiles from the directory node.
Can you flag them in the current directory?
I mean the censored flag got reset after sync ran.
And where is the flag button?
You tell me, I've never seen the flag button.
I guess somebody(TM) removed it for aesthetics and hopefully planned to include it back later on but then lost track of the issue. It was a simple interface, but at least one could report profiles and the admin of the directory could review those reports.
I've seen this in the code, with admin users able to log in to the directory and review the flagged accounts, but it seemed like old code.
It was actively used code till the layout switch. Every time I logged into the old directory there were some accounts flagged for review.
Since I can't log in into the new directory, there aren't any flagged accounts anymore!
Which is not really a satisfactory situation for the vanishing of a useful and used function TBH But I'll close my eyes and don't see any SPAM until the feature comes back.
That's the spirit!
The next version of the directory uses a censored flag at the profile and the server level, which hides all the profiles registered on that server, as well as preventing future polling. It still is a manual task in the DB though. I may add a console task for this.
Thank you for your work. :-)