I’ll be honest – my first reaction on seeing this app was “Hey, that’s my idea!” But after a moment or so, that thought passed. After all, no one really holds the copyright to the concept of low-viewcount videos. And with hosting my code on GitHub, this kind of thing is the nature of open source.
The Twitter account is still low on followers, but the Facebook page is the thing that seems to have gotten a little more love. It’s crazy to see that things were pretty dead the week prior, and I saw a 36,160% increase. Ha!
There are terrible people, doing terrible things all the time. The world doesn’t need my help in spreading awful images. When I imagine my work, my code, helping to promote that sort of thing… I seriously considered shutting the whole site down.
On Friday, I noticed a few more “likes” to the Underviewed Facebook page, and a few more followers on the Twitter account. I didn’t think too much of it, but when they started to happen at a regular clip… I logged in to Google Analytics and was a bit astounded at what I saw.
Since 2014, Product Hunt has gotten a lot of attention. And it’s now become part of my daily routine, as it’s something I check pretty much right when I get in to work. PH is one of those sites where the things you see… you’ll likely encounter them again in a few hours, or a day later, trending on Twitter of Facebook.
The interview was for a radio show called Breitband on Deutschlandradio Kultur (German Public Radio). Chatting over email was easy enough, but the tricky part (given our disparate time zones) was setting up the actual interview.
Most every camera or mobile device uses some kind of default naming convention (iPhone: IMG_1234.MOV, GoPro: GOPR1234.MP4). This site searches YouTube for those default file names, and serves up videos that have a low number of views. Because these videos still retain their default file names as titles, it’s unlikely that they’ve shown up in any searches. And it’s very likely these videos haven’t been seen by all that many people.
This is a screenshot, showing my API usage for the project I’m working on currently. Can you spot where I started to really test the thing? And can you also spot where I ultimately optimized my code, so that it wasn’t making such heavy calls? Pretty proud of that second one.