These SFR GitHub updates are LONG OVERDUE!
We have been testing the updated code for some time and glad to finally get things in sync. I DO NOT want to be the metaphorical Wizard behind the curtain with this Steem community project.
That is why it is important to finally get things up to date on our repository. This way anybody should be able to pick things up in the event that I am struck by lighting or a falling piano.
About 9 meaningful commits added. This update is chock full of flaggy goodness!
Repository
https://github.com/anthonyadavisii/steemflagrewards
Summary/TL;DR
After testing for an extended period, we have finally updated the SFR repository. This includes functionality for the @sfr-mod-fund, SFR configuration, NSFW abuse flagging support, queue enhancements and more!
Onto the 🍖 and 🥔s of this update!
I will be detailing the significant GitHub commits below.
The SFR Discord moderators tirelessly and continuously review blockchain @steemflagrewards flag mention comments. This is to ensure Steem abuse fighters are rewarded with upvotes and /or beneficiary rewards via our regular reports.
For the longest time, the approving activity went unrewarded but has now changed. We have added the pairing of our moderators Discord IDs to their Steem accounts. We use this to incentivize moderators via @sfr-mod-fund beneficiary posts.
I have also added a couple of abuse categories for content that falls into NSFW categories. This is to warn abuse fighters of potentially inappropriate links in our reports. These links are now marked as "NSFW links" in both mod and flagger reports.
The general rule previously was to not claim SFR upvotes on NSFW links which was less than ideal. The new change allows us to fight NSFW abuse using our good flag incentivization techniques. The new abuse categories are now as follows:
porn spam - You are spamming nsfw content. Often contains external image sources, affiliate links and failing to decline rewards on unoriginal content.
nsfw - Generic category for abuse that is nsfw in nature.
^This one is the catch 22.
Finally, I have replaced the placeholder we had for the collusive voting definiton. SFR mods and admins, please let me know if you think this should be adjusted.
collusive voting - The votes on the content follows a repeated pattern suggestive of collusion between multiple users and /or alt accounts resulting in significant overvaluation of content.
In this commit, we updated the code to create the SFR sqlite database on initial run of the flag rewards bot. This adds the the approved_by and mod_included columns required for @sfr-mod-fund functionality.
This change is for users who are flagging below our dust threshold. The comment conveys that such flags will be rewarded via beneficiary rewards instead of an upvote. This is to prevent our bot votes from being below the SBD_MIN_PAYOUT value of 0.02. The comment format is in the below graphic.
To "sweeten the deal" for dust flaggers, we had made it so their flags have twice the weight in the beneficiary posts. For example, let's say we had a flagger post with 2 flaggers (for simplicity sake) and 25 flags each. The first flagger's flags are above the dust threshold and the second flagger's are below it. Bear in mind that the bot receives 5% of the post rewards. The resulting calculation for the dust flaggers beneficiary weight will be as follows:
This covers the creation of the two related functions required to generate the @sfr-mod-fund. Currently, I execute the mod_report() function in an interactive Python session.
We will be adding this functionality to the approval function or a separate Discord bot function. The intent is for the mod report to occur during the regular approval workflow or initiated by our moderators on-demand. The function will take the last 50 flags for the @sfr-mod-fund report post.
This encompassed the changes to our flagger report builder and respective posting functions. I redesigned the SQL for the NSFW changes for both reports.
Our bot had encountered issues voting on approvals resulting in a "hung queue" on occasion. In some cases, the bot would succeed in voting but may have errored on the SQL. This would leave the queue in a state of limbo while the bot repeatedly tries to vote on a comment. Sometimes, a ninja database edit was necessary. This had caused me to have to restart the bot more times than I would like to admit but we seem to be in a much better state now.
In order to mitigate this, we simply added a check to determine if the comment was already voted and set the database accordingly. Nothing too fancy but it has saved us all a lot of headache
We added these functions during troubleshooting of the aforementioned queue issues. . The queue_toggle function allows our mods to bypass the queuing mechanism. This allows approving flags during a "hung queue" state. The unqueue function was used to perform the SQL update required to remove a link from the queue such as those that were already upvoted. The upvote check seems to have minimized our need to use said functions.
This added the queue bypass functionality to the Discord on_ready event.
My Social Media Links
Also, I guess I should start doing that dropping links in my post thing so I can pretend to be one of those "social media influencer" types.
Twitter
Imgur
IG
YouTube
Minds
On a serious note, appreciate any that help support me on these other platforms so we can work together to promote Steem!
Related Project Promotion
Would you like to delegate to the Steem Flag Rewards project and promote decentralized moderation? It's much more fashionable than self-voting. Here are some handy delegation links!
SmartMeme
Don't forget to follow @smartmeme for OG meme curation and Kekistani Cleanup Meme Rank Results! As time permits, the meme ranks will be a thing!
If you want to earn the prestigous content cop rank, stay tuned for updates.
SFR Moderator Fund
@sfr-mod-fund is the account used to rewards our Discord mods for reviewing and approving blockchain flags daily which supports the fighting of abuse. Follow the fanbase on SteemAuto to support the mission automagically!
Series Backlinks
Also, here is my SteemAuto fanbase link if you would like to be one of my consistent supporters.
IMPORTANT NOTE ABOUT STEEM ALLIANCE!
As some of you know, I am campaigning to participate on the @steemalliance working group to be a representative and advocate for the abuse fighting community. I STRONGLY encourage all my friends and colleagues to register in order to vote on the 27th on their Discord
My intent is to ensure we are fair with all proposals but specifically want to ensure any proposals related to Steem abuse are properly represented and understood during the process. My partners @themarkymark and @imacryptorick are also running and I can attest that both are savvy. I will try to get a post out tomorrow with more details.
See the latest @steemalliance post here