How about Safari? This would be very useful as not every developer has Apple hardware
Yes! Safari is also on the roadmap.
Readit Newstoekneestuck commented on Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years · Posted by u/thedg
toekneestuck commented on Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years · Posted by u/thedg
[I work at Jam]
- Yep, your header would be scrubbed by our default definition. And also: yes definitely, configurable scrubbing is on our radar/an inevitability. Sensible defaults has been our goal, but we're definitely aware that any given keyword may be sensitive to one company but not be to another! (e.g, an address in the context of a healthcare org's patients may be sensitive, but likely wouldn't be considered sensitive for an MLS search product)
- Re: Sentry — Makes sense! There's likely a lot of team-level configuration we can add for integrations over time
- Re: Linear — that's a good question. We used to have much deeper integration with some third parties, so I think we may be able to tighten up some of those scopes. I created a ticket for us to follow up on this, thank you!
Quick follow up on the integration with Linear: just confirmed that we do not need write scopes on the workspace. The fix will be in production by next week :)
toekneestuck commented on Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years · Posted by u/thedg
Some thoughts:
- Make the scrubbed headers configurable (if it isn't already). For example, our token header is called `X-Session-Token` and is passed on every request. Would your current regex scrub this?
- Maybe clarify that the seat (pricing) is for recorders, not for people viewing them (which I think is a reasonable choice).
- Would be nice to configure auto-deletion of Jams after X days. We'd probably go with 180 days.
- Would be neat if the Sentry integration had configurable fields (at the team level set which ones are visible, and set fixed values for some of them). For example, I don't want anyone to set the project (that's the triage step in Linear), and I want only some teams to be selectable, I'd like to skip the 'effort' altogether, etc.
- Make it possible to configure the text body of the Linear issue, with placeholders for content. For example, we'd like to skip the full-screen (non-cropped), maybe show window size or add other metadata that is often relevant to us.
One question:
- For integration with Linear, you are asking for write access to the workspace. Maybe explain why that's needed, and what it means? Same for read (though this seems more reasonable, an explanation would still be useful)
[I work at Jam]
- Yep, your header would be scrubbed by our default definition. And also: yes definitely, configurable scrubbing is on our radar/an inevitability. Sensible defaults has been our goal, but we're definitely aware that any given keyword may be sensitive to one company but not be to another! (e.g, an address in the context of a healthcare org's patients may be sensitive, but likely wouldn't be considered sensitive for an MLS search product)
- Re: Sentry — Makes sense! There's likely a lot of team-level configuration we can add for integrations over time
- Re: Linear — that's a good question. We used to have much deeper integration with some third parties, so I think we may be able to tighten up some of those scopes. I created a ticket for us to follow up on this, thank you!
toekneestuck commented on Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years · Posted by u/thedg
I 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 :)
toekneestuck commented on Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years · Posted by u/thedg
Looks very useful for developers but I am not a fan of being on a website that has a keylogger installed onto it. I know this is not the first tool to do this, but the thought of every single thing I do getting stored by some third party tool is a bit scary.
[disclosure: I work at Jam]
I generally agree with you. I think there's a few important things to note:
- Since Jam is a browser extension, its functionality only applies to the user that installed it (i.e., only you, not everyone that visits website X) - All captured data stays locally in your browser until _you choose_ to submit a bug and its details* - You can choose which sites the extension is enabled on if you want to further limit the scope of functionality - We have some user preferences to enable/disable certain functionality of Jam already, and I'm confident we'll add more over time!
* to be fully transparent: we _do_ collect application telemetry so we can identify bugs and performance issues, but we take great care in reporting information that is centered around what our application is doing, not what it is capturing.