Likelihood to read a tweetstorm

I’ve noticed something weird about my reading habits. I think only read maybe 1 on 25 tweetstorms authored by someone I follow. I will read about 1 in 5 retweeted by someone I follow.

Tweets appear with most recent at the top and oldest at the bottom. So, when I encounter a tweetstorm in my feed, the natural inclination is to scroll to the end and read them in reverse order. It is an unnatural threading.

When someone retweets a tweetstorm, it is just the one tweet with a notation that there is more in the thread. So, I click the tweet, it opens a page with the tweets in order where I can read them in order. It feels natural.

I guess I could click the last tweet from those I follow, get taken to the end and scroll back up to the top. That would put things in the right order.

Lying to Big Data

The reaction people have towards social media companies is to lie. This amuses me because self-reporting is well known as the worst data. The data scientists expect people to lie.[1] Which is why they ignore what you say about yourself and focus on your behavior.

So, you need to start having intentionally deceptive behavior. The problem is: if people like you all deceive in the same patterns, then the data points to the same place anyway. You have to deceive in novel ways others like you would never think of doing.

Good luck with that.

1. Christian Rudder’s Dataclysm: Who We Are (When We Think No One’s Looking) is about how as a data scientist for OKCupid, a dating website, he cannot depend on the honesty of people. He has data on what they say and compares it to what they do.

Unsticky Likes

Like Stamp 1
Credit: Joy Powers

Of late, I have been featured in some posts that generate many comments on Facebook. Naturally, I like these comments.

So when a new one comes in and old ones I thought I previously liked no longer show them being liked, it was noticeable. Over the past few months, I have seen the behavior over and over.

My primary hunch is that I am just a bad person and did not actually like them as I thought. Human memory is fallible. It is easily feasible that I in seeing them not liked assumed that I would have taken action to like them. The memory of having done so could actually be the recollection of doing so with others conflated to this incident.

Hypothetically, it is possible that I like a post and the action never gets updated in the database without telling me it failed. If the UI is designed to show the like whether or not the database took it, then I could see it liked and when I return later to see it not liked. Maybe because these posts have such a large dataset collected into a single place I more easily notice when this happens. It would be disturbing if we go to all the trouble of responding and others are never getting that feedback.

WP Maintenance Nightmare

Discovered this blog was showing:

Briefly unavailable for scheduled maintenance. Check back in a minute.

Any time it upgrades, this gets thrown up during the process. However, it goes away once the process is completed. It showing is not an error so much as a notification and should as it says go away in a minute. The problem is that if the upgrade hangs, it does not go away.

To manually fix it, go to the directory on the server with the files and remove the .maintenance file. (I rename them to .maintenance_YYYYMMDD so as to track how often they happen.)

I noticed that a particular plugin stated it needed an update. Even better, that plugin was set to automatically update, which suggested it was the cause. Kicking off the update hung the site again. Deleting the plugin also failed.

Eventually, I found myself looking at the wp-content/upgrade folder and noticed there was a folder named for the plugin that was the only content of the folder. I renamed that folder to prepend the name with zzz- and tried the upgrade again. The upgrade worked this time.

My guess is something was bad with the contents of the downloaded plugin upgrade temporary folder, but instead of deleting the contents of the folder as the first step the upgrade process, it just used the existing folder and hit the error each time until I removed it. Weird.

Facebook Feature Request: Privacy and Tags

This is essentially the issue of the Friends of Friends post. In this case, I am not really interested in expanding the audience.

Say I publish a friends only post. Victor, my friend, makes a comment tagging Roberta, not my friend, and asks a question directed at her. She is not notified about the tag. Nor can she see the comment or post.

Therefore, in my mind, allowing the tag to be done is counterproductive. Facebook should warn Victor that Roberta cannot see it. Ideally it would be ahead of time and prevent it. Less acceptable, but I would be happier is after the fact having a “Roberta cannot see this” notice. (The “Who can see this?” thing is vague and not generally very helpful clarifying exactly who can see it.)

Troll Facebook Button

Sometimes I want to leave a comment but not actually enter the Facebook conversation. For that, I want a “Facebook Troll” comment browser extension.

The idea is that it could allow me to post the comment and automatically turn off notifications for that post.

Pretty sure replies would still notify me.

Ironically enough, the same feature would be useful for engagements, death announcements, marriages, and other posts where I just want to leave a comment but not have to deal with notifications about anyone else leaving a comment. So 90% of use cases could be a “Congrats!” button or a “Sorry for your loss.” button.

If in doubt; then delete

The title is a joke. I hate deleting things. A digital packrat, it takes knowing that deleting something will likely fix an actual problem to delete it. And my delete is to move it out of the way not actually destroy the file.

