Our rationale behind bugmates was the situation probably familiar to you: you have an exception, try to search solution on the Internet and find nothing, while likely there was already a lot of other developers struggling the same problem who put some effort to solve this problem, fixed it and never shared it. They left no trace even about the fact that they had such a problem. We see exceptions every day, but only a small portion of these crashes get documented by people who ask for solution on forums.
Bugmates are Samebug's concept to make this situation better. Every stack trace search executed on the web and every crash logged during development in the IDE (assuming the Samebug plugin is installed) will be associated with the Samebug user. In some cases these people just ignore the exception, others will workaround it or put more or less time into finding the solution, but only in the rarest case will someone document the problem and the solution e.g. in a blog post. However, because they use Samebug, their effort and knowledge is no longer in isolation.
Now if you have an exception and check it on Samebug, even if it doesn't have a solutions, you might find your bugmates there, and you can send them a help request.
A help request is a stack trace and the description of the problem. The description might be helpful for your bugmates to identify the problem in cases when the stack trace is not enough, but you can leave it empty if you want.
When you send a help request, Samebug will notify your bugmates about it, and when they answer, Samebug will notify you. We think in this procedure everybody profits:
If you are no longer interested in answers to your help request, you can revoke it on the same page where you requested it. At the moment it does not happen automatically even if you mark one of the answers helpful.
We know that many information that Samebug deals with might be sensitive, we have an adequate idea about privacy even in this early phase.
In the context of bugmates these concepts translate to: