https://flightaware.com/live/flight/SWR15X

it dropped off that callsign and changed to SWR15X (probably because it went into international airspace)

No one gives a fuck, Salty is on.

Same. Time to hop off cloudflare.

lmao too true

im growing a hunchback from staring down at my phone

I get that.

Good catch, I did not see that... this flight was just airborne though. So that cannot be right... ? What the fuck is going on

CloudFront is AWS' DNS service.

Seems they wanted to off Lin Wood before Parler could close down at midnight.

Un-fucking-believable...

You are right, it's just Lin's...wtf?

she looks like she is about to fall apart.

also, where the FUCK is Gina Haspel? lol

I know, but it wasn't supposed to happen until Midnight eastern.

WHERE I GOTTA SEE!!!!

No, he only needs to announce to disperse. Which he has done.

says the 11 hour old account

deported yourself. good work!

8:61 pm lol

not only that... muzzle flashes, watch closely.

Welcome aboard. Just to let you know. This train has NO breaks. :)

I don't believe so. This is the same update that went out for Test Flight on December 20, and it has no changes to it.

Good eye :D

where does he say watch midway, trying to find it

noooo it just made a hard right to the north... what the heck is with that flight plan lmao

yes lol

Timestamp?

I encourage you to read into Layer 3 routing and packets.

The source IP is your WAN IP always. It carries through. NAT will change your PC's local network IP (192.168.x.x) to your gateway IP in the packet. This identifies YOU. Individually.

No SSL or TSL is needed for that.

DNS forces the traffic to re-route through cloudflare's routers and thus they get the packet data.

If that mother fucker lands at Cheyenne I am going to shit a fucking brick the size of Stacy Abrams

True the source mac ends at the router, my bad, it gets changed to the mac of the WAN for the router. But the IP address source does carry all the way through, which is all that is needed.

They cannot see your user name. That is encrypted with SSL. Just because the SSL terminates and is recreated there, does not mean encryption is broken. It simply gets re-encrypted and both keys are passed to the destination. It is not revealed at the termination point. Only the key to decrypt the new encrypted packets.. are revealed... to the destination.