apple.news/A1JRhv3dUTsWcvJiSppcIow
Leave it to the banks to create a shitshow like this. This is why Apple and Google did their own thing.
resource "google_api_gateway_api" "api_gw" {
provider = google-beta
api_id = "my-api"
}
resource "google_api_gateway_gateway" "api_gw" {
provider = google-beta
api_config = google_api_gateway_api_config.api_gw.id
gateway_id = "my-gateway"
}
Am I the only person here that thinks this resource naming is absurd? I should be able to look at these resource names and immediately understand what is going on here. This is nothing but confusion.
I wish I could say this is the only example of this ridiculousness in the Google/Google-beta provider (speaking of, two providers? Really?) but it’s not.
I tend to use Facebook on a web browser so I can use ad blockers to control the experience. Yeah, I know… but Facebook is how I stay in touch with extended family.
Anyway, I noticed this afternoon that Facebook seems to have taken a page from Youtube’s playbook and start messing with ad blockers. I’m using Arc with uBlock Origin and as you can see from the screen recording below, Facebook is trying really hard to circumvent the blocks.
https://old.reddit.com/r/youtube/comments/195octe/youtube_started_slowing_video_buffer_with_adblock/
At some point, Google and YouTube deserve some consequences.
TLS 1.3 is here and ready to go. But a couple of jerks thought breaking it on purpose would be a prudent thing to do. Apparently, they even tried to get NIST to stifle TLS 1.3 to let this broken standard gain traction.
I guess we’ll never learn.