https://www.goodreads.com/user_status/list/#######-user-name?format=rss
where #######-user-name
is the typical user number and name combination at one’s profile page.https://www.goodreads.com/user_status/list/#######-user-name?format=rss
where #######-user-name
is the typical user number and name combination at one’s profile page.This document is a response to a tweet. It is of very limited interest.
Twitter started out life as an AIM hack that Jack Dorsey added to his pager, Wired reports. Dorsey had been quite involved in the world of instant messaging, and had launched a dispatch software startup in 1999. Dorsey became quite interested in his friends’ status messages and wanted to see them and set his own …
Before Twitter was public, it was just an AIM hack on Jack Dorsey’s pager. Twitter founder Jack Dorsey had a background in messenger culture. He had even launched a dispatch software startup called D-Net, back in 1999. He was also captivated by his friends status messages on AOL Instant Messenger. He wanted to combine the \[…\]
On May 31st, 2000, I signed up with a new service called LiveJournal. I was user 4,136 which entitled me a permanent account and street cred in some alternate geeky universe which I have not yet visited. I was living in the Sunshine Biscuit Factory in Oakland California and starting a company to dispatch couriers, taxis, and emergency services from the web. One night in July of that year I had an idea to make a more "live" LiveJournal. Real-time, up-to-date, from the road. Akin to updating your AIM status from wherever you are, and sharing it. For the next 5 years, I thought about this concept and tried to silently introduce it into my various projects. It slipped into my dispatch work. It slipped into my networks of medical devices. It slipped into an idea for a frictionless service market. It was everywhere I looked: a wonderful abstraction which was easy to implement and understand. The 6th year; the idea has finally solidified (thanks to the massively creative environment my employer Odeo provides) and taken a novel form. We're calling it twttr (though this original rendering calls it stat.us; I love the word.ed domains, e.g. gu.st/). It's evolved a lot in the past few months. From an excited discussion and persuasion on the South Park playground to a recently approved application for a SMS shortcode. I'm happy this idea has taken root; I hope it thrives. Some things are worth the wait.
In the long run and for easier mass adoption, I’m hoping Manton can figure out how to parse RSS feeds in a simpler way so that users don’t need to do serious gymnastics to import their microblog posts from other sources. I’d imagine it’s far easier for him to adapt to the masses than for the masses to adapt to micro.blog. At the very worst, he could create a checkbox on the RSS import feeds to indicate which feeds are status updates and which aren’t and this would quickly solve the problem for the average user as most CMSes allow users to define custom feeds based on content type.
While there are a number of people doing things from simply adding date/time stamps (which micro.blog ignores) to functions.php tweaks to to custom plugins, some of which I’ve tried, I thought I’d come up with my own solution which has helped to kill two proverbial birds with one stone. (Note: I’ve listed some of these others on the Indieweb wiki page for micro.blog.)
The other day, I’d had a short conversation about the issue in the Indieweb chat with several people and decided I’d just give up on having titles in notes altogether. Most people contemplating the problem have an issue doing this because it makes it more difficult to sort and find their content within their admin UI dashboard which is primarily keyed off of the_title() within WordPress. I share their pain in this regard, but I’ve also been experiencing another admin UI issue because I’ve got a handful of plugins which have added a dozen or so additional columns to my posts list. As a result the titles in my list are literally about four characters wide and stretch down the page while knucklehead metadata like categories needlessly eat up massively wide columns just for fun. Apparently plugins aren’t very mindful of how much space they decide to take up in the UI, and WordPress core doesn’t enforce reasonable limits on these things.
So my solution to both problems? If found a handly little plugin called Admin Columns with over 80,000 users and which seems to be frequently updated that allows one to have greater simple control over all of the columnar UI interfaces within their sites.
In just a few minutes, I was able to quickly get rid of several columns of data I’ve never cared about, expand the title column to a reasonable percentage of the space so it’s readable, and tweak all the other columns to better values. Even better, I was able to add the slug name of posts into the UI just after the title columns, so I can leave status update titles empty, but still have a field by which I can see at least some idea of what a particular post was about.