It has come to my attention that some of the SFR flaggers are catching flak in the form of flags
Whether some of it was from a certain person getting ticked off about curation sniping is irrelevant to me. These comments are SFR mentions against ABUSE and thus we will do what we can to protect them.
This has prompted my picking up priority on the healer or flag neutralization bot. This will not be a lengthy post as I will be getting back to the coding. If you have not noticed, I also made some slight adjustments to the and
reports (the latter of which has not yet been executed but code it ready for tomorrow.)
In retrospect, I guess flaggable posts is kind of a misnomer for posts with 0.00 SBD. Ummm "maybe flaggable posts"?
The report changes will make it much easier to find what to flag to support decentralized blockchain abuse fighting via more stakeholders. Previously, the tables would have repeats of every individual abuse fighters flag and it has now been refined to include distinct posts. From the user perspective, It would seem to be a trivial thing but, from the SQL perspective, it wasn't really as I had to add some logic to accomodate the NSFW post links.
Anyways, that's all I got for you today as I need to continue monkeying around with this here code. I'll have to save the lengthy utopian blog post for another day!
P.S. Be sure to follow for future SFR healing ops. Planning on making it the dedicated flag defense bot and will be producing activity reports. I'm also considering having
for randomized "cherry-on-top" bonus vote. Delegations are welcome and may help light a fire so to speak as I hate seeing good SP going to waste. 😉
Lmk if you delegate as I will make sure the SP is gainfully employed until the healer is fully operational.