This is a tool to analyze large goroutine stacktrace dump files, to assist in debugging by parsing the dump and displaying it in a structured table.
It works entirely client-side (no data is uploaded or stored), groups together goroutines with identical stacktraces into a single entry, and allows quickly sorting/filtering/searching.
But isn't suing to enforce his patent rights also an expensive legal battle that he would need to somehow fund?
I don't see how this threat could be seen as effective.
It's not mentioned in the article, but using the MULTI command (exposed as client.multi() in this module) can sometimes help alleviate this if you need to execute multiple redis commands whose inputs/outputs do not depend on each other.
A while back I actually built a mobile site for playing Jeopardy (originally conceived as a drinking game based on jeopardy, but that's another story...) part of which was a scraper that pulled data off the fan-sourced site and parsed it out.
in that case, you might like outloud.fm. the design is barebones and utilitarian, both twitter and facebook logins are supported, and you can also play tracks from soundcloud.
full disclosure: i built it.
>Most access tokens expire in two hours, but some tokens work offline and remain valid until the user changes the password, Doshi said.
FB users can just go into their authenticated applications list and revoke access tokens on a per-application basis. Changing passwords shouldn't be necessary - that's the whole point of access tokens.
Thanks! I definitely have no intention of trying to launch this as a 'product' because of the legal issues involved - I just did it as a fun experiment.
It works entirely client-side (no data is uploaded or stored), groups together goroutines with identical stacktraces into a single entry, and allows quickly sorting/filtering/searching.