Bug: Mine died for several hundred frames. Kept getting the same JS error. This might help you out: http://imgur.com/A82D
634 karma · joined January 8, 2009
Hi.
I'm 24 and live in NYC. I recently quit my full-time to seed my own ideas for a few months.
I started off in one direction, coasted around, then started island hopping. I've finally arrived on an island resembling paradise, nearby Mozilla's Ubiquity. I'm building the swiss army knife of browsing, and in the process, another dimension to the internet you know and love. Not quite web 3.0, more like web 2.1, I'm aiming supplement already existing web services to benefit the end user.
It will be my pleasure to launch at the end of this month.
My e-mail: sam.from.hackernews at gmail.com
Bug: Mine died for several hundred frames. Kept getting the same JS error. This might help you out: http://imgur.com/A82D
Great work
If you want go that route, invest in MSFT, which has averaged something like 50% over the past 22 years.
Edit: BTW, love your blog
Give me any 1 feature, and I can zoom into it and force you to accept other features that need to go along with it, otherwise rendering it near useless. Likewise, you can zoom out from any aspect of software and see that the "feature" really only works because it's part of a greater whole. That's where my confusion over "launching 1 feature" arises. There's really no such thing as a "feature" per se, but a some Platonic-esque form of your software that you strive to achieve.
I think it's precisely this kind of mysterious trickery behind software that makes it so hard to make specifications, test, debug, etc... and why something like 80% of all software projects go either over budget or miss their deadline.
This intangibility of software is also why I take advice about it with a grain of salt. It's easy, after the fact, to look at what you've made and point out the "one thing" that made it work.
I like unalone's concept of the "core goal" behind your project. PG and others talks about this as well. Focus on the one core thing your software does, and do that the best. This has problems also... because there's nobody to tell you that your "zoom level" of the goal is just right. What if my software's goal is to "make users happy?" I could encompass nearly anything with that. Conversely, I could set my goal to be: "to allow users to post a 140 character message", which is way too specific in and of itself to create a useful product.
I guess my point is that software, and nearly all other feats of engineering, are extremely organic. I'm skeptic about advice on the topic by "proven successes" for two reasons: hindsight is always 20/20, and selection bias. I think what it really comes down to is using your best judgment.
AndrewWarner, I'd love for you to investigate: "What do you start with?" I think it's one of the biggest blockers for would-be entrepreneurs, and puts off so many people from even starting.
I wish he'd talked more about the purpose of scaling back. I'd presume that it's to save time, and to have something working with which you can improve. If that's the case, I'd much rather heed the advice of "launch early, launch often" then "scale back." The most difficult decisions to make, for me at least, are what features to spend time on. I consider every version of what I make scaled back, because to me, it's never done.
About his argument for scaling back: "there are people in their garages building an electric car." What does this prove? It doesn't convince me that these people in garages are on a better track than Tesla. If, however, one of these people manages to build a better company than Tesla, based on their garage-built prototype, then maybe I'd take his point more to heart.
Make an API for it, and charge.
What is the point of "Reminder"? How about "share this room" instead. Reminding typically means sending me something that is time sensitive.
Second, pop-up blocker comes up. Unless you're offering something extremely compelling, I'd be so annoyed as to leave. Pop-up blocker shouldn't come up for "onclick" events... you are doing something wrong in javascript.
Third.. the more I think about it, the more I wish you had an address bar up there, and some sort of "help" thing near the chat window which would list out commands, like "!map" and "!<url>" and stuff like that.
Best of luck.
Title attributes or tooltips for all buttons. I don't know what they do.
Fade the modal in/out faster, make hitting ESC or clicking the faded are close the modal (the X is rather small)
More importantly, the whole way you manage going to URLs (and "freezing") is very unintuitive and backward. For starters, the arrow to "type in a URL ... [as far as I intially read]" points to an unfamiliar icon. I go there and see "freeze" and "unfreeze" which makes no sense to me. Freeze what? It was not clear that the main window was meant to show a URL rather than being an introduction to the service.
Furthermore, I'd never expect that typing a URL in chat would control the window on the right. It's a chat box. I type in it, and what I type goes into the chat log.
I greatly suggest the following:
Put an address bar above the window, or in the window, and next to it a "lock" or "freeze" button which says "prevents this URL from changing". Furthermore, it'll pay dividends having this bar up there when you add more options.. like maybe "new tab" and things like that.
Initially have the URL be the actual URL of your "welcome" page... (eg: http://chatterbloc.com/welcome_to_new_room.php) It will immediately tell me two things: "oh I can change the URL" and "I'm currently at the welcome page, lemme see what it has to say."
Explain features and stuff at this welcome page.. like that I can type "goto <url>" in chat to navigate . And that I can prevent navigation by freezing by locking the URL.
Make back and forward buttons.
Finally, let me name the room and give me a short URL.
All in all, a nice little service akin to Gabbly, Twiddla, etc. I like the iciness of it.
Hope this helps.
I wonder if investors in movie get the rights to the software that gets created in the process, and if they view it in and of itself a good reason to invest.
Today, Hotmail probably pulls in quite a bit of revenue from advertisements, but most of it's value was "spent" by herding the massive group of users into other products, which may or may not have made MS more money.
I think Twitter is today's version of Hotmail, in terms of the concept... except Twitter seems to have gotten much luckier.
What this ingrains into my head is: give access to known technology in easy ways. Hotmail, Blogger, Wordpress, Twitter, Facebook -- they allow people to publish/share information where previously they'd need expertise in IT to do it.
Anyway, all Yahoo had to do was make mail, then their millions of users would automatically get e-mail accounts. From there, it probably spread just the same way as Hotmail.. your-name@yahoo.com, and a little message at the bottom of each e-mail: "get your own email at yahoomail.com"
What's amazing is that it took 6 months for a competitor to come in.
My guess is the ad system they have now is just to test the waters... get the team learning the ins and outs, improving the system's algorithms and reporting capabilities, etc. Running branded ads is much more of a significant move: they're clearly ads, and not so much some sort of pseudo-relevant text ad. In other words, branded ads are much harder (as a user) to ignore, and would lead to a stifle in growth -- the absolute last thing that Facebook wants.
My point is the majority of people do not have any vision. They do and think whatever everyone around them does, which comes from TV or their parents. If anything you pitch to them requires an explanation, you've already lost.
ALT attributes provide descriptive text and are replacements for missing images. Great! Now, why are they required? Not to mention, any use of any attribute not on the list will get you unvalidated. Suppose I want to include some extra data for JS, like "_droptype" or "_isDraggable". Sorry! It's not on W3C's list of acceptable attributes so you fail validation, even though all browsers ignore attributes they don't know about.
An empty tag... why do I have one? Well, maybe because inside the tag I have server generate text.. .and instead of doing;
if ($text) echo "<tr>$text</tr>"
I do echo "<tr>$text</tr>"
Would it be so hard to make the standard: "If theres nothing in the tag, treat it like it doesn't exist"? No.Furthermore, I have blank DIVs to take up width/height sometimes. Then again, I'm sure there's some clever way to wrap 20 DIVs and put browser specific hacks so it actually validates... but I prefer to do it the way that works.
Major browsers are nice enough to allow me to not care. So show me errors that I need to care about. W3C validation, to me, is like saying "I memorized every little gotcha that W3C implemented... and still, everything works! Aren't you impressed? Five years from now, the site should still work! Forward validation! Yay!"
For some reason, magnolia always resonated with me as: "Hey! Look at me! I'm sooooo easy to use! And I look sooooo good! Hey! (bats eyelashes) I'm pretty, right? Your life should revolve around bookmarking! Just go to mag.nol.ia .. no, wait, mag.nolia.com ? No, it's ma.gnol.ia. Ah, here it is: ma.gnolia.com. Anyway, bookmark it!"
You're right, the event namespacing was exactly what I was looking for.
BTW, is there a list of "reserved" words in jQuery? For example, jQuery has to store this information somewhere... possibly it gets attached to the DOM element itself. Where does ".data()" live? I often directly access the DOM elements, and want to be sure I don't interfere with jQuery.
To get around this, I use my own event normalization that seems to work across all browsers and only normalizes what I need in any given project, for example:
var e = e || window.event;
var fixed_e = {};
fixed_e.pageX = document.all ? e.clientX + truebody.scrollLeft : e.pageX;
fixed_e.pageY = document.all ? e.clientY + truebody.scrollTop : e.pageY;
fixed_e.X = (e.offsetX ? e.offsetX : e.layerX) || 0;
fixed_e.Y = (e.offsetY ? e.offsetY : e.layerY) || 0;
fixed_e.source = e.target ? e.target : e.srcElement;
Another problem with jQuery events is unbinding is tricky.. I don't like how I have to have a reference to the bound function laying around somewhere so that I can unbind it. In my event system, adding an event returns a handle, which allows you to simple call ".detach()" or ".attach()" or ".trigger()" .. it's worked out very well for me.As per the remove, I added a simple extension that's worked perfectly:
$.fn.rm = function(){
return this.each(
function(){
if (!this.parentNode) return; //already removed.
this.parentNode.removeChild(this);
}
);
}There are some things jQuery isn't too great at (event normalization is slow in IE, for example, and .remove() kills events and data), but I've never not been able to easily extend jQuery to use my own implementation.
Thanks again for jQuery.
Just look at the worthless output for news.ycombinator.com: http://validator.w3.org/check?uri=http%3A%2F%2Fnews.ycombina...
137 warnings, 5 errors. Let's take a look at what expert advise the validator offers, so that our webpages will be forward compatible (or whatever the supposed purpose of this is for).
It complains about every href that has "=" or "&" in it, claims you must put an ALT attribute on images, says <tr></tr> is invalid... etc. It essentially complains about things that have no effect on anything, but for some reason or another the W3C decided to put into their standards and enforce it.
W3C: how about you come up with something useful... like, for instance, allowing me to center a fucking DIV with CSS. With tables, I can simply... just kidding. But seriously, I have qualms with W3C.