Live data from Hacker News

Tell HN: MailChimp blacklists your IP if you open the browser's dev tools

news.ycombinator.com

31–40 of 204 posts

Re: Tell HN: MailChimp blacklists your IP if you open the browser's dev tools

#31

I used ChatGPT to get a refund from Mailchimp when their CKText editor failed to load on International Women's Day, preventing us from sending an email promotion that day. I opened the web inspector to show the library erroring when Mailchimp tried out a to load it, and also provided a screencast. I wasn't blocked, but I did receive a refund. So this must be a relatively new thing! If I were the OP, I would complain…

[dead]

Re: Tell HN: MailChimp blacklists your IP if you open the browser's dev tools

#34
post #27

That's an anticompetitive move. If you need to switch senders for some reason, the inspector is the only clean way to get an email's HTML into another ESP.

Makes no sense. If you’re considering switching to a different provider, getting blocked makes it impossible to continue to use the service?

Yes it does. Say you're an agency sending email on behalf of several different organizations. If you export one to send through CampaignMonitor (usually list or domain approval related), the employee who pulled the HTML gets their hand slapped by the IP ban. It's less likely to happen next time with a different campaign or different client. I haven't actually experienced the IP ban but I've sent for the same organization through multiple ESPs without quitting one for good.

Even if you are a single organization user and leaving for good, you might do so gradually or perform test sends first. Speaking from experience again.

Re: Tell HN: MailChimp blacklists your IP if you open the browser's dev tools

#35

Earlier quoted context omitted.

Thank you for the description. I assume they're using a bot management script which is set to block requests if devtools is open. For such websites, opening devtools in a separate window should work. Some websites will try to throw you into a loop of debugger statements if they detect devtools being opened, which is harder to work around, but it doesn't seem to be the case here.

Is there an extension or workaround that prevents sites from knowing you opened devtools (without breaking everything else on the site)?

Disabling javascript breakpoints usually does the trick. Devtools detection is often done by having a `debugger;` statement somewhere and timing of it triggered

Re: Tell HN: MailChimp blacklists your IP if you open the browser's dev tools

#36
post #19

That's an anticompetitive move. If you need to switch senders for some reason, the inspector is the only clean way to get an email's HTML into another ESP.

Is that true? An email client like Thunderbird or Mail will save a copy of the email on your local hard drive, which will include the HTML. This isn't something I do regularly, but would be first first response if I needed to see the HTML of an email. Maybe Mailchimp has protections against this route too?

Yes, it's true. You don't want all the chrome from the actual send around the body of your email because the other ESP will be providing that. You might also want to prevent certain fields and links from converting into the send versions. But in a pinch, sure, you could slice the body out of a copy in Thunderbird.

Re: Tell HN: MailChimp blacklists your IP if you open the browser's dev tools

#39
post #33
post #13

How can they tell that you opened dev tools?

I believe there are multiple techniques. One of them is detecting an abrupt decrease in the viewport size.

So ctrl/CMD left/right to move your window to one half of the screen might block you!? XD

Re: Tell HN: MailChimp blacklists your IP if you open the browser's dev tools

#40

Well that is poopy. Is there a way I can “stealth” open dev tools on all sites? I like to see network requests in a lot of places, but don’t like to think the server will change their responses based on my local actions.

There are a couple of ways they can try to detect devtools being opened. As the sibling comment implies, the most popular way is to detect a sudden viewport resize, and you can avoid that by ensuring your devtools are set to open in a new window before opening them. The only other ways I'm aware of are: - Detecting the keyboard shortcut, ⌘⌥i or equivalent, which you can avoid by using the browser menu, and - More ris…

In firefox, you can disable `debugger` by deactivating all breakpoints, making `debugger` a noop.

Toggle the thing in the dotted rectangle: https://firefox-source-docs.mozilla.org/devtools-user/debugg...

Post reply on HN