<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sreenivas V Rao on Medium]]></title>
        <description><![CDATA[Stories by Sreenivas V Rao on Medium]]></description>
        <link>https://medium.com/@sreenivasvrao?source=rss-35a5c1da4fc0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sMmZZg8ntdeeVGHQl9SKlg.jpeg</url>
            <title>Stories by Sreenivas V Rao on Medium</title>
            <link>https://medium.com/@sreenivasvrao?source=rss-35a5c1da4fc0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:30:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sreenivasvrao/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A morning without coffee]]></title>
            <link>https://medium.com/@sreenivasvrao/a-morning-without-coffee-7b3b540fe8f5?source=rss-35a5c1da4fc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b3b540fe8f5</guid>
            <category><![CDATA[short-story]]></category>
            <dc:creator><![CDATA[Sreenivas V Rao]]></dc:creator>
            <pubDate>Thu, 21 Dec 2017 19:41:40 GMT</pubDate>
            <atom:updated>2017-12-21T23:38:21.192Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This incident took place in the first week after I moved to the US three months ago. I got extremely lucky, and you will see why if you read the full thing. I just want to record it for posterity. There’s a TLDR.</em></p><p>It was a dark and stormy weekend in Amherst, Massachusetts. My roommates and I had just moved into our new apartment, and were in the process of getting set up. We needed lamps, laundry baskets, hangers, and other odds and ends. Like other broke graduate students fresh off the boat, er… flight from India, we were looking forward to a large second-hand sale that was to be held on campus that Sunday. The proceeds were going to a charity, I forget which — it doesn’t matter. The sale was charity enough to us grad students.</p><p>Sunday rolled around, and we found that the bus service in the area had far fewer buses plying than usual on Sundays. Ah well. We decided to split a cab ride to and fro. We ended up going a little late to the sale, and missing out on some good deals on couches and bean bags. However, we did find a great toaster, hangers, a lamp, a desk lamp and other things.</p><p>In our haste to get to the sale on time (which we never did), I did not have the time for coffee, or really any food in the morning — a fact which will become relevant soon. After the sale, armed with clothes, lamps, toaster, and even posters from a poster sale nearby, we hailed another cab in the Sunday drizzle and headed back to the apartment. The lack of coffee made me really groggy, and the lack of food made me ravenous by the time I got to the apartment. Once I got back, I removed my hoodie which had grown damp by the time, dumped the loot on my roommates, and dug into my pocket for my phone.</p><p><em>Nope, not there. Other pocket? Nope. Hoodie pockets? Nope.</em></p><p>Okay crap. Was it amidst all the stuff we bought? Nope. Okay, panic mode. I didn’t have a backup of the data. I had passwords saved. I did <em>not </em>have a pattern-lock, pin, fingerprint sensor or any sort of security enabled.</p><p>Okay, it wasn’t the apocalypse. I could call my phone, find out where it was, couldn’t I? Nope, I had just moved to the US. I had not got a SIM card yet!</p><p>Okay, it was probably not in the apartment. I had it with me when I was paying for the stuff at the sale. Maybe it was in the cab? I called up the cab driver immediately through the Uber app. Nope. <em>It was not in his car.</em></p><p>I took a deep breath. Okay, I have an Android. I could locate it through the online phone location tool — android.com/find. So I used that. Oh wow, the phone was connected to campus wifi! Thank God!</p><p>It was low on charge however. I remotely locked it with a password right away, and flashed a message, “If found, please return to &lt;my address&gt;”. I tried ringing the phone a couple of times — since it was connected to the wifi, I could do this even though I had no mobile network. At this point, the phone was pretty low on charge, if I rang it a few more times, the battery would probably die, and no one could ever find it. So I stopped ringing it.</p><p><em>All right, </em>I thought. <em>The phone is on campus thankfully. People here are nice. Who’s going to steal a two year old phone?</em> All I had to do was go back to campus, ask around at that sale. The cashier probably had it.</p><p>One of my roommates was nice enough to accompany me the second time to campus. I gobbled down a bowl of oats, drank my coffee, and left again to campus. The rain was picking up again. I borrowed a raincoat from another roommate, and rushed out.</p><p>The cashiers at the sale hadn’t found any phones by the time I reached there. My hopes crashed. The phone had been on <em>campus</em> wifi. It had to have been here. The sale was winding down, and maybe someone would find it when they were cleaning up?</p><p>One of the cashiers further dampened my hopes further of finding the phone further by saying someone might have stolen it. I left them my contact details in case my precious device ever turned up at their counter, but I wasn’t optimistic. An unlocked phone with no SIM card inserted. All anyone needed to do was reset it to factory mode — good as new — and that was if they were being nice.</p><p>I knew at this point that it was more or less a lost cause. All I could do was file a lost+found report with campus police department… at the other end of the campus, ten minutes up a small hillock- on a cold, rainy, hungry afternoon. My roommate was too nice to say, “Get lost, I’m going back to the apartment.” So we both went to campus police, half-jogging, half-sprinting, and fully regretting my life choices.</p><p>Ah, but even campus police is closed on Sundays! I ended up filing a report through a phone line they had — something I could have done twenty minutes ago — without travelling across campus in atrocious weather. But here I was. Phone-less, wet, cold and tired. We took another cab back to the apartment.</p><p>I couldn’t stop thinking about when I last saw my phone. And this was when the coffee started working I guess. I remembered using it to video-call my brother in India before leaving from campus… I remembered my friend using my phone to update SplitWise on the cab back to apartment… Holy shit, I had it with me on the way back! It <em>had </em>to have been in that cab.</p><p>But the driver said it wasn’t in his car… Of course, it made sense. It wasn’t in the <em>back seat.</em> We had put all our stuff <em>in the trunk.</em> It must have fallen out of my hoodie’s pocket as we were getting stuff out of the trunk! I called that cab driver once more. He didn’t respond. He was at work. All I could do I was text him from my roommate’s phone, and sit and wait in the hopes that the cab driver is a good guy. Imposing my faith in the goodness of all American people, I waited. A country’s reputation was hinged on his response.</p><p>So I waited. And waited. Every time my roommate’s phone beeped with a text alert, I looked up at him expectantly. My roommate was getting more annoyed each time. I was helpless.</p><p>Seven hours later,<em> </em>the phone beeped again. I didn’t even bother. My roommate yelled across the hall, “Congratulations Sreenivas! Your phone is with the driver!”</p><p>I wish I could remember the driver’s name, or his cab number, but it’s all beyond me now. Faith in American people undamaged, I replied to the driver’s short text. <em>“Thank God! Can I come pick it up? Or can you drop it off at my apartment again? Thank you so much.”</em></p><p>The busy driver replied — <em>“You can come pick it up from me in Chicopee, or wait until Thursday when I can drop it off at UMass.”</em></p><p>I weighed my options. Chicopee is twenty miles away (32km for the rest of us) from my apartment. I did not have a car. Public transport is three buses, and a two and a half hour journey — <em>each way.</em></p><p>I had no choice in the matter. I didn’t want to meet a random dude all alone anyway. I was forced to wait until Thursday for my phone. This is where the first stroke of luck hit.</p><p>I have a cousin, in Amherst, of all places. I had never met him before however. I had talked to him a couple of times earlier though. He agreed to drive me to Chicopee after work one evening, and pick up my phone. Hell of a first impression I was making on my cousin of course!</p><p>Meanwhile, the cab driver agreed to drop my phone off with Campus Police earlier than expected. I gave him the address from Google Maps. But he messaged back saying it’s the wrong address. What the hell?</p><p>It didn’t matter. The cab driver was getting annoyed now. This was an added hassle for him on top of his job. I messaged him back — no calls, he wouldn’t answer calls while driving — that I would pick up the phone from Chicopee.</p><p>All right, done deal. My cousin would drive me to Chicopee, and I would get back my phone. It turned out the cab driver was just as afraid of meeting a random dude from the internet all alone too.</p><p>He asked me to come to a brightly lit Rite-aid parking lot, well covered by CCTV cameras. Once we reached, he drove up to us, hand outstretched, shoved the phone at me, saying, “Here you go dude, thanks-sorry-bye”, and he was off! Perhaps afraid of getting mugged by two skinny brown dudes, he didn’t want to stop the car at all!</p><p>And this is where the story should end. I had my phone in hand. The ordeal had ended. Right? I wish. I had locked my phone using android.com/find. Amidst all the stress and the haste, I had <em>forgotten the password. </em>All the way back to my apartment, I tried various combinations of what I thought was my password. Nope. The annoying red “password incorrect” message kept flashing at me.</p><p>So after all that had happened, I had with me a dead brick in hand. My precious phone had travelled all over Western Massachusetts in someone’s cab, and finally got back into my hands, only to tell me that I could not open it. So near, yet so far.</p><p>This is when the second stroke of luck hit.</p><p>You see, I had rooted my phone, flashed a different OS. (Yay Android!) So I could access my phone through shell commands. Putting my google-fu to good use, I found that removing a couple of files would remove the lock on the phone.<br> <br> I tried it. Holy shit, it worked! I could not believe it! My phone was alive again! (The only reason this was possible was because I had rooted it and got administrative privileges on my phone of course. You couldn’t do this on any phone otherwise.)</p><p>The corollary of course is that if I could do it, anyone with the least amount of tech-savvy could have have done it as well, and got all my data. Rooting your phone is obviously a double edged sword to wield, so be careful about it!</p><p>You probably aren’t wondering about it, but before all this happened, there was a zeroth stroke of luck.</p><p>Remember how my phone had no mobile network and was connected to campus wifi, and so I could lock it? When I was locking it, I was 7 miles away from campus. The phone was in the cab the whole time. The cab <em>happened</em> to go through campus again, <em>happened</em> to connect to campus wifi, <em>happened</em> to have a stable connection and enough battery for me to ring and lock it!</p><p>I’m a smarter person now. I have a pattern lock, and I don’t skip my morning coffee.</p><p><em>TLDR: Lost phone, went on a 20 mile chase, got it back through several strokes of luck, almost got it back as a dead brick after the entire ordeal, managed to resurrect it from the dead through sheer luck.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b3b540fe8f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Reddit Safer For Work with /u/RiskyClickerBot]]></title>
            <link>https://medium.com/@sreenivasvrao/making-reddit-safer-for-work-with-u-riskyclickerbot-3bcb54fc1fe6?source=rss-35a5c1da4fc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bcb54fc1fe6</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[clarifai]]></category>
            <category><![CDATA[reddit]]></category>
            <category><![CDATA[computer-vision]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[Sreenivas V Rao]]></dc:creator>
            <pubDate>Sat, 05 Aug 2017 05:57:38 GMT</pubDate>
            <atom:updated>2017-08-05T05:57:38.981Z</atom:updated>
            <content:encoded><![CDATA[<p>In my previous <a href="https://medium.com/@sreenivasvrao/introducing-u-riskyclickerbot-22b3d56d1e2a">post</a>, I described the basic idea behind RiskyClickerBot — a Reddit bot which scans comments for links to risky images and analyzes those images. This is a more in-depth and technical post describing how the bot works. If you want to dive right into the source code, you can do that <a href="https://github.com/SreenivasVRao/RiskyClickerBot">here</a>.</p><h3>The Gears And Wheels</h3><p>This bot runs on Reddit- which means it requires access to Reddit’s API. <a href="http://praw.readthedocs.io/"><strong>PRAW: The Python Reddit API Wrapper</strong></a><strong> </strong>is what you’ll need for the job. The bot is meant to analyze images, and Reddit uses Imgur heavily for hosting images. So access to <strong>Imgur’s API</strong> is very handy. The python bindings for that are available <a href="https://github.com/Imgur/imgurpython">here</a>.</p><p>The core technology behind the bot is a Convolutional Neural Network, which is trained to classify images as either NSFW or SFW. Now this could have been a tall task in itself. Fortunately, Yahoo open-sourced this exact model last year. Unfortunately, the code is written using Caffe, and it requires setting up a Google Cloud or AWS GPU instance — which while free, is fairly labour intensive. Clarifai on the other hand, has the same tech usable through <a href="https://developer.clarifai.com/models/nsfw-image-recognition-model/e9576d86d2004ed1a38ba0cf39ecb4b1">API calls</a>.</p><p>All of this allows us to build the bot in Python.</p><p>But how do you keep it running?</p><p>Typically, a bot can be kept running locally using a <a href="https://www.computerhope.com/unix/ucrontab.htm">cron job.</a> This however requires your PC to be running for it to work. The neater way of making this work is to use a cloud platform like <a href="http://heroku.com/">Heroku.</a> So that’s what I did.</p><p>So we have our tools for the job ready. Let’s actually build the bot.</p><h3>Setting up /u/RiskyClickerBot</h3><p>I started building a simple test bot by following this <a href="http://pythonforengineers.com/build-a-reddit-bot-part-1/">tutorial</a>. Since that covers API set-up for PRAW, I’m not going to go into that again.</p><p>The Imgur-API can be setup by using this <a href="https://api.imgur.com/oauth2/addclient">link.</a> <a href="https://www.youtube.com/watch?v=OiDQu-0-DIA">This video tutorial</a> came in handy. Note that you need an imgur account to access the API. However, since the bot is not going to post/vote/comment on Imgur, we can use the API from an anonymous context as shown here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*AZi5B0Q9Nj3LGayyU4_vpg.png" /></figure><p>Clarifai’s API can be set up very easily with <a href="https://developer.clarifai.com/quick-start/">three lines of code.</a></p><p>Once all the API has been setup, we can actually get into the bot’s code.</p><h3>Getting the comments stream</h3><p>Let’s say you have a reddit bot set-up like the tutorials showed earlier. We require the bot to read the comments stream for reddit. To make the bot available site wide, we read the comments from r/all.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8da8e9d5dcec5381f13984356cdadada/href">https://medium.com/media/8da8e9d5dcec5381f13984356cdadada/href</a></iframe><h3>Calling the bot into action</h3><p>We only want the bot to act when someone says “risky click”. So…</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c2b2767acc1a002f6de19aca84c6b489/href">https://medium.com/media/c2b2767acc1a002f6de19aca84c6b489/href</a></iframe><p>This phrase is usually said in response to some other comment like in this image here. We want to analyze that parent comment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*S4HLxMSkW72u4gZl62JN2w.png" /><figcaption><strong>This is a typical comment chain that we’d like the bot to be able to handle.</strong></figcaption></figure><p>And to do that, we first have to get the parent comment:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cfa7aabfcf21d505368ee15ffeaa5c92/href">https://medium.com/media/cfa7aabfcf21d505368ee15ffeaa5c92/href</a></iframe><h3>Analyzing a comment</h3><p>The code snippet above shows the basic action that the bot performs when triggered.</p><p>The generate_bot_comment() function has a lot of bells and whistles which you can find in my source code, but the basic idea is this:</p><p>We need to find the risky URLs in the parent comment, and then handle those URLs. This we can do by using a Regular Expression.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/408620f3674977d36f5cbf4214b7f596/href">https://medium.com/media/408620f3674977d36f5cbf4214b7f596/href</a></iframe><p>The regex was largely taken from this <a href="https://stackoverflow.com/a/6883094/8138722">stackoverflow answer.</a> So once we have the list of URLs to analyze, we need to handle them. URLs are handled in a few different ways. They may be links to imgur albums (multiple images), an imgur image, an imgur gallery, or a direct URL to the image on a different host server, or maybe just not an image at all. Each of these are handled slightly differently.</p><p>Since the Clarifai API produces SFW/NSFW score for a single image, the score for an album is the average over all the scores. (Not ideal, but works well in practice.)</p><p>Imgur links have a few different formats. So it’s useful to know where it comes from. Gallery links could be to an album, an image, a gif, etc.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0d5ce07e09b1fcd166eb31aeb90fe63f/href">https://medium.com/media/0d5ce07e09b1fcd166eb31aeb90fe63f/href</a></iframe><p>Once we know the kind of link that we have received, we can actually do the analysis using Clarifai’s API.</p><p>The Clarifai API returns a dictionary containing the results. So the result is a key:value pair that you need to access.</p><pre>prediction = model.predict_by_url(https://medium.com/link)</pre><h3>The Clarifai NSFW/SFW prediction model</h3><p>There’s a broad overview <a href="http://blog.clarifai.com/moderate-filter-or-curate-adult-content-with-clarifais-nsfw-model/">here</a>, and a detailed description <a href="http://blog.clarifai.com/what-convolutional-neural-networks-see-at-when-they-see-nudity/">here (slightly NSFW).</a></p><p>The crux of it is a Convolutional Neural Network which is trained specifically to distinguish between NSFW and SFW images. A good explainer on ConvNets can be found <a href="https://www.youtube.com/watch?v=JiN9p5vWHDY">here.</a></p><h3>Sending the bot’s reply</h3><p>With this result, we have to frame a reply message, keeping in mind the Reddit markup syntax. In all honesty, this was the bigger problem in comparison to getting the rest of the bot to work.</p><p>Once the reply is framed, we can make the comment by doing:</p><pre>comment.reply(bot_reply)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/1*kK_Y7HdCPNeVwizhIXuM6w.png" /></figure><h3>Some bells and whistles</h3><p>Heroku has been a great way to set up this bot. However, one key issue is that the bot should not process the same comment twice. This can be handled by setting up a log of all comments previously processed.</p><p>The gotcha is that any log stored on Heroku is lost when the bot is periodically restarted by Heroku. Solving this problem isn’t too difficult however. We need an external storage server for the log. Heroku’s <a href="https://devcenter.heroku.com/articles/memcachedcloud">MemcachedCloud</a> add-on is a great tool for this. I found <a href="https://gist.github.com/hzsweers/8595628">this</a> tutorial really easy to use in setting that up.</p><p>Another really great add-on is the Papertrails log keeper. This add-on allows you to set up alerts. I’ve set up alerts to let me know whenever a bot crashes, and hooked it up to my slack account!</p><p><em>(These two add-ons are free to use, but they require adding a credit card to your heroku developer account.)</em></p><p>And there we go. This is how I built RiskyClickerBot. Let me know if something isn’t very clear — I did indulge in a certain amount of hand-waving here :D</p><p>If you see RiskyClickerBot do a good job on Reddit, don’t forget to say “good bot”! And if it botches up, let me know! I use the handle /u/PigsDogsAndSheep. :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/0*YWi6NPFxuf4naRoS.png" /><figcaption><strong>“This post is SFW (I’m 99.99% confident.)” — /u/RiskyClickerBot, probably.</strong></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bcb54fc1fe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing /u/RiskyClickerBot]]></title>
            <link>https://medium.com/real-solutions-artificial-intelligence/introducing-u-riskyclickerbot-22b3d56d1e2a?source=rss-35a5c1da4fc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/22b3d56d1e2a</guid>
            <category><![CDATA[reddit]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[computer-vision]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Sreenivas V Rao]]></dc:creator>
            <pubDate>Mon, 31 Jul 2017 05:30:53 GMT</pubDate>
            <atom:updated>2017-08-05T05:59:00.570Z</atom:updated>
            <content:encoded><![CDATA[<p>I use <a href="http://reddit.com/">Reddit</a> a lot. In fact, I use it a little too much. My comment score puts me in the top 40% of Reddit users — slightly better than the average Redditor (i.e. someone who has spent too long on the website).</p><p>When you do use Reddit a lot, you find these useful bots running on the website, automatically commenting on posts. I think my favourite has got to be <a href="https://www.reddit.com/user/colorizebot2">this</a> — a bot which converts your ancient black and white photos into colour photos automatically!</p><p>Besides bots that can comment just like humans, the Reddit community has some interesting quirks — some phrases become very popular among users. The longer you spend on Reddit, the more lingo that you pick up. For example,<em> cakeday, throw away, alt, risky click, ITT, FTFY,</em> etc. are phrases with specific meanings for hundreds of thousands of anonymous Redditors.</p><p>One issue however, with Reddit and other similar websites is that, when you give users the mask of anonymity, there’s a reasonable chance that someone is going to link to porn, or gore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*Q86l9bqXPcqisvg4mCpg2g.png" /></figure><p>Now when that happens on Reddit, a user who isn’t sure if they should click on it, might respond with the phrase ‘Risky click’.</p><p>Another Reddit user who’s brave enough to risk watching something horrifying, might click on that link, and then warn others away, or reassure others that it was actually harmless.</p><p>Outside of Reddit, automated warning systems for risky links exist. Porn filter systems keep your YouTube/Google/Twitter/Facebook/Instagram feeds clean. Yahoo in fact, open-sourced one such system in <a href="https://techcrunch.com/2016/09/30/yahoo-open-sources-its-porn-detecting-neural-network/">September 2016.</a></p><blockquote>So why not make a system for Reddit?</blockquote><p>And that’s what I set out to do! The phrase ‘risky click’ is used often on Reddit in the context described above. You can set up a system which reads the firehose that is the Reddit comments stream, and then jumps into action when that phrase is found.</p><p>So now we are looking out for a phrase. When that phrase is found, the system needs to analyze a comment for links, and figure out if those links are risky to click on (at least when others are around :P).</p><p>The links in this context are mostly albums of images, direct links to images, gifs, etc. So at the end of the day, this system can be expressed as a fairly straight-forward problem in Computer Vision.</p><blockquote>Given an image or a set of images, tell me if it’s Safe for Work (SFW) or Not (NSFW).</blockquote><p>(At the time of writing, the system is able to handle multiple images. Gifs pose a bigger challenge, so I haven’t added functionality for that yet.)</p><p>The detection system that Yahoo released, requires a lot of work to set up for personal use. <a href="http://clarifai.com/">Clarifai</a>, on the other hand, is a company that has a similar <a href="https://developer.clarifai.com/models/nsfw-image-recognition-model/e9576d86d2004ed1a38ba0cf39ecb4b1">system</a> available for free use through API calls.</p><p>So, now we have a system to detect risky links — mainly images, and another to analyze risky images.</p><p>Put those two together and we now have /u/RiskyClickerBot!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*Ubxp9dIt0mCzJOkSIAYJ4g.png" /></figure><p>And in case the bot didn’t reply to a risky link automatically, it can be called into action too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*rWmJ-x5tqxoRYX0aY9MpVQ.png" /></figure><p>So there you go.</p><p><a href="http://reddit.com/u/RiskyClickerBot">/u/RiskyClickerBot</a>: <em>Making Reddit safer for work, one comment thread at a time.</em></p><p>The code for this bot is <a href="http://github.com/sreenivasVRao/RiskyClickerBot">open source</a>, although I haven’t yet added a README or a License to the repo. So check it out if you’re interested :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/0*w3t_AkWv06_AjGo8.png" /><figcaption><strong>Pictured here: RiskyClickerBot’s cousin.</strong></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22b3d56d1e2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/real-solutions-artificial-intelligence/introducing-u-riskyclickerbot-22b3d56d1e2a">Introducing /u/RiskyClickerBot</a> was originally published in <a href="https://medium.com/real-solutions-artificial-intelligence">Artificial Intelligence with a Vision</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>