From the various links in the comments, the telescope uses special filters in front of the lenses to capture the faint glow in specific wavelengths emitted by the circumgalactic medium (a new word for me!) aka "gas" around galaxies.
Curious, what does someone gain with MacTCP? I'm not familiar with the space, but a casual glance (not an assessment!) suggests that OpenTransport was standard-ish from system 7.6 onwards.
Does it boil down to compatibility with older hardware?
Different software. They had different APIs from the programmer perspective. MacTCP was older and was based on Berkeley sockets (I think with some BSD code in the implementation?) and was somewhat primitive.
OpenTransport was fully multithreaded and based on SysV UNIX streams. Technically much superior. It has partial MacTCP API support for older apps but some programs demanded real MacTCP to work properly. I think Mac was the only place that really used Streams widely. Mac network programming in the OpenTransport days was alien from a Unix perspective.
OS X now uses sockets like everyone does these days.
Going off memory here it has been a long long time.
I've been playing with this for a few hours and had similar questions about scrubbing custom tokens or headers from the submitted data.
One concern I have about the instant-replay feature is the potential performance implications when monitoring multiple tabs or windows. I'm not particularly fond of the idea of all sites in this way and prefer better controls there.
I saw the block list inside the extension, but I think an allow list makes more sense for this use case. That way, .ycombinator.com or .example could work as opt-in for instant replay, and ideally, those domains could be preconfigured at the team level.
Acknowledging Chrome's extension per-site permissions is a valid option, but it's clunky.
+1 vote for a datadog integration, in addition to backend data I would love to see this work well with RUM. For now, I'll settle for jamming a common ID into Jam.Metadata and see how that works out.
I also thought Jam would accept bug reports from end-users and look forward to the development of that feature.
Comments synced to timestamps in the recordings are nice. Have you considered a scribble/annotation like the still screenshots, but for videos? The annotations could be anchored to the comment timestamp, and they would help capture a UX micro-interactions that may not be obvious in a still or video.
I think the reason for having the permissions for all sites is for when you want to use the instant replay feature on the off chance and you realise that there were no permissions enabled for the specific domain.
I'd be pretty annoyed if the bug is not reproducible and I lose that chance of generating a bug report.
That’s great feedback! The way we currently solve that is by setting a memory limit for Instant Replay and then automatically disabling that feature when the limit gets tripped.
Yeah +1, the reason why we built a blocklist vs an allow list is because Chrome settings already allows you to specify an allow list for extensions so we were just trying to round out what settings you couldn’t set already in the browser.
Also I love the idea of annotating a video, sharing that with the team! Thank you!
> June 5, 2002 - Mozilla.org, the organization that coordinates Mozilla open-source development and provides services to assist the Mozilla community, today announced the release of Mozilla 1.0, the first major-version public release of the Mozilla software. A full-fledged browser suite...
IIRC one of Mozilla's v1 killer features was "tabs" in a time when opening links in a new window was the only (mainstream) option for a meandering web junkie.
Trademark games are pretty common in consumer tech. FaceTime and iOS are high profile examples of names ("marks" in parlance) that ended up licensed / transferred.
I'm trying to avoid sounding overly nostalgic about Palm OS but it really was a nice personal computer.
This snippet highlights the focus on UX (beyond the look and feel!), and as creators I think many of us can relate to (and maybe remind others...) how great products require deliberate care in design AND implentation.
> The user interface received particular scrutiny. Hawkins set firm limits that any slow operation be reworked instead of showing a busy indicator, and explicit error messages should be avoided. Graffiti was a given because handwriting had to work, as no physical keyboard would have fit at the time. Mindful of how unusual such a device would be to many users, Ed Colligan declared that Touchdown should “delight the customer,” and developer Rob Haitani established a design theory he grandly christened the “Zen of Palm"
Absolutely, I get the concern about the docs looking like a placeholder. We're putting a lot of effort into crafting the best SDKs for major languages, so for now, the most comprehensive guide is at https://docs.postack.dev/api-reference/introduction.
Regarding A2P messaging, it's pretty standard: create your brand and campaigns, typically with a 72-hour turnaround. We're streamlining compliance by auto-generating legal documents, webform screenshots using templates, and leveraging ChatGPT to preemptively fix any issues before they reach upstream carriers. It's all about making the process as smooth as possible for you.
On Twilio: It took me a staggering three weeks just to get my business profile reviewed and approved, followed by another 2-3 weeks of back-and-forth communication to get my campaign off the ground. It was a real test of patience.
Not meant as a nitpick but lots of links to docs are "dead" or redirect to that placeholder. quick example: on your home page both compliance links go nowhere.
