RasterWeb!
Submitted for your approval… My design concept for the BarCampMilwaukee5 t-shirt. The title is “EXPLORE!” and it’s got an astronaut driving a land rover on the Earth’s Moon.
This is just my design, and technically, you still have until Monday, September 13, 2010 to submit one. After that, It’s all up to whil. (And his team of t-shirt art-choosers.)
Here’s a Chrome annoyance… I don’t like that the ‘View Source’ command is under a menu titled ‘Developer.’
It’s bad enough that it’s a submenu and not readily apparent at a top level, but to stick it under ‘Developer’ seems almost as bad as putting it under a menu titled ‘WARNING!’
I’m sure the people behind Chrome believe they are making things simpler for users, right? I mean, such things should be hidden from the “normal” people, as they wouldn’t understand it.
But the thing is… when I learned to write HTML, the number one tool to aid in learning was the ‘View Source’ command. I know this was 15 years ago, but I’m not convinced a better method has come along yet. (If it has, let me know.) I’ve always liked that the ‘View Source’ menu was up front, easily available, calling out to anyone curious as to how a web page worked. Just a click away…
I always feared that a browser would come out that didn’t include a ‘View Source’ option, but I’m pretty sure even Internet Explorer has one.
Oh, and another thing (consider this #138) why do they hide the protocol? I actually like to know if it’s http or https and have the ability to easily toggle between the two. I guess I’m just a developer and these things scare and confuse normal people though…
(And yes, I know the screenshot is Chromium and not Google Chrome but the UI is the same in both.)
Here is the audio from the first hour of Web414 for September 2010 (aka The Mystery Show!) Our guest was Michael Massie, creator of the iPhone app Smart Alarm and the guy behind StdyHll and a few other things of interest. We also have most (but not all) of the group intros and at the end I ramble on about evil.
You can also download an MP3 file if you’d like. (And for our freedom loving friends, enjoy an Ogg file.)
Also, if you want to get all of the audio automagically downloaded podcasting style, subscribe to the feed.
(consider it cc:by)
This dude is really creepy. Also, he needs a haircut. He may be scared to get one, fearful that it might cause damage to his brain or something. I mean, it is glowing as if he’s hatching some evil scheme. Creepy and evil. Besides all that, he actually seems pretty happy. In a creepy way.
In the post Planning for the future my point was to tell you that the future is unwritten. It hasn’t happened yet, which means you can still have an effect on it.
In Keep Making Social Networks, Facebook Hasn’t Won, Ben Metcalfe gets into it, reminds us of the past, and tells us that the future is open. It’s encouraging because there are times when I think Facebook has all the cards. Right now they’ve got a lot of users, a lot of data, a lot of mindshare, and we’re at a point where the usage of the Internet by “common folk” is exploding, or has been exploding for quite some time, and many of these new people join Facebook and think “this is what the Internet is all about!” and they’re wrong. So wrong…
I do use Facebook, just like I’ve used many tools in the past, to the limits of their usefulness. But I also don’t just settle. I like to think that things will get better the next time around. I still believe in a free and open web, and I’m not satisfied with how Facebook fits into that future.
So when I say “Facebook can Die Like the Rest” I’m not talking to Facebook, telling them what to do… I’m talking to you, telling you that it’s a possibility. Maybe if we work together we can make it a reality, and replace it with something better.
Keep on disrupting!