Showing posts with label Twitter. Show all posts
Showing posts with label Twitter. Show all posts

Friday, April 5, 2013

The "Unlike" Project - First Month

Just over a month ago, I wrote this post explaining that I was beginning a campaign to "Unlike" things on Facebook. The idea was to start reversing one of my "Likes" on Facebook ever day, and then tweeting about it using the hashtag #UnlikeProject. The experience has been interesting in a lot of ways - I thought I'd give my "first 30 days" report (although it's actually been more than 30 days) and let you know what's been going on.

The first thing I noticed is that it is incredibly difficult to decide what to Unlike. Fact is, the things I've "Liked" are things that, in real life, I in fact do actually like! It feels a little bit like a betrayal, especially when you are Unliking things like The Bible or your favorite sports teams. It's also difficult to find the things that are less important to me so I can Unlike them first - I wound up making myself a list to make prioritizing easier. I don't intent to Unlike everything, so I need to make sure I find the things I want to free myself from first. (Pages set up by friends of mine, for example, or organizations that I genuinely do want to stay in touch with will probably stay in my "Likes".)

Some of the earliest casualties were Pages that post a lot. The reasons those got the axe first was that I was more likely to see their posts in my News Feed and remember "Oh yeah, it annoys me when I see them there!" or "Their posts are never interesting," and then I could wipe them out and be done with it. But even with the easy pickings of those frequent posters and with my "Unlike first" list, I still didn't Unlike something every day - once I Unliked two things in one day, and four or five days I forgot altogether.

Two different organizations actually saw my "Today I Unliked..." tweets and responded to them, apologizing for whatever they did that put me off. Fact is, they didn't do anything, and I told them so! This is all about cleaning things out and simplifying... and insulating myself and my friends from invasive advertising as much as possible. I do have a positive opinion of those organizations, thought... kudos for keeping an eye on your Twitter mentions (I didn't actually even mention them by @ handle, so they're watching keywords) and reaching out to people based on that! That's the way to DO social media!

During the month, I also discovered a few facts that back up my reasons for doing this:
I'm actually enjoying the project - there's a sense of freedom in it, like when you've cleaned out the junk from the garage or gotten all the bills paid for the month. Maybe you'll give it a try? If you do, make sure you remember to tweet your Unlikes with hashtag #UnlikeProject so I'll know you're in!


Is it nuts to just start Unliking things that you actually do like? Why will you be joining the project, or why not? Sound off below by clicking the "Comment" link!

Thursday, February 28, 2013

The "Unlike" Project

'dislike button' photo (c) 2011, Sean MacEntee - license: http://creativecommons.org/licenses/by/2.0/Today I made a rash decision. I decided to Unlike stuff on Facebook.

The reasons for this are not irrational. The reason I've clicked "Like" on TV shows, musical artists, movies, and whatever, is usually because I want my profile to say things about me when people visit it and look at my details. You take a good look at that stuff when you look at people's profiles, right?

What do you mean, you never look at people's profiles?

Basically, I've come to believe that my reasoning for wanting to click "Like" on stuff (to tell my friends I like it) is flawed. My friends don't typically see it. If they do, they don't care.

You know why?

Because they see it in advertising.

The main reason Facebook has "Like" is so they can sell advertising to you and your friends. "Michael likes Coke, so maybe you, his friend, will like this ad from Coke!" (This is why, by the way, there probably will never be a "Dislike" button.) I find this annoying, and I've decided I'm not going to be complicit in it anymore... but I have far too many "Likes" to "Unlike" them all at once. Besides, I've "Liked" a few of them on purpose. I want to see updates from that band on the road, or hear what's going on with that software package I use, or whatever. So starting today, I've decided to "Unlike" one single thing I've "Liked" but have no reason to continue to "Like".

I'm tweeting my daily Unlikes in my Twitter stream, using the hashtag #UnlikeProject. Would you like to join me in this quest to stop littering our friends' Facebook feeds with advertising that looks like it came personally recommended? Great! Tweet your unlikes to Twitter when you do, and use the #UnlikeProject hashtag. Let's see how many people are freeing themselves from being stooges for Facebook's advertisers!


(After the first month, I wrote a followup post. Here it is!)