Anyway, I discovered this blog was hosed. I had noticed Gotcha Jerks Part II was missing from various social media sites. So, I went to post it and found the whole blog hozered. It just displayed a Fatal PHP Error for class.jetpack-tracks.php and so I started to look on the WordPress.Org support page when I decided to move the whole Jetpack plugin directory to jetpack.bad and “see what happens.” Well, that restored the blog. The plugin claimed it needed an upgrade, so I ran that. All is well.

Easier than my initial resignation.

I went to “diff -r jetpack.bad jetpack” to get a comparison of the differences between the bad one and the good one, but the bad no longer exists. Thus the title. I am considering deleting and reinstalling Jetpack to ensure what I have is pristine. I have a nagging feeling that the upgrade moved jetpack.bad to jetpack then updated some files. Delete and rebuild would give me more confidence I purged lingering bad code from the plugin. Additionally, the lingering issue from WordPress and SSL a month ago might be related? In sum, I suspect there are subtle issues lingering and a clean sweep is in order.

Buffer Feature Requests

Dual Window

LinkedIn, Facebook, and Google+ have significantly different character number restrictions than Twitter. Naturally, Twitter limits posts to their notorious 140 characters. LinkedIn allows 700, and Google+ / Facebook allow about five thousand.

I like to post things with a quote from the articles I share that captures what I found most interesting about it. Generally, they fall between 200 to 200 characters. Too long for Twitter, which means I editorialize it to make it fit.

Something amazing about the Pocket tool to share to Buffer is it provides two different textareas. One for Facebook and one for everything else. Brilliant! So much so, that I am tempted to completely change my workflow to push anything I want to share to Pocket just so I can share it with Buffer in a way that makes sense. On Facebook the preview URL appears to Pocket rather than the actual destination which slightly bothers me because I’d prefer the source to get attribution.


It would be nice to be able to share to Tumblr through Buffer. It seems odd that Buffer would support who has been dying for years and will finally be gone in 6 weeks yet not one of the larger social networks?

WordPress and SSL

For a while my self-hosted WordPress has been a royal pain in the ass. Trying to compose through the interface through Jetpack would show occasional errors that “Saving of draft failed” or an inability to communicate. Sometimes it was usable, sometimes there were so many errors I gave up and used the site. The site admin interface sometimes made me login every hour or every couple minutes.

I reinstalled Jetpack a couple times. I poked around on the WordPress support forums which I apparently could not search.

So I searched via Google and ran across this How to Fix WordPress Keeps Logging Out Problem article. It dawned on me that I had let my hosting provider setup SSL for the site. The WordPress Address and Site Address fields were using http. So I changed them to https. That seems to have solved the login issues.

I am writing this through the interface and got a failure on saving the draft. So there is something else to make it all better.

Facebook Comment Chat Box Pop-ups

Well, it came true for me. Facebook pushed to me the new feature of comment threads appearing in a chat box.

I hate the chat box on Facebook. I keep an open tab for messages for ongoing conversations specifically because that seems to suppress the chat box. I do not mind the notifications at the top right, but ruining screen real estate by blocking what I am reading that makes me have to close the box in order to finish? No thanks. That is an unnecessary interruption to what I was doing. It makes me more likely to ignore the message because I am determined to finish what I was doing.

The comments chat box keeps a count of how many unread have come through it. So, basically, in the top right I get a notification AND a second notification at the bottom for the. Same. Exact. Thing. Fortunately, it does appear if I check the chat box comments, then they simultaneously disappear from the top. But, if I make the mistake of checking new comments via the top in a new tab as is my normal operation, then I still have to read them in the chat box. Closing the chat box does not clear the unread.

Even when I have closed all the conversations, if I navigate to another page, then it returns and I have to close the open one just to be able to read the page. Again, my normal method of reading is to open notifications in new tabs. Then close the tab when I have consumed the new content. That basically opens a bunch of these chat boxes I have to close. Essentially, Facebook only wants us reading comments in these chat boxes and not by opening new tabs.

There is a “Hide this tab” option which asks if I want to also disable notifications for that post. I was initially confused and hit disable which means I no longer get anything about that conversation. I now hit keep. That does get me back to where I want to be with only having the single notification for comments. But, only for posts I have already handled. I will have to go through this process again for every single conversation on Facebook which is ridiculous. I may have to just not comment on anything new or post anything else until I have a permanent fix. OK, that is hyperbolic, but I will limit engagements with others until it is solved.

I tried to disable this new feature in the user interface, but naturally Facebook is on to us and did not provide a way to do so. They want us to have to become used to it before we are given the ability to restore our now bad habits. People turned off chat back when they introduced it. The help page on it is full of people complaining about this new feature.

F.B.Purity has not yet caught up to this feature. The “Hide Chat Box” gets rid of the Messenger box not the comment one.