Below I’ve embedded my first attempt at a screencast, which I’m putting on here to solicit feedback upon but also to make notes for myself about lessons learned in the process.
Takeaways from this first experience:
it’s harder than it looks!
I will either need to pre-script the audio or re-record the audio track over the video — attempting to cold-record the audio admits far too many flubs
I need to set my video encoding resolution better for Youtube (I think they’re HD is 1280×720)
Anyway, there you go. Click through for a larger version to make it easier to read what’s going on.
(As a moderate Twitter user but total geek, I’ve been meaning to write this for a while. Hopefully someone finds some usefulness in it.)
(Before someone comments, I know this could be done with a command line Twitter client, or I could just write one Python/PHP/etc. program to do it, but that would entirely be missing the point. Command line tools are extremely powerful and fun to use once you get some experience with them!)
The original idea for this came from The Apple Blog, but it has been heavily modified.
My desktop tends to be quite busy, and even with two 24″ screens, I find that I’m constantly out of screen real estate and don’t want to have yet another client open to display my Twitter stream. GeekTool to the rescue. GeekTool allows you to display the output of a shell script or a URL or file to the screen and refresh it at some defined frequency.
First, here’s a screenshot of what it looks like having my most recent 15 tweets visible on the screen, and what this tutorial is going to cover:
So who all of the readers of this blog uses Google Reader for their daily blogging enjoyment? Further, who uses the shared items feed?
I ask because I currently only have Petter, Tom, Stacey and Chutz as ‘reader sharing users’ in my Google contacts. If there are any other of you out there, please let me know so I can add you to my Gmail address book. The last few months have only reinforced my belief that the sharing feature is probably the best part of Google’s RSS reader. I consider it the ‘person’ filter of the world. For example, Petter is an excellent critical thinker and developer and he reads blogs which seem centered on those topics and when he shares an item from one of the 100+ items that he might scan over in a day, I know that it must have a particular significance.
I don’t exactly know where I sit on the whole seal hunt thing that is being widely debated in Canada these days. I honestly don’t know even half as much as I probably should about the whole situation.
What I do know however, is that I really don’t like the actions and accusations of the anti-seal-hunt people — the group I know of as the Sea Shepherd Conservation Society (I will not link to them…they are stupid). On Saturday their boat was raided by the RCMP and the captain and first officer were arrested for their dangerous use of the ship in ramming a Canadian Coast Guard vessel.
Of course, as soon as the rest of the crew gets back to shore we hear stories about how they were all innocent, why, in fact it was the Coast Guard that rammed them! (Forgetting the evidence I’m about to describe, seriously, how likely does this sound?) After which their boat was taken into custody in, get this, an act of piracy!
So, watching the news last night they showed one of the boat collisions, taken by a crew member of the Sea Shepherd’s boat. And what could you clearly see, with only a modicum of common sense? If you watched the motion of the image, and the boats, with respect to the ice, you could see that the only boat that was even moving was the Farley Mowat (the Sea Shepherd’s boat)! So if only one boat is moving, and there’s a collision, who exactly do we think is responsible?
Just another case of the so-called peaceful protestors doing what they do I guess. But when you’re weilding a multi-hundred ton boat as a weapon, I totally support the actions of the RCMP.
Oh, and btw, McDonald’s totally needs to start serving baby seal on a bun — McFlubber! (This was thought of years ago by a group of us in J9, I’ve sent the idea twice to McDonald’s — no response yet.)
Well, it became crushingly evident yesterday that at least one person that I work with at Bishop’s has found my blog, when I was called into an office of my peers and read a paragraph (that I actually do not even remember writing) posted some time ago and speaking very critically of the department for which I now work. Not that I regret posting anything on here, nor was I wrong in what I said, but the knowledge inevitably causes you to think differently about what you may speak about in the future.
This should be interesting as I have some work-related topics that I plan on posting about in the next couple of weeks. One would think that working at a university would afford someone with a certain high degree of intellectual freedom as to what they may wish to speak about, but alas I get the sense that those freedoms are only really afforded to faculty, and not staff. We’ll just see I suppose.
I suppose I should write one of those disclaimers… “all commentary appearing on this blog are the personal insights of Scott Stoddard and have no connection either real or inferred with Bishop’s University or the IT Department at Bishop’s University….blah, blah, blah”. In short -> Only my words. Suck it.
Okay, I’ve seen Google do a lot of smart things over the years — and this one is going to get less press than most — but this is the smartest thing I’ve ever seen them do.
Every web application developer should learn about this; it has all of the hallmarks of a product that could lead to revolutionary change on the web. Until now, the decision to build a web app depended on not only your ability to code it, but the availability of a server to run it on (can you set one up yourself? how long will that take? if you do, will it be accessible on the web? can you solve the myriad of maintenance issues?) and/or your ability to pay someone else to host it.
If you are a developer, free up an hour and watch the six videos from the intro last night, part one below:
Just a reminder to Quebec readers or people who are likely to visit Quebec anytime soon…it is now illegal to drive and talk on a handheld cell phone in this province. For that matter it’s illegal to drive and use one hand to hold a cell phone (I don’t get that one…I can has cheezburger but I cannot has cell phone!)
Don’t even get me started on the fact that the holding of the phone is not the distraction point of a cell phone conversation, so this law really misses the point entirely. I suppose however that the alternative would be to make it illegal to talk while driving…I better be quiet with that shit, I don’t want to give this province any ideas.
…to the new blog. There are some aspects that I have not yet ironed-out, such as commenting. The way this system should work, I want people to be able to comment without my having to moderate them first…but I also don’t want any comment spam. I will have to make some additional changes in the next couple of days because right now I have to manually approve each message.
I look on with more than mild interest to see how this will turn out.
Personally, I’m in the category that assumes the result will be…clusterfuck.
If unfettered internet access is offered to the 30,000 members of the media then some travesty will occur. Protests will happen. People will be killed. The journalists will report. And in doing so, should that sufficiently anger or embarass China causing them to block the pipes (or worse, and a significant possibility, they never open them to begin with) the media will still report (you know, that whole ‘free speech is relentless’ thing that we all cherish). That’s all bad news for China…no matter how you slice it. I’m almost certain that these Olympics could generate more negative press about the country than positive.
I’m not against the clusterfuck at all. In fact, I think the country needs a whole host of additional protests, actions and other general forms of defiance. It’s just that every time China ‘manages’ a situation a lot of people seem to die. I wonder how many people they’ll be willing to kill with the eyes of the world on them.
I was listening to CBC Radio this morning and the executive producer of Desperate Housewives was paraphrased saying that he’s spending tens of thousands of dollars a week digitally-processing the nipple imprints of his stars out of each episode of the show. Something about it here. It is 2008 right?