Do you have a different take on Facebook "Likes"? If you do, please click the "comments" link below and join the discussion! And if you are tweeting your Unlikes on Twitter, feel free to link to this post (a short link is http://bit.ly/FBUnlike) to explain your reasoning.

Friday, September 16, 2011

Google Plus

My first post on Google+ was made on July 1 at 9:06am. My boss had scored an account over the weekend, and was wondering if I was using it too. I actually hadn't heard of it until he told me; I had been a little bit out of the tech news loop because of a big project at work, but when I heard, certainly I was interested! He had "shared" something with me - at the time this was the only way to get an account - and so I was in. The post was a link, shared only with him, to this Mashable article about the then-upcoming Gmail update.

I was immediately hooked! This was like Facebook, minus all of the things about Facebook that constantly annoyed me! This was awesome! This was... this was... well, sort of empty. It was like arriving at a party at the newest, coolest venue in town, but nobody had arrived yet. The primary attraction of Facebook is that everybody is there. All your friends. Everyone you've ever met, it seems, is on Facebook. The only people on Google+ at the time were you and the person who shared something with you, and the other guy who you shared something with and talked into trying it out. All the coolness, but none of the people.

On those counts, things haven't changed too much 2½ months later. It's a little easier to get an invitation (in fact, if you need one, feel free to use one of mine), but so far the general public hasn't particularly seen a reason to jump ship on Facebook, or even bother to try out another social networking service. And heck, after Google Wave in 2009 and Google Buzz in 2010, who could blame anyone for not jumping on a Google social networking site right away? I think Google is getting it right this time, though. The interface is Facebook-like enough that it's not too hard to understand what's happening, but it's different enough in good ways that the experience is much nicer. I have several friends who actually have jumped ship on Facebook for G+ (although I doubt most people will completely abandon Facebook any time soon... too much history there). I'm not deleting my Facebook account, but I'd love to go all-Google+. Problem is that there are a few things that are making that difficult at the moment... and there are a few more things that, should they happen, would make a move to G+ almost a no-brainer for me. Keep in mind that G+ is really still officially "in wide beta-testing" which means that the public has access, but it's not to be considered a complete product yet. It's entirely possible that some of the things I'm going to mention are in the works. I think it's probable that a few of them are on the drawing board. Let's see how prescient I am!

I'm so impatient about the lack of an API for programmers. At this writing Google has released a very minimal, first-iteration API limited to only reading public profile information and public posts. I can't wait for the release of something more substantial; I use TweetDeck for posting to Facebook and Twitter, and I would love to be able to use it (or Hootsuite, or whatever) to post to all three. Right now it seems the only way to post to G+ is using the Web interface or one of the mobile apps. I have a mobile phone, but it's a Java-only "messaging" phone, a free feature phone from several years ago; it doesn't run Android or iOS.

That leads me to another thing I'd like to see: better SMS support. I have G+ set up to forward status updates from several of my friends to me vis text message, but I can't respond to those messages via text, and I can't send posts of my own via text. I text posts into Twitter and Facebook several times a day most days; I'd love to be able to do the same with Google Plus. Even just sending new posts that way to a default bunch of circles that I specify ahead of time would be useful. I'll be getting an Android phone when my contract runs out on this phone, and at that point I'll install the G+ app, but even then I could see SMS as an easier way of firing off a quick post than starting up an app. And with SMS posting, I can actually cross-post to several services very easily, just by sending to multiple recipients.

I'd like to see RSS feeds made available for posts. You can already use third-party hacks like this one to pull down a feed of your public posts (or roll your own using the API that was just released), but it would be nice to be able to create "private" feeds based on your circles (something you can do with calendars in Google Calendar). I'm using the hack I linked to above to cross-post my public G+ posts to Facebook by running the feed through Feedburner and Twitterfeed. It would be SO awesome, instead, to just share a post with a "Facebook" circle or a "Twitter" circle and immediately shoot the post out via a custom RSS feed!


Part of the talk when G+ was first launched was about incorporating it with other Google properties... Picasa was of course a launch-day incorporation, but what about other properties? Here are my two favorite no-brainer Google properties to incorporate into Google Plus:

Google Reader. G+'s "Sparks" functionality mirrors some of the functionality of Reader; how difficult would it be for G+ to represent your Reader feeds or lists as Sparks? Or, coming from the other direction, wouldn't it be cool for Reader users to be able to easily do a one-click share to G+?

Blogger. Many G+ users are very nearly using G+ as a blogging platform anyway; why not optionally integrate Blogger blogs into Plus so that there's none of this post-the-blog-entry-then-share-it-on-plus nonsense. Just magically allow the blog post to show up on Plus when it is posted to Blogger. An added bonus: combine blog comments and G+ comments so that if I post a comment on a Blogger/G+ entry in Blogger, the comment also shows up in G+, and vice versa. I would LOVE to automatically have more comments on my blogs because comments flowed in from Plus users! Another bonus integration: automatically (but optionally) convert a blog to a Spark, so when you see a blog post from someone you like (say, a friend of yours reshared it) you could follow that blog without having to circle the blogger.

There's a lot of potential in Google Plus! I hope to see some of this stuff happen in the near term. If Google suddenly today rolled out all of the things I've mentioned in this post, for me it would be like knocking the walls out and letting the sunshine in. I really would love to be able to use Plus as my social networking hub and flow information out from there. With these kinds of adjustments, it could happen.

Tuesday, November 2, 2010

Swimming Out of the Shallows (a book review)

Today I reached the end of a unique experience. I finished a book which I found interesting and highly informative... but I completely disagreed with the author's conclusions. I don't dispute any of his facts, but in my opinion, he's adding two and two together and getting five. Or maybe he's adding two and two and getting negative four. Whatever it is, I think he's placing the blame for bad things in the wrong place, and I think he's seeing evil where evil doesn't exist. He's looking at Benjamin Franklin flying a kite and he's saying, that flimsy kite proves that there will never be a 747 carrying passengers across the Atlantic.

Before I go deeper into my thoughts on the book, I'd like to let the author of the book have his say. His name is Nicholas Carr, and the book is a highly-expanded version of an article he published in The Atlantic Magazine. Here it is. Go take a look... I don't mind. I'll wait right here until you get back.

The book I read is called The Shallows: What the Internet Is Doing to Our Brains. The basic premise behind the book is that the Internet has caused us to become shallow thinkers, incapable of deep, sustained thought. Carr says that he first started to notice this phenomenon in himself and in his friends. Journalists who no longer do thorough research, instead opting for the easy "click a few times on the Web and find what you need" method. Literature majors who no longer read complete books. That sort of thing. He believes that this is a trend which has to do with heavy use of the Internet, which is making changes to our brains as we surf, rendering us incapable of creating, or even following, longer trains of thought. He takes a great deal of time describing how the adult human brain, once thought to be quite set in its ways, is actually very flexible, changing all the time. Every time you or I do something, a physical change takes place in our brains, creating a memory or cementing a habit. He then goes into the history of writing, starting from brief scratches on ancient shards of pottery and proceeding through several technological changes: writing on clay tablets, the invention of paper, the refining of single-sheet paper into scrolls and eventually the codex (which we usually call a "book" - sheets of paper bound in a cover); the idea is that the computer is the thing that will usurp the role of the codex, in much the same way as paper usurped the role of clay tablets.

And, Carr believes, the Internet is designed with distraction in mind. Emails arrive. Tweets tweet. Ads flash and distract. Hyperlinks take our attention away from the text in which they are embedded. SMS messages come in our our phones. New blog entries hit our RSS readers. Spending our time being variously distracted by all of these things is, Carr insists, making changes in our brain that make it impossible to not be distracted. I agree with everything Carr says, up to that last sentence: I think that the Internet plays a role in our being distractable, but the Internet is not the perpetrator: the Internet is just the tool that the real perpetrator is using to make us distractable. The actual perpetrator is: ourselves.

A book is a highly static medium. I'm talking about a physical, bound book. It doesn't change on its own. It doesn't react to signals from elsewhere. If you tear a page out or drop it in the toilet, of course that will make a change to it, but it doesn't change on its own. Carr explains that before the codex was invented, human beings thought in shorter bursts. A verbal lecture might hold the attention of someone for a longer period, but other than that, your attention didn't really have to last any longer than it took to read the words scratched on that clay tablet. Because writing was time-consuming and difficult, it was generally reserved for extremely important (and brief) documents such as legal documentation. But when the bound book was invented, and particularly when the printing press came to be and books became quite cheap, anyone could have something in his hands that required many hours of sustained concentration to take in. This resulted in changes in the brains of the readers, strengthening their abilities to concentrate on one thing and filter out distractions. Carr had concluded that because our computers interrupt us almost constantly, the constant barrage of interruptions (which we respond to) train our brains to be distractable.

Let's think about that argument a bit. If ancient man was distractable because his (eat or be eaten) environment demanded it, and "codex" man became a "deep reader" because books demanded it, and "Internet" man is becoming distractable again because his computerized environment demands it, isn't that a return to the more natural state of mankind? I'm not sure there is a way to determine whether "distracted" or "immersed and oblivious to surroundings" is a better way to be, but it seems that it would depend on the lifestyle and needs of the individual. For example, someone who lived in a dangerous part of the world would be well-served by being distractable; it could save their life if something in the corner of their eye makes them instinctively duck.

And really, what is it about most books that makes it so helpful for us to immerse ourselves in that environment? When you have immersed yourself in a book, you have allowed one human being to insert whatever he or she wants directly into the world of your experience. That author is controlling, to some extent, your thoughts and your interpretation of events or facts. Is that actually so much better than a quick jaunt across the Web, picking up facts from many sources and building your own composite picture of reality? I say this as a pretty avid reader myself; I love books, but there are definitely advantages to having instant access to multiple trains of thought. The tyranny of one author controlling your thoughts for an extended period is replaced by many voices competing for your attention, giving you the chance to choose best-of-breed for yourself.

There are a number of reasons people have trouble reading long articles on the Internet, and it's not all because of their email "ding." Reading on a computer screen basically is not fun. I say this as a person who has read an entire book, in pdf format, on a computer. Backlit computer screens are hard on the eyes, and people don't necessarily have the most comfortable reading environment set up in front of their computers. It's not that people can't read a long article on their computer; it's that people don't want to read a long article on their computer. But given a strong enough desire, they can and will. I've done it many times. If you've read this far, you're doing it right now. It's completely possible. You are the captain of your own fate. I predict that as e-readers such as the Kindle and its brethren become more and more popular and inexpensive, people will read longer articles, and even books, much more frequently in digital formats. The technology will continue to adapt to become more comfortable for human beings, just like reading and writing technology progressed to ever more useful forms.

So, does Internet use make it impossible for people to read physical "codex" books? Of course not! You can't say that just because you've trained yourself in such a way that it is difficult for you to focus, your brain is ruined for life and you'll never be able to focus again. The mere existence of technologies does not force you to enslave yourself to them 24 hours a day, seven days a week. And their existence doesn't mean that you even  have to use them at all!

I like candy. Most everyone does. I'd like to eat lots of candy! But if I eat a lot of candy all the time, my body will become sick and fat. Candy is okay in moderation, but too much is too much. Burger King is convenient and always available, but if I eat Burger King every day, all the time, I'm going to become very unhealthy. Burger King is okay sometimes, but it shouldn't become your constant diet. Too much is too much. And if your constant mental diet is making your brain sluggish and fat (or hyperactive and ADHD), maybe it indicates that you are being irresponsible with your use of the technology. The tech is not at fault; your bad habits are.

And really. Distractions are nothing new, and they are not limited to technology. I spend about an hour and a half every weekday reading physical books on my bus commute to and from work; and believe me, distractions are everywhere. Someone behind me having a loud conversation on a cell phone. People getting on and off. Things outside the bus. Announcements by the driver of which intersection we're at. Some of these distractions are important for me to respond to (for example, I need to remember to get off the bus when I get to my stop!) Some of them are unimportant, and some are just a nuisance. But I get through my books eventually, because I've learned to tune out the unimportant distractions. The same goes for the Internet; I've unconsciously learned to tune out the things I don't need to concern myself with, and only respond to distractions that matter. In fact, sometimes I tune out distractions that do matter, which is why I have to change my "new email" sound every once in a while... I've spent whole days not noticing that I have urgent items in my inbox!

Let's talk about some of those distractions. Let's talk about that email indicator, that Facebook ding on your phone, that text message from @AplusK on Twitter. Are they distractions? Do they break up your work day and keep you from concentrating? Yes? They do? How about this: TURN THEM OFF. If they're a problem, eliminate them. The distraction is not forcing itself into your life; you have brought it on yourself. Eliminate your own distractions. Simplify. Your brain will respond to that, just like it responds to the opposite. If our brains are so elastic that they can be negatively changed by negative environmental factors, then they are also elastic enough to be positively changed by better environmental factors.

It's nonsensical to blame distractability on information overload, too, although it's true there is a real glut of information available to each of us on the Internet, information about pretty nearly anything you can think of. One thing I've seen computers bring a huge change to in my own personal life is Bible study. When I was a kid, Bible study was, obviously, all about books. If you wanted to study a topic, you looked it up in commentaries, topical dictionaries such as Vine's, or study Bibles such as the good old Thompson Chain Reference. You could also take a word-based attack, looking up your word in Strong's Concordance (which contained every English word in the King James Bible, along with original language dictionary for translation assistance). It was kind of slow, but it could get you where you wanted to be. Fast-forward to today, when that Strong's Concordance lookup that took you two hours with the book can happen on your cell phone in seconds. But do you really want to find every verse in the Bible that contains the word "love," or do you want to learn about a specific kind of love? How much God loves people? How a husband loves his wife? How a man loves his neighbor? For that, your speedy word-based lookup is only a good starting point. Those commentaries, topical dictionaries, and other study helps are all out there in digital form, accessible at the click of a mouse, but to really understand the Bible, you have to go deeper. You have to do it on purpose. You have to not take the easiest way out. The problem is not a glut of information; the problem is intellectual laziness. The same goes for journalists that go for the "easy kill" without really checking out their facts (like this utter nonsense, which I heard reported last weekend on my local TV news... reporting the 823-year urban legend as fact). You have to actually care enough to take your time, even on a computer, or eventually you're going to wind up looking like a fool. You have to be wise in your use of the tools at your disposal; scatterbrained research leads to scatterbrained thinking.

Let's talk about communication, because Carr seems to think that digital communication is de-humanizing us because when we text message or IM, we are not face to face with the person we're communicating with. Hogwash. Consider people who, in centuries past, sustained long-distance romantic relationships via letters which had to be carried across oceans in ships. Consider people who stay in touch today with distant loved ones via telephone. Those lovers with the quill pens would have loved to have been able to pick up a telephone, but they used the technology at their disposal. Communication is communication, no matter what form it takes, and over time, communication becomes more human and personal, not less, with the introduction of better and better technology. Today I can start up Skype and see and hear moving video of a friend on the other side of the world. For free! I can call or text my wife's cell phone, and no matter where she is (within coverage, of course) I can reach her. In the past year or two I've become involved again in the daily lives of friends I haven't seen for 2 decades, via Facebook. Without those technologies, none of that communication would be possible at all. Okay, so it's digital; that means that the communication is carried on electronic impulses instead of through the air or in an envelope on a ship. It's not a sign of the decay of human interaction; it's a sign that people will communicate, and if it takes a computer to do it, so be it.

Carr also seems to think that there is a chance that people will try to (and already are trying to) sort of "outsource" their human memory to computer memory. But then he explains himself that that is impossible, and gives the physical reasons why it is impossible. Your brain, despite what may have been taught to you in fourth-grade science class, is not a computer. It's not even very much like a computer. Computer memory is not like organic memory, if only because computer memory is digital and organic memory is not digital. You can have a strong memory and you can have a distant, hazy memory; a computer can only have "yes" or "no". Either the computer knows it, or it doesn't. And most of your memories aren't things that you could even figure out how to offload into a computer anyway; your brain is full of pictures, sensations, smells, sounds, ideas, impressions... all things that cannot even be communicated to a computer, and even if you "offload" them to a computer somehow, they remain in your brain as well. The only thing computers are really good at is "computing" (math), and they do a fairly good job as storage devices for data which is much less complex than the things inside your brain and mine. Tools like Evernote can help you remember your shopping list or the date of the Gettysburg Address or what your kids want for Christmas, if you store those things there, but those tools can't help you remember how the meadow behind your house during your childhood smelled in springtime. I know they call it "computer memory." It's not. It's storage space for ones and zeroes.

Does the Internet cause some kind of brain damage? You might argue that; every single thing you do all day long causes minute changes in your brain, and if those changes are unwanted, you might call them damage. Is this damage irreversible? Not according to Carr's book... it says that the human brain is quite flexible and adaptable. The argument that your brain is so flexible that Internet use changes your brain, but then that the changes are permanent and damaging, is circular, self-defeating, and illogical. At any point you can choose to change your environment. Ironically, in the chapter on "how I wrote this book," the author tells about how he did just that... shut off the email and the IM and the feed reader and Facebook and Twitter, and re-taught his brain to focus. Even he, the arm-waving paranoid alarmist, found that all he had to do to work with no distractions was to remove the distractions. Why is this rocket science? Turn off the "ding" and your brain remembers how to concentrate on one thing at a time. The "can't" automatically becomes a "can."

My best take-away from this book is that it has reminded me to re-examine my own work habits. What is distracting me? What do I need to cut back on so I can work uninterrupted? Am I wasting whole days by remaining distracted from morning to night? More than once since I began reading the book, I've considered my environment and adjusted things, or turned things off, or un-followed or un-friended. or whatever I needed to do in order to simplify. That's certainly been a good, helpful thing. The information in The Shallows is fascinating, but the freaking out is unwarranted. If the brain is as flexible as the book says, it can snap back from almost anything... including Gmail and Twitter. Take charge. Don't sabotage yourself by creating a hostile Internet environment! Use a little common sense, and the Internet will be your friend and not your enemy.

Monday, October 12, 2009

Twitterfeed

If you follow my Twitter account, you'll notice that whenever I post to one of my blogs (there's a list of them on the right-hand side of this page) a tweet always shows up. I don't do this manually; I use a great service called Twitterfeed:





