wombarly
I pay €14/mo to not have ads on YouTube. It's good they have the skip feature for those sponsor segments, since they're just embedded ads.
Creators still benefit as my view has a higher $. Well... not anymore I suppose with the view attribution endpoint being blocked by my adblock.
A basically permanent ID. Unified ID2 is one version of this.
The 3rd party cookie ban and heavy pushback against alternative solutions suggested by Google just pushed advertisers into going an even worse route privacy wise.
Almost all of ad tech is moving towards identifiers like hashed normalized emails (e.g. removing +'s from gmail), phone numbers, names, etc. for personalized ads.
iDEAL is the payment system in the Netherlands. And they use ideal.ing.nl for it.
So if you write to the same file twice, one write will succeed before the other and change the etag of the file, which should in theory cause the other request to R2 to fail because the etag you send with as conditional no longer matches.
Ofc its a different matter if you write to the same key in the same file. But that could be solved with special method that allows you to do a setOrUpdate on a key in the json and when retrying the update method is executed again (allowing you to do increments or add a new item to an array) while guaranteeing consistency.
Most people either don't care or everyone around them only uses WhatsApp for chat making it difficult to switch.
https://mijn.overheid.nl/.well-known/security.txt
which redirects to the second one.
https://www.rijkswaterstaat.nl/nieuws/archief/2023/04/hoger-...
Not really. The only actual competitor to GA is Matomo Analytics, the rest are just copies of each other with the same very basic feature set.
There was also a leak of one of Ubisoft's games, not sure about source code.
If they attack a dynamic page, check if you can cache them for 30 or 60 seconds. Pretty close to real time.
If you have cookie based authentication for those pages, its going to be difficult to cache them at all though. Which is where SPAs come in useful since auth is client side.
The biggest thing we do to help ourselves when we're under attack is making sure that the pages being ddosed (homepage, etc) is being cached by them. There will always be some requests that CF doesnt block, so the cache ensures they get served by them.
Besides its not like we're not paying them anything, our monthly bill with them is $1k+
120TB of that is our CDN backed by a Cloud provider, we had to only pay them for 3TB in bandwidth charges.
During peak traffic they serve 35% of our pages because of their cache, with some site improvements we will be able to up that to 60% soon.
Edit: I must add that we are on the Pro plan and do use multiple paid features like Workers and Load Balancers.
Edit: Some numbers, most of them are between 2k-5k requests per second. But we had some with 20k-30k rps.