According to the writeup; there are two methods: it is possible for an extension to mark some parts of itself as 'web accessible'; and linkedin has assembled at least one characteristic file for 6,1000-odd extension IDs and attempts to fetch it to confirm/deny the extension's presence.

The other is based on the fact that the whole point of many extensions is to modify the site in some way; but the site normally has largely unfettered access to inspect itself, so they have theirs set up to walk the entire DOM looking for any references to "chrome-extension://" and snagging the IDs if found.

Not exactly a 'declare installed extensions'; but it looks like, out of some combination of supporting the use cases where an extension and page actively interact by design and either not wanting the possibility or not wanting the complexity of trying to enable 'invisible' edits(presumably some sort of 'shadow' DOM mechanism where as far as the site and everything delivered with it knows only its unedited DOM and resources exist; but the one the user sees is an extension-modified copy of that one, which sounds like it could get messy), inferential attacks are fairly easy and powerful.

Where exactly does supporting 3 people on $133k/year count as 'upper middle class'? You could be doing a lot worse, and many are; but that's not just tons of money in a HCOL area; and that's also lower than twice the median salary for full time employees with bachelor's degrees; so you are calling either a single income household doing a bit better than median or a dual income one doing worse 'upper middle class'; which seems pretty ambitious.

It's hard to train a cow to keep its cellphone charged; so you can see why you need something to keep their tracking collars topped up.

Realistically, the status quo has arguably outrun the dystopia there. Your phone already does far more than anything you could get into the power envelope of a bracelet or embedded chip implant, and if for some reason you've raised enough eyebrows that you'd be hauled in for an RFID read DNA is a pretty indelible identifier.

It's not 100% ironclad; but penetration is broad enough that you've basically got the majority carrying highly fingerprintable RF beacons and the minority standing out for their relative radio silence and attempts to deal in cash. Expensive and uncomfortable ankle trackers are good business and feel nice and punitive, just to remind the wrong sort of people we aren't happy with them; but you don't really need to impose a surveillance society when it will build itself for you.

My (admittedly anecdotal from the totally unscientific sample of random stuff I've had reason to work on) impression is that some 'shared' BMC ports had oddities related to network controller sideband interface speeds, since NC-SI is what the BMC is depending on if the NIC is on someone else's PCIe root. It's not like the BMC actually needs a faster link for much(normal management traffic probably doesn't fill 10mb and mounting virtual media may be literally once-in-a-lifetime) so the actual speed of the NC-SI interface was not a burning priority; but it left things up to the NIC whether it would support remaining at gigabit speeds and just quietly slipping the trickle of shared traffic in(presumably slightly more complex; but seems to be what the newer ones do) or if it would knock the link rate down visibly to simplify the case.

You see little echoes of similar behavior elsewhere. The intel desktop and laptop NICs that support 'vPRO' will be GB or 2.5GB when the system is on; but quietly drop back to 10 or 10/100 when it is off and it's just the management engine listening. Some enterprise vendor USB docks do similar things; looks like a normal USB NIC when the OS is up; but drops to a lower speed and operates quietly over, I think, some sort of oddball vendor-defined messages if one of their systems is plugged in but off.

I assume that, as an exercise, getting 5 simultaneous introductions working makes for a better paper; but is there a reason why you would want that in practice? Especially if there is any wobble in the ratios either randomly, across generations, or in the presence of certain environmental conditions that tweak the plant's metabolism one way or another that sounds like it would be a real pain in the ass to have to re-balance (and, if different patients are deemed to need different combinations even a perfectly stable plant is going to need re-balancing of the outputs) vs. very specifically going for a specific target output per-plant(or e. coli or yeast or whatever is easiest to bioreactor) and then just mixing to taste after purification. Is there some advantage I'm not seeing?

I realize that there are cases where some plant-sourced pharmacological effect looks like it is actually driven not by the identified 'active ingredient'; but by dozens or hundreds of assorted things, and in that case you just have to live with the complexity if you get better results with that than with purified isolates; but if you are deliberately engineering for very specific outputs why a mix of 5?

AI has been running at a big loss to get the users hooked. It was inevitable that prices would start climbing. That process is nowhere near done, running AI is expensive as hell.

Once the market starts reflecting the actual costs, you can bet the cost/benefit will not be nearly as rosy as it looks now. But some customers will already have gotten themselves between a rock and a hard place and will be sucked dry, then discarded. Those "expensive" people that are getting dumped will start looking like a bargain, but they will have already been snapped up by smarter companies by the time management that can't see past their own toes figures that out.

All of this makes me remember a short story reading assignment in the 5th grade. It was about kids growing up in a society where machines did all of the intellectual work. To them, writing was 'squiggles'. They managed to disable a filter on their "bard" (a story teller for children) and had it tell them a tale of machines ruling over Man.

Nobody expects prophesy from a 5th grade reading assignment.

The problem is that the people who could afford this and would do it are exactly the people the rest of society is better off without.

Immunology, presumably.

The only donor bodies that aren't going to treat the transplant as an act of war are clones or heavily immunosuppressed; and it's probably more plausible to assume that you'll be able to clone a human like a sheep than assume that you'll be making some fundamental breakthroughs in immunology to deal more elegantly with unmatched hosts.

I can see the utility of having spare organs in certain emergencies; but how much life extension would you actually get even if the sort of neurosurgery involved in removing a brain and reattaching it to a new host's spinal cord were viable? Is the theory that the assorted ghastly flavors of neurodegeneration are actually to be blamed on older organs and everything will be fine; or is this just a very expensive way to ensure that you skip the various ways peripheral organs can kill you and are assured to be the spryest patient in the dementia ward?

As a counterpoint, The Linux kernel and much of the userspace in various distros is done remote. It can work, even on highly collaborative projects. Like anything, some will enjoy that more than others.

Required physical equipment can be a limiting factor, of course. Though I have done firmware development from home because the dev board wasn't expensive nor is a debugger for that hardware.

There is a nicotine source that isn't at all age locked. I guess the teens will move on to these "cigarettes" you hear about from time to time.

They even come in cool Menthol.

The laws are a joke by people who apparently flunked "Hello World".

They demand a mechanism, but don't even offer guidance on what mechanism it should be. You can technically comply while having no 2 Linux installs following the same API, making it effectively useless.

A better approach would be a purely optional userspace package (perhaps call it "Californication") that returns 1 dword with the age information encoded in it. Each person installing it gets to decide what that encoding will be.

Yes, it returned 0x0BADF00D, that's the code for 18+.

Someone else might decide 0x0B00B1E5 means 18+.

Some early adopters of "Here's a complaint one, pretty please use it" included small operations like PGP. Others were small companies then, later to become large.

Not too long after, there was the whole flap around DeCSS for DVDs. The medium itself is nearly dead now, but it was individual efforts that rendered region coding largely a joke. The Chinese vendors whose DVD players didn't give a damn about region codes came second.