So, apparently around November 5th we stopped posting to Twitter. We didn't find out until around the end of that month and when we did nobody had the time and/or ability to look into why until this past week.
Now how we get our headlines over to Twitter is overly complicated and, frankly, idiotic. It's done by one of our IRC bots pulling headlines from the RSS feed and posting them on Twitter as @SoylentNews. The bot was written back in 2014 with hand-rolled (as opposed to installed via package manager) Python libraries and hasn't been updated since. This was breakage that should absolutely have been expected to happen. Twitter's penchant for arbitrarily changing their unversioned API means you either keep on top of changes or expect things to break for no apparent reason.
Here's the question: do we even care? We can either find someone who's willing to rewrite the bot to a new Twitter library, do it the sane way as either a cron or slashd job, or just say to hell with it since we only have two hundred or so followers on Twitter anyway. What say you, folks?
[TMB Note]: Twitter's who-to-follow algorithms really impressed me this morning when I logged in to manually post this story. How did they know we were all huge @JustinBieber and @BarackObama fans?
[Update]: We're again annoying Twitter users by spreading relative intelligence across their platform of choice. Credit goes to Crash for wisely pointing out that we don't have to code everything ourselves.
(Score: 3, Informative) by The Mighty Buzzard on Monday December 18 2017, @10:10PM (3 children)
Because I was asking from a "my time" perspective not a "site direction" one. A morning's coding is worth it to me if even a handful of people are significantly inconvenienced but if literally nobody cared I wasn't going to screw with it.
My rights don't end where your fear begins.
(Score: 0) by Anonymous Coward on Tuesday December 19 2017, @03:12AM (2 children)
(Score: 2) by Runaway1956 on Tuesday December 19 2017, @04:29AM
https://www.youtube.com/watch?v=dk01eeKMD_I [youtube.com]
(Score: 3, Interesting) by The Mighty Buzzard on Tuesday December 19 2017, @04:44AM
Oh don't go making me out to be all altruistic now. I code for SN because I enjoy using SN, so if a bit of my time helps get me a few more people worth arguing with, I consider it a personal win. Plus, and this is no small consideration, I do so enjoy showing the folks over at the old site how it's done. Didn't they promise unicode support "soon" a year ago or more?
My rights don't end where your fear begins.