41–50 of 121 posts
> monster in the middle (MITM) That’s not what it stands for. There’s nothing sexist about using an acronym the same way everyone else does.
I have seen it in at least one other project: https://blog.cloudflare.com/monsters-in-the-middleboxes/ , https://github.com/cloudflare/mitmengine I think it's equally understandable, and monster is objectively a more fun word. Seems like not a big deal?
I said awhile back that QUIC leaving out having a "non-s" mode was going to mean people would just leave keys dumping on :(
> monster in the middle (MITM) That’s not what it stands for. There’s nothing sexist about using an acronym the same way everyone else does.
Chill out. If you start to find offense in everything. you're not going to have a happy life.
Earlier quoted context omitted.
I assume you've never heard of ISPs or vendors that _inject_ ads and other shenanigans on non-https and decrypted https websites?
That's the ISP's problem. Mine doesn't do that. I trust it more than Google, at any rate.
If data privacy is your goal, keeping both at arms length would be ideal... except most people can't choose how much data* ISPs scoop up, or even choose to switch to a competitor if they disagree with an ISP's policies.
*In contrast, you can control a decent amount of what Google collects on you.
Earlier quoted context omitted.
I have seen it in at least one other project: https://blog.cloudflare.com/monsters-in-the-middleboxes/ , https://github.com/cloudflare/mitmengine I think it's equally understandable, and monster is objectively a more fun word. Seems like not a big deal?
Are we also going to change the middleman to middlemonster?
Monster in the middle is at least cute and conveys the authors intent that this agent is untrusted and assumed malicious.
People in this thread clearly don't like being called a monster which I think demonstrates exactly that words matter and these ones are doing their job.
Earlier quoted context omitted.
I have seen it in at least one other project: https://blog.cloudflare.com/monsters-in-the-middleboxes/ , https://github.com/cloudflare/mitmengine I think it's equally understandable, and monster is objectively a more fun word. Seems like not a big deal?
It shifts the narrative to demonize MITM. Ironic seeing a Cloudflare link, given that they are MITMing all traffic. You are not a monster if you are doing it, it's corporations who are monsters if they try to prevent you from doing it and you are fighting for freedom from them. So it's freedom-in-the-middle.
Earlier quoted context omitted.
Being able to choose your ISP is a luxury many people, especially in the US, do not have. Elsewhere there might be choice, but none are really trustworthy. This is about disincentivising ISPs. If it's hard for them to pull off, they wouldn't do it and it would become something normal every ISP does.
This is the thing US brought to itself. Liberal market with minimum regulations. If in my country ISP would touch the traffic, they would get prosecuted by the state. Selling browsing history? Under wiretapping act (you can imagine some jail time). And I can choose between 3 ISPs in country with 2 million people. And optics with at least 100/100 is normal in "larger" city (village in US terms :D) for $60 including ip…
Earlier quoted context omitted.
How do I choose not to use Google properties, including their ad services, analytics, captcha, maps, etc? Is there at least a comprehensive list of their domains, if I choose to block it all (despite that rendering half the web unusable)?
Host list that lists every one of their domains with ip 0.0.0.0
Earlier quoted context omitted.
I have seen it in at least one other project: https://blog.cloudflare.com/monsters-in-the-middleboxes/ , https://github.com/cloudflare/mitmengine I think it's equally understandable, and monster is objectively a more fun word. Seems like not a big deal?
Are we also going to change the middleman to middlemonster?
I said awhile back that QUIC leaving out having a "non-s" mode was going to mean people would just leave keys dumping on :(
Which is the desired result, right? Key escrow forces you to be explicit about who you're allowing to decrypt your traffic rather than letting it be everyone by default.