The WIPE/privacy extension developer is using a pre-existing(hard-coded or generated) fingerprint to “mask” the user from meta .

Meta implemented a quality of life feature powered by the ability to set cookies and track you across the web of course and help users with forgotten accounts to unify them - but not a security issue you cannot do anything unless you are proving access governed by standard auth protocols ; the extension developer’s hack to mask created a broken experience because of the reused IDs.

Adblockers can create unintended effects , it is hard to reverse engineer complex platforms like meta and also hard to keep up to date with billion dollar companies code updates by small indie teams of volunteers ; doesn’t mean we shouldn’t use them, just be aware that it may happen when enabled

Last year Github said they are giving away 11.5B action minutes [1] for public repos for free, that translates to about ~30,000 cores . The explosion in commits, pull requests and action minutes that Vlad the CTO mentioned[2] in the August postmortem is approximately 10x and he also highlighted they added 3 Million cores to their fleet.

Assuming a similar 10X growth in open source; total public repo compute budget is only 10% of the new compute they have added. Only half of Github is on Azure as of April, and Azure itself is much much larger.

Last year numbers were worth $180 Million going by list prices of action minutes [3]. However that would be only $20-30M equivalent typical outlay for a mid-size tech company if they were actually buying 30,000 cores on the cloud ; and definitely much cheaper for Azure's procurement ;

It is a good PR strategy and very good deal for Open Source but is really only a small customer acquisition line item for them and doesn't likely meaningfully impact their compute issues one way or other.

[1] https://github.com/resources/insights/2026-pricing-changes-f...

[2] https://github.blog/news-insights/company-news/the-august-17...

[3] Action minutes are priced more expensive than even buying on-demand compute on the cloud including with Azure;

There are also third party providers of IP annotations to classify known VPN address ranges that content providers typically subscribe to blanket block providers.

The reason for this aggressive approach is streaming apps all need your IP as core signal for tagging your region and all content licensing is region locked (even on YT).

Netflix are/were the most relaxed about it , and for long time would only buy content if they got global distribution rights, but not anymore. Many VPN ads specifically used to market that you can watch Netflix geolocked content.

[1] IME they block DC IPs too although not needed for blocking professional VPN, even self hosted OpenVPN on cloud box usually gets flagged.

Sub-agents not sharing context is a useful design-pattern when you want adversarial or independent reviews.

Cache reads could be shared between sub-agents, A single node(8GPU cluster) supports few hundred concurrent user sessions, that all share the same KV cache memory, so it is likely model providers do colocate your sub-agents in one node, it is more efficient , but may not be guaranteed so performance could vary; like we have with elastic compute and storage[1]

This can be cheaper depending on your coding flow i.e. cache hit % and the billing plan - cache reads are basically free or charged very little in subscription plans.

[1] Modern AWS does offer collocation at additional costs for compute but that is not the default and most other clouds do not offer it

Middle East runs on poor people from the subcontinent and Africa.

Hong Kong depends on live-in foreign labor who have to camp out in public spaces on their day-off.

America is built on poorer labor of every kind - enslaved African cotton farmers , indentured Chinese railway workers, famine stricken Irish, or more recently Latin American or H1B Indians in tech.

Some countries try to attract the richest percent like New Zealand, however it is not economically meaningful nor is major portion of immigrants globally or within their countries even.

Countries may not like foreign poor immigrants, but they certainly need them to work harder for less pay and rights.

Nobody is saying nuclear is cheap it is not - we will be building a plant once in while for pure strategic reason no matter the cost anyway. The point is construction cost comes down per MW with higher frequency of plant building, and this is the case SMRs, we can get cheaper construction both Per MW and overall TCO in absolute dollar terms relative to large plants with SMRs.

Flameville 3 is the first reactor for France in 21st century and suffers the frequency problem I am arguing. It was a path finder therefore only one was ever ordered. EPR2 is 6 under construction and France does have a track record of doing it consistently at scale for cheap(by nuclear standards).

The Asian giants all do it for cheaper because they build regularly, Japan (post Fukushima policy direction notwithstanding) and South Korea achieve overnight numbers of $5-6M/MW or less, so does China.

Regular construction is key, to the industry having a chance, without SMR that is never realistic anymore.

AP1000 (reactor as Vogtle 3/4) in Taishan is estimated to cost $4M-6M /MW compared to $15M/MW+ at Vogtle. if Chinese safety standards seem lax, South Korea does regularly reactors at $4-6M/MW range.

Even Flameville 3 in France was significantly cheaper than Hinkley point C (same reactor type), which infamously required some quite ineffective Fish speakers. The EPR2 series (6 reactors) in France is expected to cost considerably less than Flameville did.

Key to cheap nuclear - SMR or otherwise is regular construction. SMR makes regular construction more likely as each plant is not a $10-20B+ capex that is a tough sell to tax payers particularly when it inevitably overruns, SMR also potentially have a bit less regulatory hoops to jump through due to their smaller size.

Not sure how that would work with building say a docker image, reproducible builds are pretty hard problem to solve, and caching intermediate layers is not always simple or even doable, we typically still need to publish to a registry which is not the cache server.

[1] https://googleappengine.blogspot.com/2008/04/introducing-goo...

The final asset/artifact is rarely small either. even best optimized artifacts can be few hundred MB docker image or more commonly multiple image layers running GBs in size .

each step is a network pull then recompute cache if stale and keep going till end .

Even fully cached outputs needs to fetched and read from a remote server[1]. A step n-1 outout fetched from remote cache server need to written to disk and then again read by step n[3] - all disk I/O and network bound operations.

10s may be achievable/realistic goal in the Java/C++ world where Bazel normally seen. In TS eco-system most people would be over the moon to get into ballpark of 1-2m for a decently large monorepo.

We should define Build more clearly here, if you mean running just transpile/compile steps or the full series of steps that includes tests (as the linear post here is talking about). It is hard to see even a small sub-set of a large suite of test that require a virtual DOM or a real browser can run in 10s or less.

[1] Typical for say managed CI setup .

[3] Common run-of-the-mill frontend + backend stacks in different languages etc.

We don’t complain about switch cases in code when there is two or three switches we start refactoring once it starts to proliferate.

The law is no different , passing a wider ban would not get the votes easily or quickly and the interested parties the onion industry have no reason to push for it neither does the lawmaker acting on their interests.

If said small markets also had exceptions passed seeing the onion one there could have been case to be broad.

It would premature optimization to otherwise, based on just need for elegance , code or law has to work first even if dirty .

It points to friction rather than cost economics. Same reason we are always surprised why multi billion dollar product companies with millions of install base prefer electron instead of a native app.