Show HN: Snapbugz – The easiest way to discuss bugs.(snapbugz.com)
snapbugz.com
Show HN: Snapbugz – The easiest way to discuss bugs.
http://www.snapbugz.com/
41 comments
I lolled at "as not yet seen on" too.
The proxy issue is indeed unacceptable.
The proxy issue is indeed unacceptable.
I had a chuckle at that, and the links to tweet them was a nice touch :)
With Firefox 27 (or Safari 7.0.1) on a MBP running Mavericks I get the error:
"Bummer! Creating a Snapbugz currently only works on desktop computers."
"Bummer! Creating a Snapbugz currently only works on desktop computers."
Where can I discuss that bug? ;)
http://i.imgur.com/IGuNEzT.png
http://i.imgur.com/IGuNEzT.png
For all having this "desktop" issue on real desktops - please give us more information via hello @ snapbugz.com. Kudos!
My suggestion is instead of chasing UA sniffing (which is a losing proposition), just give up on blocking "mobile" or any kind of browser.
FWIW my mobile browser is just as capable as my desktop and as long as you don't block zooming I can deal with an "unoptimized" layout.
FWIW my mobile browser is just as capable as my desktop and as long as you don't block zooming I can deal with an "unoptimized" layout.
The creation part of snapbugz is just not ready for mobile/touch usage as UX patterns on the annotation part are different. However, the result / collaboration part is already finished: http://www.snapbugz.com/p/88a7a69a
I'm against bug-tracking systems that fork a program's (or web-site's) own bug-tracking system. You end up with multiple problems:
1) The same bug in both places, with different buy useful discussions in each. How do you merge these two bugs? How do you mark one as a duplicate?
2) The developers of the program (or web-site) probably don't know you exist, so while there might be a great discussion related to the bug, the person who can actually resolve it doesn't know.
3) Assuming you're not the only "foreign" bug-tracking system for a program (or web-site), how do you interact with the other "foreign" systems?
4) There's no barrier to entry, so there's no incentive to creating anonymous bugs or to using the platform to rant at the developer.
You're not alone with these problems - GetSatisfaction and UserVoice have the same issues. My suggestion would be to create such an amazing bug-tracking system that the developers WANT to use it as their primary source. Then get bought by Github.
1) The same bug in both places, with different buy useful discussions in each. How do you merge these two bugs? How do you mark one as a duplicate?
2) The developers of the program (or web-site) probably don't know you exist, so while there might be a great discussion related to the bug, the person who can actually resolve it doesn't know.
3) Assuming you're not the only "foreign" bug-tracking system for a program (or web-site), how do you interact with the other "foreign" systems?
4) There's no barrier to entry, so there's no incentive to creating anonymous bugs or to using the platform to rant at the developer.
You're not alone with these problems - GetSatisfaction and UserVoice have the same issues. My suggestion would be to create such an amazing bug-tracking system that the developers WANT to use it as their primary source. Then get bought by Github.
Thanks for your points.
Indeed we tried to solve some of your points at http://usersnap.com (the technology behind snapbugz). We integrate with different, existing bug trackers but made the experience that there are many people who still rely on email as a bug tracker.
Indeed we tried to solve some of your points at http://usersnap.com (the technology behind snapbugz). We integrate with different, existing bug trackers but made the experience that there are many people who still rely on email as a bug tracker.
I like the fun feature when I type the site's own URL into the search box. First a message that reads "Do you really want to see the internet implode?", followed by a redirect to the "Google into Google" sketch from The IT Crowd[0].
[0] https://www.youtube.com/watch?v=OqxLmLUT-qc
[0] https://www.youtube.com/watch?v=OqxLmLUT-qc
I didn't. I actually wanted to report a bug with their site, that it lacks any explanation of what it does and why you'd want to use it (eg, does the feedback actually go anywhere?)
Pretty asinine that I can't even read about what snapbugz is in my mobile. It might be the greatest thing since sliced bread, but I'll never use it, because I tried to find out more info and got slapped in the face for it. If it were of interest, then I would email myself a reminder to use it on desktop.
Creating on mobile is on our agenda for the next week.
In the meantime, have a look at the result page for mobiles please: http://www.snapbugz.com/p/88a7a69a
I tried one of our sites, we force https, it seems the 's' is stripped and loading fails. If the site is about discussing bugs, I would think a target market is web applications, pretty much all of which will be using https.
And most bugs are often found before going into production, so client's will be accessing the site behind an IP restriction or HTTP auth most likely.
For full HTTPS / IP-Restriction / Auth / external bug tracker support, please have a look at https://usersnap.com - this could fit your professional requirements.
I tried to load one of our sites - specifically with very minimal "helper" Javascript and it also failed to load the site. I can't imagine it would load anything on a site where the DOM is only 2-3% complete when onLoad() is called.
Images didn't seem to load in the produced screenshot, though they did load in the preview where I marked the area. Unfortunately I could not snapbugz http://www.snapbugz.com/result/minichan.org/a5a77fcb-f86a-4a... as instead it took me to https://www.youtube.com/watch?v=OqxLmLUT-qc
Looks like the page minichan.org does a referer-check for all images to prevent hotlinking.
Love the "As not yet soon on:" logos at the bottom which tweets to those publications about Snapbugz. Great marketing hack.
Seems somewhat similar to how Google did it for Google+ in the early days. I'm surprised it took this long for someone to replicate that feedback system to be honest. I thought it was brilliant from the moment I saw it.
Have a look at http://usersnap.com :-)
Please stop the background requests to tons of 3rd party servers. It's such an unhealthy trend. (Now that we know that everybody and their mother tracks and profiles us all the time.)
If you type snapbugz.com into snapbugz.com, you can break the Internet. So please, no one try it—even for a joke. It's not a laughing mater. You can break the Internet.
For all on mobiles - here is an example result page: http://www.snapbugz.com/p/88a7a69a
I thought this was for discussing bugs in bug trackers like bugzilla. Then I thought this was related to FogBugz, but it's neither.
So, how does one render a website properly into a PNG? Headless Chrome?
It's done by Usersnap: https://usersnap.com/
http://phantomjs.org/ would be a good start.
wkhtmltopng part of: http://code.google.com/p/wkhtmltopdf/
> Easiest way to discuss bugs
Not on mobile it's not
Not on mobile it's not
I thought it was neat that they let me email myself with a reminder. This is an MVP, it's just the right response.
this is very cool, I definitely plan on using it.
just curious, why only store the bug for 7 days?
just curious, why only store the bug for 7 days?
You can extend the storage time by inviting others to discuss - 1day per invite. (If you already have sth like a bug tracker / pm in place - look at https://usersnap.com ).
nice. Is the storage time simply an up-sell mechanism? or is there a technical issue at play? again, just curious.
No, no technical issues :-)
Latest Chrome probably shouldn't have this.
> "As not yet seen on:"
Putting this at the bottom of the page with a list of popular website's icons is disingenuous to say the least.
It's also not clear to the user, but this service silently proxies any site you go to with little concession for what the user might be doing. Given that they're already being so unpleasant with the bottom links, I wouldn't hesitate to think that they are capturing user content as well. Even if they aren't collecting private data, they're stripping SSL data and serving it back up in plain text.
Completely unacceptable.