Writing a good bug report is not easy, and users should not be expected to know what information the developer will need to find and fix the bug. They only want to report that there is a problem, and that they'd like it fixed.

That said, you can guide them to give more useful information. I found that making a form to fill out with all the details broken out into separate pieces gave us more useful information. Want to know how to reproduce the bug? Make that an individual question on the report. Which component where you using, or what web page were you on? Make that a specific question. A real person can follow up if necessary to get other information, and then they can file the "official" bug report in the form that the developer can understand and use.

I'd say we definitely need something besides Cryptocat:

"Cryptocat is run by people that don't know crypto, make stupid mistakes, and not enough eyes are looking at their code to find the bugs. Cryptographers know the minimums or at least know you should look them up. Cryptocat tried PBKDF2, RSA, Diffie-Hellman, and ECC and managed to mess them all up because they used iterations or key sizes less than the minimums. There was a bug in the generation of ECC private keys that went unchecked for 347 days."

(As far as the competence of the people behind heml.is, I can't say one way or the other.)

Solar powered chargers in the aftermath of a hurricane?
It'll be days after a hurricane before there's a clear day.
Solar panels work poorly on cloudy days ... those on my roof generate about 5 to 30 percent compared to full sunlight.

My first job was delivering telegrams (by bicycle) in downtown Buffalo during the 1960's.
My Western Union office had its hours posted on the door: "We Never Close". The building's been torn down, so, in a sense, the message turned out to be true.

Question: what'll happen to the American Telephone and Telegraph Corporation?

Here in Berkeley, one of the main drags is Telegraph Avenue and a cell-phone store is named "Telegraph Wireless"

I work in computing; a meter away is a mathematician.

He knows real math: group theory, complex analysis, Lie algebras, topology, and, yes, differential equations. To him, math isn't about numbers ... it's about rigor, elegance, and beauty.

No surprise that his code is rigorous, elegant, and beautiful. When he showed me how to use Cheetah to build templates in Python, he explained things with an clarity and parsimony. In his world, clumsy coding is as bad as a clunky math; a clear mathematical proof is as fascinating as a tightly written function.

This man is the go-to guy for the 100 person business. Soft spoken and never argumentative, his advice and opinions carry weight. I'm honored to work alongside him; not a week goes by that I don't learn from him.

If the asteroid has any rotational motion then the crater created by the first impactor will have moved out of the way of the second.

When you win a copyright case you may be awarded your attorneys fees. I can't wait to see YouTube's attorneys fee motion. It's going to make my firm's bills seem like chicken feed.

But the defendant's lawyers have done a great job of beating back the Evil Empire, and in so doing have accomplished an important victory for the vitality of the internet.

Yeah.

And trying to 'maximize' the 'minimal' legal authority that exists to support their positions.

And trying to maximize their eroding monopolies.

Actually, you're 100% right. I think I was trying to decide between the phrase "content cartel" and "copyright maximalists", so my aging brain settled on "content maximalists". Would you change that to "copyright maximalists" for me, please :)

It means the big old school content "gatekeeper" companies, and their trade groups like the MPAA, RIAA, ASCAP, etc., whose economic power is being eroded by digitalization and the internet, and who are fighting back by taking extremist positions in defense of their copyright ownership.

Oops, I forgot to put "(PDF)" after the link to the Judge's 24 page decision, which is indeed a PDF file. I always like to give that heads-up, but forgot to this time.