> but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took Ah ah. At one gig we had trained the users to always send a screenshot of the entire screen. People reviewing the tickets would dump them if the screenshot was cropped and the user warned: "No full screenshot, no ticket" . Why? The most important info was the time at which the error happened (…
Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
141–150 of 240 posts
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#142"network tab" isn't it a security concern to record API calls? Also how future proof it is with Google changing Chrome addons permissions / API etc...?
Great concern! We do two things to address that: The first is nothing gets recorded and saved (or even sent to our backend) until the user actively chooses to log a bug. So it’s like actively choosing to save a HAR file when there’s a bug. The second is we scrub all network requests on the client side for anything that resembles PII or sensitive data. We just don’t want it on our servers. Is there anything else you t…
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#143Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#144Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#145Earlier quoted context omitted.
Indeed, that's a great rule. Another one is "What URL was the browser on?" which is rarely ever in cropped screenshots but is visible in full screenshot
Don’t many browsers hide the full URL now?
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#146Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#147I got really excited before I saw there was no firefox support. Thats a deal breaker for my team :( I really like this idea and if Firefox support was added I would purchase it in a heartbeat.
[I work at Jam] We do have an internal build for Firefox.. it's coming :)
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#148Earlier quoted context omitted.
Don’t many browsers hide the full URL now?
Oh maybe, I do remember hearing about that. Mine don't (Firefox & Chrome on Fedora) but maybe that's a default setting (on Linux) or maybe I changed the setting and forgot about it?
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#149The explanation for why OP built Jam was precisely the motivation I had for building Bugcam. I had transitioned to a team in Europe as part of an acquisition that had non-technical PMs filing bug reports. Their reports were completely nondescript and incredibly frustrating to decipher and repro.
I ended up abandoning the project due to other opportunities that came up. One interesting thing I noticed was that a significant percentage of users downloaded Bugcam to record themselves playing games for YouTube. Perhaps there was another opportunity there, but I decided not to pursue it.
Congrats on the product and best of luck Jam team!
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#150This looks really interesting, but I want to walk you through the journey I just had on your pricing page. 1. This looks really cool and it has a free tier. 2. Okay you have to pay for bug trackers...oh cool they support Linear and it's only $8. Maybe I'll just put that on my creditcard and get the founders to pay for it once it's proven itself. 3.Oh wait that's for two users and I have 2 founders (non tech), 3 techs…
Appreciate your feedback! Feel free to reach out and we can give you some free credits to your account: dani@jam.dev We really just care that we can help you streamline bug reporting, we don’t want the pricing to get in the way.