Going to https://www.securesuite.net/ gives you a nice blank page. And here’s the whois information:

Registrant:
      cyota
      yaron shohat
      174 Middlesex Turnpike
      Bedford, MA 01730
      US
      Phone: +1.8665606153
      Email: 

   Registrar Name....: Register.com
   Registrar Whois...: whois.register.com
   Registrar Homepage: www.register.com

   Domain Name: securesuite.net
      Created on..............: 2002-08-23
      Expires on..............: 2012-08-23

   Administrative Contact:
      RSA
      Network Operations
      174 Middlesex Turnpike
      Bedford, MA 01730
      US
      Phone: +1.8665606153
      Email: 

   Technical  Contact:
      RSA
      Network Operations
      174 Middlesex Turnpike
      Bedford, MA 01730
      US
      Phone: +1.8665606153
      Email: 

   DNS Servers:
      pdns3.ultradns.org
      pdns4.ultradns.org
      pdns2.ultradns.net
      pdns1.ultradns.net
      pdns5.ultradns.info
      pdns6.ultradns.co.uk

Who’s cyota? Who’s yaron shohat? And what fucking moron at RSA thought this was a good idea? Here’s the Google results for securesuite.net phishing. Doing a search for Securesuite.net does not return Visa or Mastercard’s official sites…

Well, it turns out securesuite.net isn’t a phishing scam, after doing some Internet searching, digging up direct links from Mastercard.com, and calling MasterCard directly to get verbal confirmation and to give them a piece of my mind. It’s not a scam, it’s just moronic and a phishing scam waiting to happen.

• Alexander – In The Twilight
• The Horde and The Harem – Darlin’
• The Head and the Heart – Down in the Valley
• Unknown Mortal Orchestra – Ffunny Ffrends
• Anamanaguchi – Another Winter

I was meaning to post something up sooner, but alas, crazy work deadlines and SxSARS have conspired against me this week. Miraculously, I managed to stave off sickness for all 10 days in Austin, but I ended up picking something up (I think) on my plane flight home (I’m looking at you coughy mccougherson in the next seat over). In any case, some less than organized thoughts while they’re somewhat fresh.

First, on SXSWi (Interactive), I think Gruber nailed it pretty spot on:

Used to be that SXSW[i] was an interesting conference and a great weekend experience. Now it’s a terrible conference and a good-but-crowded weekend experience.

