20160828 22:46:34 +0200  received badge  ● Good Answer (source) 
20140923 12:12:42 +0200  received badge  ● Good Answer (source) 
20140923 12:12:42 +0200  received badge  ● Nice Answer (source) 
20120920 13:11:19 +0200  received badge  ● Nice Answer (source) 
20110602 18:02:18 +0200  received badge  ● Nice Answer (source) 
20110514 16:53:23 +0200  received badge  ● Famous Question (source) 
20110102 04:14:03 +0200  received badge  ● Good Question (source) 
20110102 04:14:03 +0200  received badge  ● Nice Question (source) 
20101209 11:29:54 +0200  received badge  ● Notable Question (source) 
20101209 11:29:54 +0200  received badge  ● Popular Question (source) 
20101014 23:11:12 +0200  received badge  ● Teacher (source) 
20101014 23:11:11 +0200  received badge  ● Student (source) 
20101014 23:11:10 +0200  received badge  ● Supporter 
20101014 23:11:10 +0200  received badge  ● Autobiographer 
20101007 04:38:27 +0200  answered a question  exponential equation real solution Well, my answer doesn't use Sage, but: your equation is equivalent to cosh(2x) == 1. The hyperbolic cosine function (cosh) has a global minimum at 0, so there's only one real solution: zero. Other things that can help you figure this out: plot exp(2x) + exp(2x) and see what it looks like. Show that the derivative is positive for all positive x, and negative for all negative x, and use that to prove that the function has a global minimum at 0, so that the original equation can only have one solution. 
20100825 01:08:23 +0200  answered a question  how do I install an spkg? There's also "sage f" (the "f" stands for "force"), which works just like "sage i" but will install the spkg even if the same (or a later) version is already installed. This is very useful when you're working on a spkg and making little changes, or if someone gives you a modified spkg with the same version. 
20100822 23:39:18 +0200  commented answer  Is there a way to make an audible noise when a computation is complete? Also, if you are not working with the notebook, you can use Python's subprocess module and any commandline sound player: just define the done() function as above as something like subprocess.call(['ogg123', 'path/to/file']) 
20100822 23:32:52 +0200  commented answer  Is there a way to make an audible noise when a computation is complete? That is a *fantastic* "I'm finished" sound. Way better than some lame old beep. :) 
20100819 02:18:20 +0200  asked a question  What features should we add to this site? As a companion to the "what's broken" question, what features should we add here? As a start, it would be nice if there was some mechanism for autolinking trac ticket numbers. Other autolink ideas:

20100819 02:09:48 +0200  answered a question  What are my best options for taking advantage of multiple cores? 
20100819 02:03:06 +0200  answered a question  How do I avoid sage_constant compile errors? This question seems a bit vague. Can you give an example in which xrange fails, but a preallocated list works? What's the error that using xrange gives? 
20100818 21:50:07 +0200  answered a question  Why is so hard to use Mercurial queues?
I don't know about the reviewers you worked with, but when I'm reviewing tickets, I only care about what kind of patches are posted  I don't care how they were created. A clean diff, ticket number in the commit message, proper username...that's what I want.
Right now, probably not. But I did find that once I figured out queues, it was the most natural and easy way to work. Take a copy of Sage, qimport a patch, test it, pop and delete it  and my copy of Sage is just like it started. Things get a bit more complicated with the sagecombinat stuff, since they have a huge queue and use guards and all that  but you can ignore that stuff. It sounds like much of your confusion would be cleared if you could sit down with someone and have them show you things  or maybe a good chat on IRC with a shared screen session. Read the Mercurial book and ask questions. I think you can understand queues without too much trouble. 
20100818 21:11:56 +0200  answered a question  What should the FAQ contain? Before answering the question "What are some key points that the FAQ for this ask.sagemath.org site should make?", we need to know exactly what this site is for. Do we want questions about how to compute things with Sage or other software? Do we want questions about installing and basic usage of Sage? Do we want questions about design, improvement, bugfixes in Sage? Having a welldefined focus will certainly improve the usefulness of this site. I would like to see the relationship between this and the mailing lists explained/decided. We might also develop some guidelines about the questions that are asked. It seems like a question such as "Should we support 32bit FreeBSD?" would not be ideal for this venue; a question such as "I have a bunch of data in format X, how do I load that into Sage, interpret it as Y, and then compute Z?" seems much better. 