Does anyone know of a similar tool for catching SMS messages in local/development environment? My company uses mailtrap[0] in our development environments to give engineers and product managers a tool to preview emails that would otherwise be sent to users and we're looking for a similar tool for the SMS messages that we send via Twilio. I'd love to have a shared "inbox" per-development environment where PMs can see all the SMS messages that would have been sent (namely to whom the message was sent + the content of the SMS). Ideally it'd hook into whatever Twilio SDK your app is using to send messages (Python, in our case) to intercept calls and route them to the sandbox instead.

It seems like Twilio played with this idea with the Twilio Dev Phone project[1] but that project doesn't seem to be actively maintained.

[0] https://mailtrap.io [1] https://github.com/twilio-labs/dev-phone

This is what Mailosaur[0] offers - countries available depends on tiers though due to the number operating costs and associated regulations.

[0] https://mailosaur.com

Not the same thing, bit VCR and variants can help with testing external api calls (see "ports to other languages"):

https://github.com/vcr/vcr

That is a false equivalency.

We (theoretically) have control to improve and enhance workers' rights, and can make legislative changes to increase job security, or decouple the ability to live and subsist with employment.

"almost" was written intentionally.

I don't see Chrome going anywhere for a long time, and I don't see Google blocking its own analytics service within its own browser on its own volition.

Google may have a hard time continuing to explain away it's refusal to respect user privacy as the sole browser that doesn't block GA. And if the Chrome team continues to fight privacy initiatives, Chrome will be replaced by something like Edge, which is compatible but also actually cares about privacy and security (these two things are the same, if you aren't prioritizing privacy you are not a secure browser).

Regulators will also be paying attention to this over the next few years.

I think a startup should be very aware of these risks if building off of GA.

I have a hard time believing Edge is any more private then Chrome, it's just a question of who gets the data.

I'd love to be proved wrong on this though.

It's weird for you to believe this, because Chrome is made by an ad company whose sole goal in existence is collecting data for ad targeting...

Many of Chrome's features are implemented in Edge by replacing Google services with Microsoft ones. So for many things, Microsoft may be collecting similar data (though likely not monetizing it at all).

But the key thing is that tracking prevention: It means your browser is leaking your data around the internet significantly less. Not just less to Google, but less to almost everyone else on the Internet. Chrome, by refusing to implement tracking prevention, is pretty much a leaky ship with holes in it.

Here's Edge's implementation: https://docs.microsoft.com/en-us/microsoft-edge/web-platform...

Here's Firefox's implementation: https://support.mozilla.org/en-US/kb/enhanced-tracking-prote...

Here's Safari's implementation: https://webkit.org/blog/7675/intelligent-tracking-prevention...

Chrome has nothing. Google paid some of their staff to write a FUD piece about how preventing tracking was a privacy risk somehow.

All valid points. Much appreciated.

I was coming from a position of "Why would MS remove anything instead of redirecting it to themselves", but failed to consider that they would be adding things themselves to prevent other tracking.

And don't get me wrong, I agree Microsoft is no saint on data collection. I use Firefox and encourage others to do so. But I'd recommend Edge over Chrome because I consider tracking prevention so necessary for safe browsing.

Microsoft's data collection and use seems primarily to be focused on telemetry for product improvement. They obviously do it in Edge too. I find it less malicious than ad targeting, but I'm strongly opposed to mandatory telemetry. And I think telemetry-driven development is a mistake that should be avoided. It dehumanizes software support and still provides incomplete information, while also violating the privacy of your users.

Agreed that it's too late in that the key is compromised at that point, but a notification before you release to production that you've accidentally committed it allows you to roll the key (hopefully) before any bad actors find it.

Time and time again, the Next.js (and Zeit) team blow me away. The rate at which they release new, high-quality versions of their products is astounding, especially given how few people are working on this full time -- it's basically just Tim Neutkens, who's insane: he's constantly pushing updates, reviewing PRs, and finds time to be very active on the support channel.

We use a bunch of Zeit's tools (particularly Next.js and its static export feature) at Common (https://www.common.com -- we're hiring!), and they're consistently such good and reliable products (doesn't hurt that they have a sharp focus on developer experience).

Congrats to Tim and to the entire Zeit team!

> it's basically just Tim Neutkens, who's insane

Insane is an understatement. The dude has helped me on the support channel more times than I can count. Forever grateful.

Not to mention pkg is pretty awesome too from Zeit

> it's basically just Tim Neutkens, who's insane

when looking at tools to build a business on, that can be a liability no?

Fair, but my confidence in it stems from the giant community around Next.js. Zeit, a company with a good reputation among developers, works on it full time. It has contributions from other big-name OSS contributors and big companies (Netflix, Hulu, Nike, Ticketmaster, Jet, Auth0, Marvel, etc.). It's definitely a liability if it were truly just one individual developing it, but I suppose it's more that there's a small core of facilitators, with a giant OSS community around it.

As said elsewhere, I mostly act as a curator of a very large effort of hundreds of individuals. The project was actually co-created by several other people who work on infrastructure at ZEIT (e.g..: Naoyuki Kanezawa led all the initial releases, designed important parts of the framework, Arunoda Susiripala contributed the test harness and key build pipeline infrastructure, and so on).

Curious why you didn't mention Arunoda -- does he not work on it anymore. IIRC Arunoda started Next.js right after (perhaps because of) leaving Meteor ecosystem.

I don't think he created it, but he was there early on and works for Zeit. Still eternal grateful for him creating kadira.

Wow, TIL. Also a very nice display of Cunningham's law: "the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer."

I'm going to post the same answer I gave in another thread on the initial post:

As said elsewhere, I mostly act as a curator of a very large effort of hundreds of individuals. The project was actually co-created by several other people who work on infrastructure at ZEIT (e.g..: Naoyuki Kanezawa led all the initial releases, designed important parts of the framework, Arunoda Susiripala contributed the test harness and key build pipeline infrastructure, and so on).

Completely agree! I have used next.js in multiple projects now and have gotten very fast turnaround on any submitted issues. Love the product and the team!