1,008 karma · joined May 26, 2009
I haven't used Chrome since this rolled out, since I didn't see a way to object to the new tracking. This is what the linked article [0] says:
> It’s unclear if toggling these features off will stop Chrome from collecting these data altogether, or if it just won’t share the data with advertisers.
[0] https://theconversation.com/google-chrome-just-rolled-out-a-...
[1] https://developer.chrome.com/en/blog/shipping-privacy-sandbo...
Here is a reference for the userChrome.css to hide the default tabs. https://news.ycombinator.com/item?id=23268077
What about gmail? That has all the state server side. How impressive would it be if all rendering was done server side?
Answer: don’t show anymore than three history suggestion items and provide no way to increase it
For one application I used a base 58 encoded value. Part of it was a truncated hmac, which I used like check digits. This meant I could validate IDs before hitting the DB. As an attacker or script kiddie could otherwise try a resource exhaustion attack.
So in the age of public internet faceing APIs and app urls, I think built in optional check digit support is a good idea.
https://aws.amazon.com/blogs/hpc/in-the-search-for-performan...
Where AWS explain why TVP isn’t good enough for them and why they are developing a replacement.
A colleague of mine went diving through the JavaScript source and found a reference to an ActiveX component called XMLHttpRequest. We realised it was pretty useful and ended up using it to build an SPA that approximated a spreadsheet for global logistics planning. It worked very for 2003 standards.
Google maps came in 2005
According to this benchmark [1] zstd does not drop its decompression speed as the compression ratio increases. It stays about the same level.
[1] https://www.truenas.com/community/threads/zstd-speed-ratio-b...
I would say the decentralised features of git work for me. And they are no overblown.
If supply and demand is just a convention, they what are the alternatives?
I guess I’m ignorant, but central planning is the only one I can think of.
But this is not to say that I disagree about regulation. It would be nice if we could limit the depth of the transitive tree of contracts. But I doubt that is feasible.
However Mark Russinovich, CTO of Azure did say that it's time to drop C and C++
https://twitter.com/markrussinovich/status/15719951172335042...
Our requirements were quite unique and so writing custom code but aligning to an OIDC style flow was a good choice for us.
In the end it was a good choice and much easier than forcing an auth framework to do something it wasn’t designed to do.