| The article can be summarised to: "Use the subreddit where your target audience hangs out" Nothing wrong with the advice, but most subreddits have a no self-promotion policy (and reddit has a "no promotion over 10% of account activity" policy). There are things like self promotion threads but its only visited by people looking to promote their products and not by other people. Users who don't cease the promotion on being warned will have a very real possibility of having their account and domain banned from the sub. I've been on the moderator side of subreddits, and the general sentiment is that people are there because of a shared interest and not to be the promotion ground for some wannabe-rich guy. If a subreddit is for fountain pen enthusiasts, they'd rather see 10 posts going "Help me choose my first fountain pen" rather than some guy promoting his fountain pen store on etsy. |
If the post doesn't pass my sniff test, my script will remove the post, mute the user, and permanently ban the user with a single keystroke -- do not pass Go, do not collect $200.
I can't just rely on user reports alone because a few of the members of the community are overzealous about what they'll report. I need a variety of metrics to make the call, and it's much easier to use the Reddit API to collect, process, and report those metrics than to try to click around in Reddit's horrible moderation UI to get the information I need to make a reasonable decision.
Confession time: I started writing the script about 5 days ago, and since I'm waiting to start a new job, I've actually made this script into a bit of a hobby to kill the time. By now it's morphed into a multi-threaded Mutt-like Reddit moderation tool, where it displays all mod queue content via a curses interface that I navigate with VIM key bindings, and keystrokes issue commands onto an asynchronous queue that another thread consumes and acts upon via the PRAW package. For example, the keystroke to approve a submission will immediately delete the post from the curses view because I love wicked-fast and responsive UIs, but the deletion on the backend could take another couple of seconds, especially if I'm rapid-firing 5 or 6 approvals in a row, and I just let that happen on the queue. Maybe if I refactor so that Python experts' eyeballs won't bleed when they see my code (e.g., I'm manually grabbing and releasing locks on stuff that's shared between the curses interface code and the async queue code rather than using more elegant synchronization capabilities in Python) I might consider releasing some source.