Show HN: A new way to consume the social web
tawlk.com
tawlk.com
It still has some rough edges which we very much hope you all can help us work out. As we obviously want to monetize parts of our platform in time, we want to listen to the community to create the best tool possible. To that end, we have already open sourced some of the libraries behind Tawlk via http://github.com/Tawlk and we welcome any contributions or forks. We very much believe in the "Open source -Almost- Everything" model.
Also worth nothing about this demo, is that to make good use of our current limited server resources and to avoid hitting API and CPU limitations, we are utilizing many relatively new techniques including combinations of WebSockets, HTML5 localStorage, HTML5 App Caching, and direct browser-side data collection to make it work.
I hope you find the beta interesting and intuitive. I look forward to your comments or questions.
If you find bugs, please screenshot them with steps to reproduce so they can be taken care of quickly and please be nice to our servers :-)
EDIT: If you see connection errors you can dismiss it with the "x" in the top right. Search should still work, you just wont get any of the websocket supported sidebar stats (which i very much encourage you to try out on another network). We are working on some fallback connection methods to resolve this for firewalled and otherwise unable-to-connect users.
In the mean time, here is a reference rendering: http://dumpon.us/media/uploads/TAWLK_GUI_HORIZONTAL_V18_1.jp...
[Edit: Added a missed word]
Connection Failure: This is probably due to the fact
your browser does not appear to support a technology
called "WebSockets" which Tawlk relies on. We are
working hard to bring full compatibilty with a wider
range of browsers soon. In the interim please consider
using the latest version of Chrome, Firefox or Safari
Yet I am using Chrome (16.0.912.63) on OSX.Once the load spike dies down a bit we will be working to push out some protocol updates to help provide fallback support for browsers that for whatever reason can't maintain a stable websocket connection.
I will probably check it out when I get home from work but as of now I am a little annoyed that I cannot try it out.
The connection errors happen when there is limited websocket support due to browser or network. We are working on a migration to sockjs so we can have some flexible fallbacks just in case. If you dismiss the error the main search should still work, you just sadly wont get any stats. Probably best to wait till your on a direct connection for now.
Obama: 44% positive ("barack obama" is 62% though)
Mitt Romney: 67% positive
Michele Bachmann: 50% positive
Herman Cain: 71% positive (?)
Ron Paul: 71% positive
Rick Perry: 81% positive (??)
I am not sure the sentiment calculation is just based on Positive/Negative dictionary comparison or something else. Is there a logical explanation of above percentages? Do results vary for other people?
We however only have the server resources to have a large rolling window for a limited number of topics (currently the ones in the side bar).
When you searched for "Barack Obama", it based the sentiment score on just what your browser collects live on the fly, whereas when you searched "obama" you got sentiment calculations based on our server collected rolling data set which is far more stable.
Both are fairly accurate, however they differ in how large of a window they are averaging against.
As topics become more popular and as server limitations allow we automatically migrate them server side for more aggressive collection to provide more reliable sentiment.
We also only provide scores and reach assessments for topics we posses enough server-side data for to justify it.
One question I have is do you plan on filtering out the noise? There seems to be some content that I would consider spam or highly unrelated to the topic that I choose to search.
We have developed a strong revenue strategy around social data and sentiment analysis. Feel free to shoot us an email for more info. In the meantime we are just looking for people like you to enjoy the product and have fun with it!
I like the interface a lot, and it certainly seems well architected (in that I've had it open in three tabs simultaneously and not noticed any lag whatsoever).
However, to use an idea from the Intercom.io blog[1], what job would I hire this app to perform?
Well currently it could be used by brand managers to see how popular or unpopular a given topic or person is, or to have an easy way to digest overall stats about the topics social presence.
You could also do things casual like just seeing how people feel about Obama compared to Justin Beiber or android phones or use it while watching a live event to see what people are saying about it. Live results are one of the ways this stack really shines.
As far as where we are going to take the platform, we have some strong ideas ready to implement provided we get the right investment group interested. Lots of things that would be more interesting to those wanting to hire this to do a "job" for them or their company.
Also, Just to check the buzz about Talwk, I visited tawlk.com/#!/tawlk and witnessed the oh-so-tragic condition of the enlish language on the interwebs.
We will be implementing a lot of features like this soon to give a far more relevant and diverse range of data based on its social media popularity for a given topic.
Console is full of errors: http://dl.dropbox.com/u/533753/Screen%20Shot%202011-12-15%20...
It also took me a long time to figure out how to close the about modal...
Tawlk communicates with all the major APIs directly from your browser on your side of the network.
I noticed you've open sourced a bunch of your modules in Javascript and Python. Out of interest what does your technology stack look like? (framework choice etc)
The only thing not really detailed here is that the whole stack runs on a set of redundant servers with Round Robin DNS at the helm to randomly distribute between them.
Also "caching proxy" should really just be called "routing proxy" as that is all that we are using it for. If websockets go to Tawlk app, if else go direct to nginx static serve.
I tried with Safari and it worked.
Opera - OSX 10.6
For Flickr that is a very fair point, we need a way to link to the original Flickr URL. That is a UX oversight we need to resolve.
Where are you seeing "Reset Tawlk?"