2012-09-23, 16:45
I should probably also mention that I have investigated using github as the destination for the error reports.
Unfortunately github requires that you are authenticated when creating the issue - it's possible to setup a scope in the OAuth setup, but it is very wide and would give access to every action on a repo, not just access to create issues - so I dropped implementing that.
I had a quick look at google code, but i think it's the same problem.
I have also considered email as Tria suggested above, but in my experience sending an email from a random box is not as easy as you might think due to all the spam and what not that is sent on the internet these days... SMTP servers are pretty much locked down (otherwise they would be an open relay) and I don't think it's a good idea to ask the user about which SMTP server to use.
If you have another suggestion please let me know...
Unfortunately github requires that you are authenticated when creating the issue - it's possible to setup a scope in the OAuth setup, but it is very wide and would give access to every action on a repo, not just access to create issues - so I dropped implementing that.
I had a quick look at google code, but i think it's the same problem.
I have also considered email as Tria suggested above, but in my experience sending an email from a random box is not as easy as you might think due to all the spam and what not that is sent on the internet these days... SMTP servers are pretty much locked down (otherwise they would be an open relay) and I don't think it's a good idea to ask the user about which SMTP server to use.
If you have another suggestion please let me know...
