For the best experience on desktop, install the Chrome extension to track your reading on news.ycombinator.com
Hacker Newsnew | past | comments | ask | show | jobs | submit | history | more michokest's commentsregister

Or http://talkerapp.com, which is free and maintained by the (subscription driven) Teambox


The side effect of this is that, overall, your "organic" traffic might seem to perform worse vs your Adwords campaigns, since people looking for images are usually lower quality visitors.

I wonder if this is just a coincidence.


@michokest yes, that happens too. For me the biggest issue was thinking that we were doing great at some keywords with SEO and it turned out it was just Google Images. Certainly, people coming through Google Images doesn't convert at all.

After my "hack" at least we know :)


Right, the market is full of point solutions that keep focusing in only one aspect of the communication problem. Sort of like UNIX command line tools: great at doing one thing, but loosely coupled with other apps you use.

Yammer is great at microblogging, falls short for the rest. Email is great for 1 to 1 messages. Campfire does chat really well. Asana or Trello do tasks. But your data still lives in a dozen places.

I started a company around the very problem you mention, trying to bring together all the tools I used, and we're now close to 250k business users. And, despite the big guns like Yammer, we're seeing our revenue double every 4 months. Take a look if you're curious, it's called Teambox (http://teambox.com) and it brings together tasks, GDocs, chat, wiki-like notes, etc.


Disclaimer, I work at Yammer.

I'm not going to plug our product's features here, but I'll say this: microblogging is not an accurate portrayal of what it is anymore, and hasn't been for at least one and a half years.


Care to elaborate on what it is? At work we looked at Yammer, some people use it and others don't. However, my impression awhile back was "great another facebook but for work". (I mean no offense to it, I am honestly interested in how you view yammer.)


Minor typo:

> "[object Object]" with {}+[]

I believe it should be []+{}


For completeness, here's a link to the first part of the post: http://pau.calepin.co/backbone-dealing-with-stateful-applica...


What a great find! My solution is much more limited but also very lightweight: only textareas, only two scenarios (click or load on demand)


No problem, it's often hard to find the thing you want, so you just build it. Thanks for sharing and helping others!

However, I would say, that for 4kb (minified), sisyphus offers a lot of functionality - and is supposedly cross-browser compatible. If you want to limit it to textareas only, it's not much of a modification.

Anyway, just thought I'd point out an alternative, and thanks again for sharing your work!


I didn't need it for anything else. Feel free to send a pull request if you find it useful for more things.


I probably wont do that, but maybe updating the selector would allow for more form elements to be used (if somebody wanted to use it for more than just textareas)

    textarea[data-save-id]

    to 

    form *[data-save-id]
I dont even know if that is a valid sizzle selector though


I made this for my own project (which uses all those), but you have a point.

I just removed the Modernizr dependency. I kept jQuery 1.7. I kept underscore.js for the great _.debounce function.


Imagine if you're replying a long thoughtful reply to this post and you lose because you close the window, or your browser crashed. Load the page again and it'll be there.

We use this for Teambox, where users type long long descriptions for some things.


Update (I'm the author). This is the feature I finally implemented: https://gist.github.com/1733598

It listens to see if the user scrolled recently and navigated away without clicking, and then explains her what happened and how to avoid it next time. You can dismiss that message if you like Mac's behavior, or you now know how to disable it. Easy peasy.


So maybe you should update your blog with the fact that this is NOT a case of "Lion breaks the web" but in fact a case of "Chrome and Firefox break the web because they can't /copy/ a feature without stuffing it up"


froth much?


The author claims "Lion breaks the web". This is false, and the majority of people commenting seem to simply ignore that the problem he sees is caused by third party browsers that attempt to copy a feature in the included browser, but fail to implement the usability/UX part correctly, thus causing the issue.

How is highlighting that "froth"?


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search:

HN For You