Twitterfeed is a simple service... you set it up with an RSS feed and with your Twitter account(s), and then when new information is added to the RSS feed, the link automatically gets posted to Twitter. I don't limit its use to my blogs, either... I use a service called WorldCat.org to keep track of books I read and movies I watch, and it can output RSS feeds as well. So when I read a book, everyone following me on Twitter automatically knows it! That's just for fun... the best thing is that it helps me publicize my blogs without having to think too much about it.

Something else I like about Twitterfeed is that it allows you to create an account using OpenID. This is accomplished using a nice service called RPX which handles all of the confusing parts of implementing OpenID. If you click "Sign in with OpenID" you'll see this screen:



RPX-powered login screen
 Click the logo of one of the services on which you have an account, log into that service (if you are already logged in, as I usually am with my Gmail account, you're all done without having to log in again at all!), and your Twitterfeed account is ready to go! It couldn't be simpler. I'm planning on incorporating RPX into the redesign of my Guide to Petra Web site, coming up soon. As it is now, people have to go through a series of click-a-link-in-this-email steps to use the interactive portions of my site; this will work MUCH more smoothly!

You can set up multiple RSS feeds with one single Twitterfeed account, and you can actually post to multiple Twitter accounts as well. It also supports some services I hadn't heard of... laconica, ping.fm, and HelloTxt are in the drop-down. I've tested it with more than one Twitter account, and it worked great. You "link" the account using OAuth (basically, you log into the Twitter account from Twitterfeed) and then you put in a "Feed Name" and the URL for the RSS feed. And then you're done! Of course, there are some great "Advanced Settings" you might want to look at:


Twitterfeed settings for this blog
My favorite things to change are the "Update Frequency" (I set it really long because my blogs seldom update more often then once a day) and the "Post Prefix" (which is added to the beginning of each tweet), but there are also some other settings you might want to look at... whether the tweet is the title from the feed, the description from the feed, or both, for example, or whether the "newness" of the posts is determined by pubDate or GUID (if you don't know what that is, try one and see if it works as you expect... if it does, you're good). You also have the option of using any one of a large batch of URL shorteners... I use bit.ly (you can even give it your account information, if you like to use a bit.ly account) but TinyURL is there, and SnipURL, and a couple dozen others.

Once you have some feeds set up, the feed dashboard (which shows a list of all of the feeds you are automatically sending to Twitter) provides some interesting information; link click-throughs are tracked and displayed as bar-graphs. If you use Feedburner, as I do, you can even set things up so that you know how many click-throughs came via the bit.ly (or other service) link, and how many came directly through the Feedburner link. If you are thinking of using Twitterfeed for a business purpose, these kinds of metrics could be very informative.

The only time I've found the service to be anything but reliable was during a recent Twitter outage... but during the outage, Twitterfeed communicated status reports frequently through their own Twitter account. There was never a time during the outage that I felt like I didn't know what was going on with Twitterfeed. It truly is a set-it-and-forget-it situation; it just works, day-in, day-out. It's the glue that connects my social network friends with my blogs, and I've seen more comments than ever before on my blogs in the weeks since I started auto-tweeting my new posts. It's been a great help to me in getting my blog posts noticed!

Friday, October 2, 2009

Google Wave: What I'd Like To Use It For

This week there's been a lot of chatter about something called Google Wave. The reason the buzz ramped up this week is that Tuesday Google announced that they would be expanding their beta-testing to 100,000 more users (plus their friends and relatives, apparently, because each invite comes with more invites for buddies attached). Wave is not something that is easy to explain in a few words, although the concepts are not hard to understand. It's kind of like email, except with the immediacy of an instant message and the editability of an online document. I know, that doesn't seem to make sense, so you have a couple of options to get you up to speed for this post. You can go to wave.google.com and watch their eighty-minute video... but who in the heck in this Twitterized, cell-phone-infused world has eighty minutes to sit and watch a video online? Instead, I recommend that you take a look at this one. It's a lot of fun to watch, is quite a bit shorter than the ten minutes they mention at the beginning, and it'll help you wrap your head around the basics:



Back? OK, so that kind of explains it. If you're still having trouble or want some more detail, I thought this Lifehacker article was helpful. Go ahead, I'll wait for ya.

...

OK. So Google Wave is looking like the coolest thing to come down the pike in a long time. Basically, it's a platform that a bunch of other things can kind of piggyback on. Now, I've been reading some articles on how people envision that Wave might be helpful in what they do... businessmen, for example, or newspaper writers or even filmmakers. For myself, the first thing I thought of when I saw it was, "That looks MUCH nicer than Facebook!" Indeed, some have speculated as to whether Wave could eventually do in both Facebook and Twitter, and I agree that it may give them (or the bug-riddled Facebook, at least) a run for their money at some point (of course, if they're smart they may actually incorporate the Google Wave technology themselves and then it becomes a question of who has the cooler interface and the most users, but anyway). But the more I thought about the capabilities of this thing, the more my mind started going in another direction.

Where I work we've been on a quest to find an effective trouble-ticket system. Our business is almost completely centered around what we can do with our Web sites, and customized computer coding is what I do all day long. When something is wrong with one of our sites, we get an email or a phone call, or sometimes we get a "drive-by" request (those are pretty common when your office is on the way to the bathroom for a lot of people!). Once upon a time we hired a contractor to build a trouble-ticketing system for us. It worked OK, and it was integrated with our internal systems, but there were still some things about it that were inflexible and caused problems. To a computer programmer, writing a ticketing system (someone logs a problem into the system, it is classified and prioritized, someone works on it and solves the problem, the ticket is closed, end of story) seems like a deceptively simple task, but things get complicated VERY quickly. Who can see the ticket I'm working on? The person who submitted it? What if they called it in on the phone and someone else keyed it in? Can they see my comments? I need to add a comment that is critical for developers but which might be confusing for end-users. What do I do with the screen shot the user emailed to me? What about this pdf they sent in as an example? Trust me, it gets crazy quick. So we abandoned the home-grown system and began shopping.

First we tried out a system called Trac which our I.T. director had used at a previous job. Trac is a combination wiki/ticketing system, and there are some things it does incredibly well... automatically linking text in the format "#123" to trouble ticket #123, for example. We ran into problems, though, when we tried to figure out ways for our customers to see the status of their tickets. There's just no obvious way to show part of what's in the system; it's pretty much an all-or-nothing proposition. So the I.T. director went shopping elsewhere.

Enter Jira. Besides the fact that the name makes me want to say "Gojira! Gojira!", the software is able to do all of the things we need it to... there is a flexible permissions system that allows you to show things to only the people who need to see them, but there are other great bells and whistles (like pasting in a screen shot directly from your Windows clipboard... how cool is THAT?) that impressed us so much that we are likely going to adopt it as our new ticketing system very soon. (It is a commercial product, by the way, but I am receiving no compensation for mentioning them.)

But just for a second, let's think about how Google Wave could be used as a trouble ticketing system. The hypothetical Wave-based ticketing system need not reside on Google's servers; the platform will be open-sourced, so the ticketing service could be a private machine owned by the company using it, or it could even be on a third-party hosting provider. Each new ticket would be a wave (when "wave" is lower-case, it means a particular "message thread" or "document", as opposed to the upper-case "Wave" referring to Google's product as a whole). When a ticket is opened by internal personnel, all of the stakeholders could easily be added to the wave; if the ticket comes from an external source, when the staff became aware of it they could add stakeholders to the wave themselves. As progress is made on the ticket, technicians could update the wave, and even add questions for the client; the client could modify or add information as necessary. I was particularly intrigued when I visited the Wave extensions page and saw the Ribbit extension. Assuming enough storage space is available to store them, the wave could conceivably hold the entire contents of a conference call, recorded for reference back if needed! Tickets could also be submitted via telephone and immediately and automatically added to the appropriate waves. Those audio tickets would be exactly what the client requested, with no intentional or unintentional translating done during data entry. The phone call IS the request.

The possibility of adding robust phone call/teleconference recording capabilities to the wave would be what would make it a killer app for trouble ticketing. One of the most frustrating problems we have with some of the people that we do work for is that a request is placed via telephone and either misunderstood or forgotten, and then it winds up never getting taken care of properly (or messed up, which may or may not be worse!) To be able to go back and follow every part of the ticket wave through its complete development, to have that granularity on the project, would be invaluable. It would be like the difference of getting where you want to go via horse cart, automobile, or jet plane.

Why oh why couldn't I have been one of those first 100,000 to request access? :)

Monday, September 28, 2009

AutoTweeter Pro

I haven't been on Twitter very long, but I'm a sort of scattered thinker, and I had been tweeting only a few days when I found that I would get on a roll, thinking of things I wanted to tweet, and tweet five or six times in rapid succession. I also discovered that whenever someone else did that, I hated it. Especially if they kept going... nine or ten tweets in a row and my whole Twitter home page was filled with one person's profile picture. I realized that what I really needed was a way to kind of queue up those tweets and let them out a little at a time. Enter AutoTweeter.

AutoTweeter is a tray application for Windows. The basics are very simple: you save your tweets into a plain old Notepad-friendly text file, tell AutoTweeter how often you want to tweet them, click on "start tweeting", and AutoTweeter does the busy-work for you. Very straightforward. And it works like a charm... I can queue up several tweets at a time and let them come out every 60 minutes, 45 minutes, 30 minutes... whatever I want. I even spent an entire Monday recently, just for fun, letting AutoTweeter tweet random Animaniacs quotes every fifteen minutes! And I instituted a new tradition for my Sundays... throwing a list of quotes from a VeggieTales episode at it and letting it tweet one every thirty minutes all day (get laughs! Annoy the living heck out of your friends! That tradition ended with some thinly-veiled hostility from those same friends this weekend... lesson learned. Not everyone loves VeggieTales.) Usually I use it at work during the day, queuing up tweets on the fly, so when I think of two or three things to say I can spread them out over time and keep adding to the list as I go. During the day I'm seldom without a fresh tweet for more than an hour at a time! And I never have to worry about "spamming" my friends and followers (at least, not since I cooled it with the VeggieTales thing).

Anyway, let me explain how AutoTweeter works, and then I'll tell you the good things (there are lots of them) and the bad things (there are a few) about the application. AutoTweeter has no installer (a plus in my book); you just unzip it to any location you like (I put mine in C:\Program Files\AutoTweeterPro), click the .exe file, and you're ready to go. An icon that looks like a bluebird's head will appear in your system tray; there's a little bit of fairly straightforward setup to do first, so you will have to double-click it to look at the dashboard. First you'll need to go to the "configure" tab and put in your Twitter username and password; there's no OAuth support in this release so it's old school authentication for now (I understand OAuth is in the plans for a future release). You also might want to change the default tweet interval from 1 minute to something longer unless you're going to have a tweet file that has a lot lines in it... and friends who will put up with you tweeting every sixty seconds!

The default tweet file, sample.txt, has one tweet in it already, but you will almost certainly want to set up your own file. You can set up your own .txt text files in the autotweeterservices directory (in my case, C:\Program Files\AutoTweeterPro\autotweeterservices) and even switch between them whenever you want. I set up a file called tweets.txt in that directory and then put tweets.txt next to "tweet file" in the "configure" tab. Make sure you click the "save" button or else your changes will be lost. (If you leave the default tweet file in place, the first tweet is an @-message to the software's creator... which is not a problem, but you probably don't want your permanent tweet file to be called "sample.txt"!)

Once you have everything configured, you're ready to add some tweets. You can use a text editor like Windows Notepad, but a much easier way to add tweets is the "auto tweet" tab. The auto-tweet tab has two boxes: the large box for the tweet itself, and a "shorten url" box. Type your tweet into the large box, and click "tweet later" and the tweet will be added to your tweet file. You can add as many tweets to the file as you like; however, the trial version will only send fifty tweets before it automatically stops tweeting (we'll talk more about the limitations of the unregistered version in a minute). The "shorten url" functionality is disabled in the trial version.

If you want to tweet right this minute, click over to the "quick tweet" box and add your tweet there. Once you click "tweet it," your tweet immediately goes to your Twitter account. I just used that function to tweet "Writing a blog post about #AutoTweeterPro!" It's very handy if you don't happen to have the Twitter Web site open but have something to say, and you don't want to queue it up in your AutoTweeter tweet file.

The "house keeping" tab helps you to keep track of your tweet files and how many tweets are left in each. If you did what I did (creating a tweets.txt file), when you click "load data" you will see that the sample.txt file has one tweet in it but zero have been sent, and the tweets.txt file has zero tweets in it (my "quick tweet" never went to the tweet file). There is also a "delete" button (which actually physically deletes a tweet file... you can use it to delete your sample.txt if you like), and a "reset" button which is disabled in the trial version.

Let's talk about the limitations of the unregistered version. Registration at the current time is $15, and it is well worth the price if you like the unregistered features. Once you register and your key is in place, the "reset" button becomes active, and you can reset the "tweets done" to any number... for example, if you had a 50-line tweet file and you had tweeted all of them, you could reset the "tweets done" to 26 and tweet the last 25 tweets again. The process for doing this is a little bit clunky (check the checkbox for the file you want to reset, click under "reset to", key in the new value, click under "tweets done", and click the "reset" button) but it gets the job done. You can manually change this value in the configuration file using your text editor, but it is certainly more convenient to make the change right in the "house keeping" tab. The "shorten url" boxes are another terrific convenience you get with registration; using those boxes, you can change any http://www. URL to a bit.ly link without having to go to the bit.ly Web site. Oddly, any URL that does not start with http://www. will be rejected by these boxes... https: URLs are not acceptable (even though bit.ly handles them just fine) and any URL that doesn't start with a "www" will not work (for example, one of my blogs is http://blog.ScriptureMenu.com... no good for the "shorten url" boxes). It would be nice if this box would accept any URL... limiting it this way seems kind of odd.

Another (intentional) limitation of the unregistered version is that the "repeat tweets" and "windows startup" checkboxes are disabled. I can't imagine a situation when I personally would want to "repeat tweets" unless I decided to run a service of some kind where I had hundreds of tweets in my tweet file and wanted to recycle them every so often (quote of the day services or such). The checkbox is mostly there for Twitter marketers, so if that's your bag, definitely pony up the $15 for the registered version. When I checked the "windows startup" checkbox, AutoTweeterPro started up when windows started, but for some reason it couldn't read the configuration file... I had to exit AutoTweeter entirely and start it back up manually to get it to work. Your mileage may vary... I think I may have moved the executable file after the first time I used the software, so maybe that was the problem. For that reason, I'm not sure if a power outage would mess things up or not; if the computer came back up, the software would come back up, but I don't know if it would be tweeting without a manual click or not (in my case, until I logged into the computer, I would be out of luck anyway!) I also had a little trouble getting my registration key to "stick" when I first registered; the tech support people were very patient with me and we finally got that worked out. The registration process is fairly simple; you make payment via Paypal and a key file comes in your email. The key file just needs to be present in the folder where your executable is.

There are a few minor things about the software that bother me. When you click "start tweeting", no tweet is immediately sent; if you have your interval set to 60 minutes, it will be 60 minutes after you click "start tweeting" before any tweets go to Twitter. Not a bug, but something to be aware of. The presence of the "quick tweet" tab helps a little bit on this.

Also, sometimes I wonder if tweets added to the queue will happen without clicking "start tweeting" again, particularly if you've already tweeted the last line in your tweets file. If there are two or three tweets left in the queue I don't notice a problem, but if I'm on the last tweet already, it seems like the software loses its place. To make things worse, the "tweets done" number in the "house keeping" tab doesn't always update when tweets happen; it definitely updates when you exit the software, but the program doesn't update the configuration file on the fly, so re-loading the data while you're tweeting doesn't tell you anything new. And you're on your own if you try to manually update the tweet file or configuration file with a text editor while the program is running. It would be nice to have a way to view or even edit the tweets file on the fly; I keep an eye on the tweets file using a text editor, but I would certainly rather keep that within the program. And if the configuration file was physically updated after every tweet, it might provide some more useful information in the "house keeping" tab while you're tweeting.

A BIG update I would love to see is a deamon that could be run as a Windows service. That way, even if I was logged off of the computer I could be tweeting. For most people that might be overkill, but at work I log off when it's not business hours, and at home, each member of my family has his or her own login for the computer. If I'm logged off either one, no auto tweets. This would also solve the power outage problem I mentioned before. Maybe for version 3.0?

Overall, I really like the software! It is a tremendous step up from the previous version, which started out as just a sort of daemon for tweeting a text file; initially there was no gui at all. The dashboard is a much easier way to control the program. I know there are online options to queue up tweets, but for sheer immediacy of access and ease of use, AutoTweeterPro is a terrific option. Visit www.autotweeter.in and try it out! And if you like the trial version, consider spending the small amount to register. It's worth it to remove the software's built-in limitations, and it never hurts to help support a developer who is making software you enjoy!