
In Social Networking, The New Web on January 22, 2008 by endub
Warning: Snarky post ahead
Hey, here’s a good way to get more people as friends on our new social network: take a contact list from somewhere else, and then search for people on our network. Match people on our network by email address, username, or full name.
Email address? I sure hope the person I’ve been emailing has the email address to which I’ve been addressing their correspondence.
Username? Well, that’s probably not as unique… but in this Web 2.0 world, people usually use the same username across a bunch of different sites. Unless they’re like me and can’t make up their mind between nwadycki and nelswadycki. Or if they have a common name, and someone took their username on some other social network. Speaking of common names…
Full name? Sure, no one else is named Nels Wadycki. Might be more of a problem for my friend Andrew Moore. Or Carl Smith. Or Brian Cooke.
Now, I realize that Pownce is developed by a single person, and she has made a significant accomplishment in launching the service single-handedly… but Full Name? Did Leah check with anyone before implementing that? Or are all the Pownce users just supposed to know that their newly imported friends might not actually be the people they’re looking for? This seems especially true for people importing contacts from Gmail where just about everyone ever is added to your address book.

In Actionscript, Chicago, Flash, Longform, Ruby on Rails, The New Web on December 5, 2007 by endub
On a metaphysical level it was nice to have another day off from work. On a realphysical level, it was nice to get back into the routine. And not having to walk all the way from the entrace of Navy Pier to the back. It was a 10 minute walk and I was trucking it.
I took a picture of Colin with my cameraphone, and I was all excited cause I found out the USB cord for my real camera connects to my phone, too. But when I connected it, Windows couldn’t find the software, and so, no picture.
Anyway…
Colin was a great presenter, and I applaud him for presenting for essentially 8 hours (he kept saying 9, but that included the lunch break). I guess when the name is “ActionScript from the Ground Up” I shouldn’t have been expecting any real advanced coverage of the topic. I got a great review of OOP, though, and I’m sure for all the Flash “design” type people there, it was way too fast. It was essentially a 9 week course crammed into 9 hours with no time for homework. So, yeah, I’m sure there were some minds blown. But I also am sure there were people who were bored out of their minds. I was close, but I hung on and managed to pick up things here and there even in the OOP stuff. That said, I’m pretty sure I can skip his book (sorry Colin!) since the reviews on Amazon say that it goes a lot into the OOP stuff. But that frees up some cash, so I can get the RIAs with Flex and Java book I’ve been wanting forever, or else Adobe’s Flex 3 training book. And for Adobe, I think that was the point anyway; just to get people more exposure to ActionScript and make them more interested in using it; so they can stay on top of Silverlight.
I am also glad I got to see how similar ActionScript is to Java. I’d say that AS is probably more like Java than JavaScript. Of course, names for languages really don’t tell you anything about them.
I overloaded myself with the Flex/ActionScript by reading my Flex 2 with ActionScript 3 book on the train and bus to the event. Now, I will try to busy myself with a game I’d like to develop using Flex/ActionScript, and try to also fit in an extra credit project at work using Ruby on Rails. My FA side project will be a good one since I can probably move quickly to advanced Flex/ActionScript concepts since the languages are so similar to what I already know. The RoR project will have a bit more of a learning curve since I’m still getting to know Ruby.
Just an FYI (while I was finding the picture below), I came across this TIOBE software site that ranks programming languages. As of Dec 2007, Ruby is at #9 while ActionScript is #25 (glad to see it’s at least that high; MXML doesn’t count as a programming language). Java is #1 with a 20% share, so I guess it’s good that I’ve got that one down pretty well.


In Google, Social Networking, The New Web on October 30, 2007 by endub
Google properties:
- Google Talk status updates
- Google Reader shared items
- Google Calendar events (added, invited, updated?)
- Google Documents (recent changes, new, updated)
- Picasa (new photos from friends)
- Google Video / YouTube (new videos from friends)
- Blogger posts
- Orkut updates (whatever those consist of)
- Gadgets added to home page, aka “iGoogle”
- Google Shared Stuff (or whatever it’s called) added
External properties:
- Anything with an RSS feed basically… including stuff like…
- Twitter/Pownce/Jaiku, Tumblr
- Blogs not on Blogger (like: Facebook Notes, LiveJournal, VOX, Xanga, Windows Live Spaces, WordPress)
- Photos not on Picasa (aka Flickr, Webshots, Smugmug)
- Bookmarked items not on Google Shared Stuff (aka del.icio.us, ma.gnol.ia, etc.)
- Last.fm, Pandora (any other social music with RSS feeds?)
- Digg posts, votes feeds
- Upcoming (Yahoo Events)
- Apps built on social APIs (think Werewolves and Vampires), though these may come in the form of Gadgets
What I’m wondering – well there’s several things, but I think the highest on my list of wondering – is where the Activity Stream will be displayed. An answer to that may solve the second thing on my list, which is, how is Google going to decide who my friends are and which updates I want to see on the Activity Stream?
They have the new contact manager that they’re rolling out with the update to Gmail, but I have 220 Gmail contacts, and I certainly don’t want to see all their updates from all their Google (and other) activities… And I’m guessing most of them don’t want me to see all that stuff either. So… Google will have to do two things (most likely): 1) Have some way of determining who is allowed to see what (privacy level settings), and 2) create an algorithm like Facebook to decide what is most important to show.
I don’t like Facebook’s algorithm, but I feel like Google could come up with a much better one. I also think, though, that Google could create an interface (like the one on Socialstream) that would allow for a much larger number of items to be displayed and still make it fairly easy for users to understand.
I’m waiting for the November 8th (or so) announcement, but I’m pretty sure it will be a release of the API glue, which will seem underwhelming until Google (or developers) starting using the glue to stick things together.

In Fun Times, The New Web on October 9, 2007 by endub Tagged: awesome, pink shirt guy

In Bloglines, Google, Longform, The New Web on September 27, 2007 by endub
When I said yesterday a month ago that Twitter vs. Jaiku is shaping up to be another VHS vs. Betamax (yeah, I write here a lot… I promise), I was aware that the bigger battle is obviously Bloglines vs. Google Reader. Oh, I mean HD-DVD vs. BluRay. Sorry.
Anyway, now that Read/WriteWeb has a post about the war between the two biggest Web RSS Readers, I’ll throw in my 2 pennies.
Bloglines = still better.
I’ll admit, I used Reader for a while, and got used to it, and probably would have stayed with it if Bloglines hadn’t launched their new beta. For me, it’s basically the same as the old Bloglines with two extra keyboard shortcuts. That is to say, I use it in essentially the same way as I did before, but instead of going feed-by-feed using the “s” key, I now use the “f” key to go from folder-to-folder. It’s only a slight increase in efficiency over the old Bloglines, but it’s definitely better than the Shift+J -> Shift+O required for Google’s Reader.
The other big improvement (aka: new keyboard shortcut #2) for Bloglines comes with the addition of the “o” key. This is new for them, but the same as Reader’s “v” key. So, it’s not a win for Bloglines, but it does make the Beta better than the original, and helps to push the whole-of-the-parts ahead of Google.
There’s a bunch of other new features in the beta Bloglines, but after trying some out (like the 3-pane view), I chose to stick with the basic default set up (which, as I said, is pretty much the same as before). And still better.