So how do I see the boobs
post
My original guess was that they're intercepting DNS, but since boobs is in the path, it wouldn't be sent. How does this work?
Don't know if this is entirely accurate, but Wikipedia has article about it.
They are giving response codes like 403 so it's not a failure to resolve and I agree it's not DNS... It's behaving differently based on different sub pages so it's something underneath the https encryption. Maybe an intermediary WAF that decrypts? Maybe some weird server side tooling that has govt provided?
I would guess WAF but I'd love to hear from someone who actually knows.
Right? If it were an unencrypted HTTP GET request, then every router on the way would see the plaintext string boobs in the URL and therefore intercept it.
If I had to guess, Iran has so few landline connections that they man-in-the-middle every TLS connection they can by either forcing every server to hand over their private key files (difficult) or by forcing a certificate authority trusted by default Web browsers (there's a lot of them) to issue certificates for every top level domain they see in SNI data attached to encrypted packet headers; the latter method need not even require participation by Iranian servers, so long as the traffic is bottlenecked for man-in-the-middle attacks and outsiders don't question unusual certificate authorities being used.
It’s either
- Client side ssl forward proxy (MitM cert installed on client)
- in-line decryption in the server
- client side software
- tls downgrade
- cert authority compromise
It was annoying as hell trying to download a LaTeX compiler and having the entire word be blocked, presumably because certain degenerates use latex - the material - for immoral acts.
Why with Iran?
Presumably because instead of responding to the request for boobs.jpg with with an HTTP 404 error (meaning, "not found"), Iran's censorship tech returns a 403 error (meaning basically "you are forbidden from accessing this resource).
The "boobs" are "forbidden" you see; the tech mirrors the ruling party's moral stance, probably coincidentally. Trying the same curl command in Russia and China will likely just get you a 404 error, so the joke really only works with Iranian servers. The 404 version is slightly less funny: "We couldn't find the boobs!"
They should change it to 80085 error.
It's 403 because they are upfront about the resource being censored as opposed to unavailable, and they tell you who to contact if you have legigimate reasons to access it.
Overwhelming majority of countries don't do keyword-based blocking, especially not for incoming requests.
Saves a click?
I dont see a screenshot.
exactly, there is no screenshot and I don't want anyone to need to go to the website
I'd rather my app didn't interact with twitter without my permission
Hmm, Voyager seems to have a problem with posts that are cross-post and have a photo. Thanks for pointing that out.
friend, you have won the internet argument. i say that with no sarcasm whatsoever. the other person misunderstood you, then politely conceded after you made a more detailed comment, adding that this being a crosspost might have caused the bug.
they didn't say "oh huh, must be my app", they said "ohh yeah, it probably is my app, thank you."
what more could you have asked for? what response would you rather have gotten?
To keep me off Twitter, thank god.
Lemmy itself doesn't allow posting a link and an image together, at least not in the default UI on lemmy.world. Consequently, apps being able to show them together isn't the go-to expectation.
P.S. Upon reading your comments further below, it's outstanding what an annoying prick you are.
I was thinking maybe some types of Lemmy apps/clients don’t show it? Mine does but I was giving the commenter the benefit of the doubt.
Once I was trying to find info on my server’s administration policies and including time it. Turns out it wasn’t available in my app at the time, I had to go to the website.

all 48 comments