As someone that actually lays down my own cash for SXSW, I was pretty offended by how horrible the conference setup was this year. I think Matt might have had more success with my Lanyrd than I did. This was by far my worst panel year ever (this was SXSWi #12 for me, and the past few years were fine, thank you very much), not because of the panel quality, which has continued to improve, but because the logistics have gotten precipitously worse. The panel/room scheduling was a mess (with some of the most popular sessions in the smallest rooms), and the half-assed shuttles (unmarked, not on any schedule, never there before or after sessions, taking you on a loop around town; some unlucky people apparently got shaken down by similar unmarked pay shuttles) and across-town campuses was an unmitigated disaster (the word clusterfuck is the term that comes to mind). I met some friends who had much better experiences – they did the sensible thing and just didn’t bother attending anything not in ACC/Hilton. Lesson learned.

Anyway, if I went to SXSW for the panels still, I’d be kicking and screaming for a refund. I’ll let others argue about the ethics of taking money from attendees that the conference clearly doesn’t have the capacity to support. My simple suggestions for fixing things (as there were sessions I would have love to have caught):

• If you’re going to be selling Interactive Badges, where people are paying for panels, they need to be within the ACC block. Move Film panels if you need to, find some creative locations nearby (lots of boarded up stuff), or (god forbid) stop fucking selling badges if you’re over capacity, but having to choose between a 1hr roundtrip or a $12 cab ride to see a panel at the Hyatt is pretty much the definition of bullshit. (even worse were those that made a hike to find the panel they were going to was full or canceled)
• Millions of dollars in badge receipts and you’re telling me you can’t UStream all the sessions and make them available in simulcast and archive form for attendees? This seems like a completely reasonable and rather simple solution. If a speaker doesn’t agree, fine, mark it on the schedule (or tell them tough noogies), but this seems like a no-brainer for most of these.
• Stop being fucking babies and open up your schedule API to Lanyrd, SCHED, etc. These tools are way better than anything your team has done, and if there was less time wasted writing their own scrapers to your (not well formed) data, they would be more accurate and could coordinate better – especially for tracking attendance, demand, etc. This year, SCHED provided Foursquare with its SXSW event data. Why? Because there was an API and they had their shit together.
• In an interesting regression, conference staff seems less willing to swap rooms, even when there’s an obvious mismatch (and an obvious swap candidate right next door) a half hour before the session…

OK, that’s all the indignation I can really muster up. Etsy threw a better conf down the block. That’s pretty sad yo.

Anyway, I’ve never been a fan of the “SXSW is too big” meme… but, I found that this year, much more than the past couple years even, that I had some issues for the first couple days getting into the SXSWi groove. Primarily, SXSWi is a time for me to meet up with “200 of my closest friends” – the people of my tribe that I might only see once every year or two. In the past, it was much easier to depend on serendipity (and over the past couple years, some dependable end-of-night hangouts), but I found this to be a bit harder this year. Part of it I think had to do with the aforementioned shitshow with panels – I didn’t realize how much of my dinner plans depended on the group of 5 people that I’d run into after the last panel session (of course, this was also my first year over a decade without a Break Bread w/for Brad to kick things off…).

All that being said, I ended up having a pretty good time, especially once I realized I’d have to work a bit harder at social planning, and rallied.

• The Old Timers Ball was a great idea. During SXSWi, I have two rules of thumb that have served me well: 1) no waiting in line and 2) I don’t mind paying for my own drinks. (Especially during Interactive, many people seem to break #1 for #2).
• I don’t believe I had a sit-down meal until my 3rd day in Austin. I did however have the pleasure of sharing and introducing fried oreos to more than a few friends. The East Side Drive-In was one of the best surprises this year. If you didn’t make it out there, you have something for your TODO list now.
• Speaking of pleasant surprises, two words: CNN Grill. So good that I’m not even going to make the obvious snarky observations in relation to the quality of their reporting.
• The following hashtags (on 4SQ! barely used Twitter @ SXSW) were useful: #noshitshow, #noline, #oldtimers
• I mentioned this in a tweet, but despite the hype (and my own personal expectations) that GroupMe or Beluga would be useful, it turned out that 4SQ was much more useful for coordination. I ended up in 5 SXSW GroupMe groups, but it turns out that while GroupMe might be well-suited for small groups of strong-ties, it’s absolutely useless as a serendipity enabler. 4SQ wasn’t perfect, but it was pretty good (more in-depth thoughts below).
• Cell networks stood up much better this time around, both during Interactive and Music it seemed like. I was using Sprint, which dropped down to 1x much too often, but also had 3-4Mbps 4G available (at the cost of destroying battery life).
• Interestingly, because of the huge new venues that had opened up (the Power Plant, the new ACL, the Pepsi Max Warehouse), I ended up swinging into some mega-parties during interactive that were relatively uncrowded. The night we agglomerated a gaggle of Brits into a big nerd pack, we rolled into the RedLaser Chromeo sans-line (there were maybe 500 people at a probably 2000 capacity venue?). Rolling in at the end of the 4SQ Big Boi concert, and into the Microsoft Yeasayer party were similarly pleasant experiences. Maybe all those hundreds-thousands of people standing in line at Mohawks and Stubbs is a good thing? It seems like there was definitely a big gap in terms of good real-time crowd reporting…

Which is as good a segue as any to talk about 4SQ. First of all: holy crap are these guys hitting it out of the park. Between the great 3.0 features and the crazy biz dev (AMEX, etc), it’s just great seeing 4SQ really starting to fulfill some of that LBS potential. (it’s only been a decade or so in the making, right?) Comments in particular, super useful this year. It’s with that in mind (and the fact that I actually lived up to my Super User status this year) that some constructive criticism is offered:

• Two 4SQ apps, 4squareand7yearsago and flicksquare were especially nice, especially since then former had an “early adopter” edition during SXSWi that sent you a history of your checkins from 2 years ago. A nice reminder of how your checkins could be personally valuable
• While I had mentioned that 4SQ was more useful than the group chats for coordination, it was still not ideal. A few thoughts in that regard:
  • While the checkin is useful, two verbs that I was most missing were “heading to” and “leaving.” Being able to signal intent would be killer, especially if you were trying to catch up with someone or vice versa. This could be a picoformat in shouts (like “>” or “/l” with @names), but would be nice if it were parsed in the system
  • Along those lines, it seems like something like Ditto where you could propose a meetup/location would be super useful as a 4SQ feature rather than a separate app, especially if it integrated with some realtime status
  • I didn’t end up rolling this out due to some complications, but one of the things that I worked on for the SCHED map was a way of reporting realtime status (lines, crowds, lateness) to a venue. There’s no reason this couldn’t be implemented in 4SQ
  • The map view was pretty useless with a lot of friends checked in. More interesting views would be heatmaps that showed say a time+density based visualization (venue trends) as well as say, relative crowdedness to people you knew. The ideal venue at SXSW is actually the least crowded venue with the highest percentage of people you know checked in!
• That being said, while 4SQ was OK during Interactive, for whatever reason, it worked way better during Music. Ended up catching a bunch of bands and having a bunch people roll in to meet up based on checkins/shouts. Also super great way to ask friends what the line/crowd/lateness status was.
• A heavy concentration of 4SQ users meant that you rarely had to search to find your checkin location. Which is good, because SRPs continued to be astoundingly bad. Searching for the Hilton or ACC or Convention Center would rarely turn it up in the first several screens (which would seem impossible if even the most basic popularity/activity ranking was being used). Also, this may be Android specific, or maybe based on service timeouts, but my Favorites rarely showed up at the top. Lastly, as a SU I saw things that I constantly would want to merge, but just couldn’t (unless I’m missing something in the Mobile UI)
• Related to “riding” on checkins, I hope (but doubt) that 4SQ are tracking this? I (and I suspect most people) tend to pick friends checked in when hopping on their checkin locations – there’s some crazy future data-mining+awesomeness generation potential there (even beyond the current co-presence data being used).
• There’s no way to unsubscribe or block a user from the app! Or the mobile site?! Or, watching kathrynyu unsuccessfully try, even via iPad. WTF?! That’s bad!
• Sadly, iOS Notifications has actually caused a big regression with 4SQ this – while I didn’t notice it on my Android phone because notifications queue into the notification bar, using my iPad even for a few minutes made me realize how it sucked big time for iOS users. Basically, like the bad old days w/ Dodgeball SMS’s (the social app that punished you as your friends used it more as I liked to put it), except iOS Notifications are even worse, popping up in a constant stream in the middle of your screen. The only solution I can think of really of (besides waiting for iOS 5?) is for there to be an easier way to turn Pings Off for users or to institute internal digesting/summarizing/rate limiting against iOS notifications.
• Annoying niggle only notice through mega-usage: when you successfully checkin on Android, it doesn’t update your location in your listing. This is especially annoying when you’re on a slow network since it has to poll to update. In general, having a “last updated” status would be useful. Overall 4SQ still has a ways to go to be more useful when you’re offline, even updating the time rendering at least would be a good first step.

SXSW has been “on notice” for me for the past few years (I had originally decided that 10 years running was really longer than I needed to do anything, but it’s just been too fun to stop), but this year, at the end of SXSWi, when I realized I still had 5 more days, I was pretty sure it’d be time to take a break (surely I have better things to do with $4K and 10 days). However, Music was actually a total 180: completely re-energizing in all the ways that Interactive was enervating. I had a great time.

Instead of taking video, I ended up using a combination of 4SQ and a new app called Whoa to track the bands I caught (66 rated, yeah!). This year, SCHED tracked just under 7300 events (almost 50% of the parties and music events were unofficial), with over 4500 users (tracking on average over 60 events each)… As I side-note, while I know SXSW has a sometimes rocky relationship with “unofficial” events, and heck, even with SCHED, but, it’s a big part of the reason they’ll be getting my Platinum badge money if I’m back next year, not to mention why its worthwhile for most of the bands that come. It’s the fact that bands will play multiple shows (building buzz and letting fans catch them in an otherwise impossibly packed schedule) that really distinguishes SXSW from everything else.

Interactive peeps, if I catch you in Austin next year, sadly, it’ll probably be in-spite of SXSW rather than because of it.

That being said, I don’t think Charlie goes quite far enough. The essay starts framed by the thesis that in the world, things haven’t much improved, and the besides a few specific counterpoints about disease and the general march of technology, it feels like he gives up on really repudiating that thesis… for the developed world. And it’s easy to see why. In terms of general socio-economic trends, it’s hard to be all that positive. Things are downright unsettling heading towards dystopian. However, there’s at least one aspect, the very medium where we are commenting on that is worth, uh, commenting on.

Yes, the interwebbytubes, as Stross puts it, is quite a different place than it was at the beginning of the millennium. We are looking at a 2X adoption growth in developed nations (from plurality to supermajority, if not ubiquity). Worldwide, 2 billion people are now online. Beyond the quantitative changes, the qualitative changes are even more intriguing. In 2000 there was no Web 2.0. Blogging was in its infancy. Most of the things we take for granted online today were not invented yet. Among them: Wikipedia (2001), Facebook (2004), Google Maps (2005), Twitter (2006). I list these in particular because I don’t think there’s a day that goes by where I don’t use these particular services, but I’m sure that others have their own lists. Lest you think that this was a singular period of growth, I’ll throw in that the iPhone (2007) and iPad (2010) have kicked us into another era of hyper-growth that will be just as (if not more) life-changing.

We’re just starting to see what happens when the Internet starts engaging with us in a location/context aware fashion. We’re also starting to see what happens when Internet-style/scale dynamics are applied outside traditional consumer Internet contexts (e.g. Obama Campaign, 2008). In a historical scale, we’re still at the very beginning stages of figuring out what it means to live in a digital, massively inter-networked world, and similarly just starting to get a handle how that will change society (attention, communications and collaboration in particular).

All that’s a really long way of saying… well, there’s a pretty dang bright spot in the developed world too. One that has the potential of being turned into the shovel we need to dig ourselves out. So, here’s looking to the future. Happy New Year.

In any case, after I get some stuff done before Christmas, I’ll probably be spending some of the last days of the decade thinking doing some reflection (also, while I first started migrating .plan updates to the web in ’97, and the direct predecessor to my current blog in ’99, my 10-year blogging on rf.net is actually coming up in a few months…

(Amazingly, it wasn’t until earlier this year when my old USC links (and email account!) finally got broken. 10 years ain’t a bad run.)

Yesterday, Cyanogen, an Android community developer who maintains the most popular (and arguably best) alternate Android firmware, CyanogenMod, mentioned receiving a cease and desist from Google Legal.
Alternate firmwares (or custom ROMs) are along the lines of the custom WinMo firmwares that enthusiasts have been putting together for years (and in fact, there is at least some community crossover, including some shared forums). I only recently discovered CyanogenMod after complaining to the one Android superfan I know about how slow the Android phone I had was, and it was to me a night and day improvement over the stock firmware – performance went from unusably laggy to downright zippy.

Now, while Google is obviously within their legal rights (the C&D was specifically about redistribution of their closed source components), honestly, I’m rather baffled by this. It just doesn’t make any sense from a practical perspective – these apps are distributed with all the phones that the Cyanogen firmwares can be installed on, and are mostly used by a small set of the platform’s most dedicated enthusiasts (low tens of thousands at most, less than 1% of the Android userbase) – and of course, by a select few hobbyist developers putting in an inordinate amount of time in maintaining the firmwares and supporting those users. Not only is there no upside in attacking this community, but I can’t picture any scenario where there would be a net-positive outcome for Google.

As you can imagine, once word spread about the C&D, a community reaction was inevitable. A petition app was quickly put on the Marketplace (not the worst idea, honestly), and there were a few mentions in the more general tech news, although I haven’t noticed a big splash (say on Techmeme)… yet. That may change soon, I believe, as the fallout is now much bigger than inconveniencing a few “modders.”

Earlier today, Dan Morrill posted an official position statement on the issue. His statement about redistribution of closed source components seemed straightforward enough, but the implications are still unfolding. It turns out that by explicitly outlining the legal boundaries for closed-source components, we learned that not only core parts of the Android experience (like the Google Mobile services and Marketplace app), but also parts of the SDK and other base components are also protected. This news doesn’t just kill custom ROMs, but potentially makes Android as an open source project not viable at all. From Cyanogen’s Twitter stream:

@crazywizdom it’s pretty much like a bare bones linux install without the google bits. no contact sync or anything like that. #

From what they explained to me, you are not even allowed to copy the proprietary applications from your device. #

@gacktoh but you can’t distribute the market app. And it relies on the Google Mobile services anyway. #

I’m trying to get clarification now on what can actually be included. There are things in the SDK that aren’t in AOSP. Very confusing. #

Oh yeah, one last tweet before I violate the don’t-tweet-while-drunk rule. Nandroid is probably illegal. Awesome huh. #

All this woe (that’s counterproductive towards Google’s interest even if weren’t a PR, and now full on developer community nightmare – the custom firmware releases brought steady streams of improvements to tide over the true believers to what has been thus far, a somewhat lacking software product), probably set in motion because some PM got wind of the v1.6 Marketplace app being on the phone and got in a snit, setting the legal wheels in motion. And poof, over the course of a day, a cascade of events leading… who knows where.

Which is not to say that this can’t be fixed. The Google folks (even the legal teams) are smarter and more agile than most – if this is a priority, there are many ways to patch things up, from offering some sort of non-commercial redistribution terms, or having the Android team announce that they’re working with the community to make sure that they’re making it a priority to make sure that custom firmwares can be installed w/o touching the proprietary APKs, or that the AOSP is useful as an end-user installation (both of which jbqueru at least appears to already be moving on).

As it is though, it appears that Google has just shat on it’s biggest enthusiasts, and has given a good cause for those who are supporting Android as an “open” alternative to actively consider how far that openness extends (and realize how ostensibly “open source” Android really is). And of course, it’s a shame that there won’t be any more CyanogenMod builds. Still, this has been pretty fascinating to watch unfold, and should be of interest to anyone managing developer communities or trying to create an “open” platform…

(If you’re interested in following the conversations moving forward directly, the Twitter streams of cyanogen and Android developer jbqueru seem worth following.)

UPDATE: To some degree, this will probably blow over, since over the weekend Cyanogen announced he will continue w/ his work (after developing a new backup procedure to allow backup and re-installation of Google apps and with the inclusion of an alternate marketplace). Still, these are the types of incidents that chip away at social capital and reputation (until suddenly one day, the public no longer gives you the benefit of the doubt and any action taken gets looked upon in the worst possible light) – not to mention the amount of ultimately, pointless (or at least, repeated) man-hours that will be spent engineering a technical workaround to a policy problem.

Actually, this article was actually the one that actually convinced me to write something, specifically this quote:

I used to think Twitter would never catch on in the mainstream because it’s somewhat stupid. Now I realize I was exactly wrong. Twitter will catch on in the mainstream because it’s somewhat stupid. It’s blogging dumbed down for the masses, and if there’s one surefire way to build something popular, it’s to take something else that is already popular and simplify.

To clarify, I think this is fundamentally wrong and completely misses the point. (As an aside, similar things were said about blogging when it started taking off. These comments were also fundamentally wrong in the same way.)

Now, for some context, even though I was a relatively early adopter (my first tweet – I believe it was still called twttr then with a snot-themed logo and a focus on SMS), that’s not to say my own understanding and thinking hasn’t evolved along with the service (and its audience)…

The first time Twitter really picked up on my radar was while I was in London, as it had gotten a fair amount of traction as a cheaper way to text. Along those lines, it took off, again as a “group chat” style tool the next year at SXSW as a way for friends to coordinate in a lighter-weight and less annoying way than Dodgeball. At this time, it was still focused around SMS delivery, although there were some interesting clients starting to pop up. Also around this time (post-SXSW) that my (and others’) focus turned upon looking at Twitter through the lens of ambient awareness (Clive Thomspon did a great writeup writeup last year) and what we began to refer to in conversation as “statuscasting” (a term, which I might have made up, but I assume must have been on the tip of everyone’s tongue). Then there was a big explosion in clients, mashups, and the use of Twitter as a “command line” interface. And, of course, through all of this, Twitter continued to build up steam in the way that social tools do, as waves of adopters and their networks jumped on board. While there has always been the dialectic between semi-private conversation and broadcast/publishing that continues to make Twitter really interesting, the trend arguably has been toward the latter (especially with the “collection” of followers).

Now with some context that hopefully hints at some level of complexity to the Twitter phenomena, here’s where I return to directly smacking down that original quote and offering an alternative interpretation…

Twitter isn’t “retarded blogging” anymore than blogging was “retarded long-form writing.” What blogging uncovered was a “web-native” sort of communication – one focused on links-both hyperlinks and permalinks, temporality (dated posts, reverse chronological order) and decentralized conversation – at first manually since people simply read each other’s blogs (when I started, it all fit on a single list), then later with comments and formalized through trackbacks, pingbacks, and dedicated aggregation tools. It took a while, but I believe that Twitter has revealed a communication style that is native to the “web” today. What is this web? It’s one filled with activity streams – the “social web” and the “continuous partial web,” and one that exists beyond the browser and beyond the desktop – the mobile web and the “widget web.” The ingestion characteristics of these media are focused around intermittent (but constant) bursts of attention and the ability to scan both gestalt and to track details, and the output is about the “in-between times” of other activities. You don’t sit around for an hour writing a tweet. In fact, most people start with time that otherwise would have been spent idling (hence the large proportion of airport complaint messages).

That, I suppose is one aspect of the quote that is right – Twitter is does have more mass appeal because it can take root by fill a vacuum rather than being an activity that requires active displacement (at least to begin with!). The point is that it’s high immediate reward with low incremental commitment. And of course, the innocuousness of that small text box is part of Twitter’s genius…

Now, if there is a better (or different) model, my suspicion is that it’s in finer scoping. Sure geeks like to talk about interop and decentralization (and while that may come as it did for email, it may not (like for IM)), but I think it’s ultimately less interesting than figuring out how Twitter (or a similar type of service/activity) ends up bifurcating or integrating the aforementioned pull between public and private (groups? targeted/typed messages? ).

I think that’s where already see some interesting things like how location services have splintered off, and I think that’s what Facebook is attacking – in the same way that it created a semi-private place for photo and online-discussion activity, it’s trying to do so for tweets as well.

For those that recall, this harks back to discussions on semipermiability (ironically semipermanant, here’s the archive of Joyce’s paper on that), which never really took off (again, a niche that Facebook expanded into, I think).

Well, there’s not much of a conclusion here. This is entitled random thoughts after all. Maybe two last things while I’m here for those who remember the milieu and impetus of blogging… Firstly, my friendfeed, which is currently aggregating my activity streams across over a dozen services, and second, a graph of my blog output over the past few years:

See also:

• Today, Jason Kottke wrote a great piece entitled In Defense of Twitter
• As a counterpoint, back in 2007, Kathy Sierra asked Is Twitter Too Good?

To preface, like Matt, my background is also primarily as a web developer, although not exclusively – I’ve written my share of Lingo, Java Applets, OpenGL, Shake scripting, Max/MSP and Processing and other stuff. These days I hang my “expertise” hat on web architecture and systems, but I’ve done a fair amount of just about everything on the web side of things including some lower level things like working on Apache modules.

This isn’t to brag (you’ll note no accomplishments of merit mentioned above , but simply to give some context of where I’m coming from. Learning Cocoa has been interesting. Of course, first and foremost, there’s the unique feeling of being a newbie again – that awful confusion, but also the excitement and then that somewhat retroactively forgetful feeling of incomprehension at not understanding how something works…

This learning phase may have maybe been more painful that it could or should have been. “Learning Cocoa” encompasses, not just a language (Objective-C) tied intimately to multiple very large sets of libraries (collectively Cocoa, but also CoreFoundation, AppKit, and in my case Quartz, Core Image and CoreAnimation as well as an inscrutable third party API), but also XCode and Interface Builder, each with a myriad number of settings, plists, etc.

While I think that a further discussion of the total lack of context and the bits and pieces of documentation/tutorials that did help me get my bearings may be the topic of another post, I did want to mention that the Apple Developer Documentation did not help me as I would have hoped in terms of orientating myself.

Some more observations:

• It’s sort amazing how much more work seems to go into accomplishing very little, and how your ambitions scale along with that. I’ve spent more time working on looping some animations and making sure it doesn’t leak memory for example than say the Event SRP, or heck, the entire offline-task system on MyBO. Maybe it’s just my experience so far (biased say with spending a solid week fighting a certain third party SDK while learning the fundamentals), but I can see now why desktop apps haven’t seem to evolved as quickly as web services have. There’s just a lot of slog involved.
• Note: PyObjc doesn’t make things easier – it’s just … hideous
• Although… it would avoid Objective-C 2.0′s ridiculous memory handling – there’s garbage collection on the RunLoop, but only in some cases (for explicitly init’d, alloc’d and retain’d objects) but the AutoRelease doesn’t happen in threads, which by the way NSTimer launches, so make some subpools, but be sure not to over-CFRelease lest you cause an ecxeption (and crash) down the line, but good luck w/ MallocDebug if you missed anything and need to track it down… Don’t I have better things to do with my brain cells?
• Casting through contexts is just out of control. NSImage, CGImage, and CIImage? Really?
• Get used to writing at least 10 LoC to do what seemingly should be a single easy action (or declaring something in at least two if not more files and sections). Coming from scripting languages, the amount of boiler plate is mind boggling
• Also, as someone used to CPAN, PEAR, and PyPI, it’s also been interesting discovering how spoiled by the ease of third party libraries and how much less common and more effort it takes. Maybe I just haven’t gotten quite that far yet…

In any case, it was the last event that I want to write about a bit since it was a bit of a serendipitous discovery, and is a good example at some of the gaps that still exist with event tools.

A couple days ago, I saw a pretty neat video featuring a new Electro Harmonix effects box. This demo was definitely a cut above the average music gear demo (this one is even better). Browsing around today, it turned out that Mark blogged about this video yesterday on Boing Boing, and that an EHX employee ended up posting some more info about the performers, including a link to their YouTube accounts. Their current video is entitled Show on Wednesday! and 10 seconds in, it turns out that it’s in San Francisco (the YouTube profile doesn’t have anything about the location). A quick check on the posting date (yesterday) confirmed that the show is in fact happening tonight.

The reason for this lengthy description of how I discovered this event is because it’s really quite a long (and fragile) chain of serendipitous events (particularly in clicking into the comment thread (which definitely wouldn’t have happened if I had caught this post later in my feed instead of randomly browsing on the site), and then choosing the right YouTube account (of three linked), and then clicking play on their new video to discover that they were local).

Now, of course, as any band of any sort would, they have a MySpace page. Which has a big graphic highlighting their show – and they have their show entered (and a MySpace blog post), so if someone happened directly on there, I guess they could find out about it.

At this point, I had enough information to enter it onto the old red and yellow, where I could continue to add to my copious notes on entry improvements (perhaps the topic of some future post).

Now, of course, since I’m an events geek, I decided to continue along this trail and the next stop was to the Red Devil Lounge’s site and more specifically, their calendar. It, like most other venue sites, is about par for the course, appearing to be hand generated in Dreamweaver. Interestingly, it does have an RSS feed, generated by a commercial desktop app no less (FeedForAll). The interesting (and somewhat amazing) thing about venue sites is that across the board, they haven’t really changed much in the past decade…

Now one interesting thing about the event is that I got the official title wrong (I didn’t change it on the Upcoming event – one of the things we (and no-one else) ever tackled was multiple representations/ownership of the same event). But, rather than go off on tangents about the minutiae of event modeling (there are a bunch of more interesting coinciding process issues with editing even of canonical entries as well), I did want to point out something that caught my eye.

Pirate Cat Radio‘s official link for the “Baghdad By The Bay Showcase” is actually an Upcoming RSS syndication link of the guy who runs the Baghdad By The Bay show, RICK!. Now, it’s pretty cool that Rick has a somewhat active account that has his radio show schedule (sorry recurring events never got better), but surprisingly, the actual physical show wasn’t listed (score one for Upcoming’s entry-dupe checking).

Now, since I don’t do this for a living anymore (and haven’t for a while now, so I’m out of the loop), so this isn’t really any sort of rigorous analysis, and there are some guys attacking the music side of things much more vigorously (for example, it looks like Rick added the concert to Sonic Living last month, and there’s a heckuva lot of Tour/Ticket related activity), so that area, while still incomplete is actually getting a lot more attention than others.

But I guess one of the things that struck me was how there’s lots of information out there, but it’s not particularly well connected. There are some pretty huge gaping holes and the “serendipity” feels more haphazard than gratifying, and well, it’s all just a lot of work.

Hmm, I’ll just end here. I think I started off wanting to talk more about interactions of calendaring/semi-private/public event planning/interactions and proactive discovery, but this is getting a bit long for a ramble, so maybe next time when the spirit moves me (i.e. when I’m avoiding real work).