Beyond all the issues with third party JavaScript inclusion on sites blowing up their security perimeter, there are also significant issues with the link tracking for these as they nest and re-encode their values so much in the URLs any reasonable firewall concludes that they're some kind of obfuscation attack.
Usually they don't, they just need to fire an event with the analytics properties from the link and whatever persistent identities are available on the client side (device ID, fingerprint etc.), and then keep firing new events with at least one of those identities. The link URL or query string will have the user's canonical identities in it already.
When IDs don't persist across domains or subdomains there are also plenty of methods that don't involve passing via URL or tripping reasonable network security, and that work for >99% of user clients.
+1 for Blacksmith. You need to have a Github org to use it as it won't work on personal accounts, but it feels like a magic want that just makes runners 2x as fast.
I have it for all my stuff (dozens of repos and hundreds of PRs/builds per week) and it's only once in the last year that I've exceeded the free resource levels. I don't know if it's just extra capacity or they're burning VC dollars in the hopes of inspiring posts like this, but either way I feel like I'm taking advantage of them at this point.
I saw video of a costume contest this year where one participant was wearing an Amazon delivery driver vest, flung a cardboard box across the stage and then took a picture of it (all to wild applause).
Quit being overly pedantic about how contrived the example is and struggle with the underlying fact that the compression type is negotiated between the client and server. If the compression happens on the HTTP request (as some of the comments here suggest), then the server must use that compression method or it fails to read the body of the request.
Lots of apps will, for example, bring in your Google avatar (i.e. they fetch its URL for ingestion) as a default avatar if you use them for SSO. Slack included, IIRC.
Even air conditioners have improved as we've moved away from having multiple leaky window air conditioners to mini-splits and central (though I would still think that's an increase in overall energy use).
reply