1ncorrect
It’s no different to religions or economics.
‘AI’ doesn’t exist, and LLMs have vanishingly narrow legitimate justifiable use cases. Any output from one is intrinsically, explosively, imprecise, and can’t be trusted to be build upon without specialist treatment. I’m yet to identify any application of a LLM which can rationally be mistaken for intelligence.
Anyone who persists in referring to LLMs as ‘AI’ is either betraying they don’t understand what they’re talking about, or they’re invested too deeply in an active grift.
https://en.wikipedia.org/wiki/Content-addressable_memory#Ter...
open -a <GUI Application> <File>
Handy for distinguishing between editing and consuming media.
The only way I’m currently able to deliver anything to domains hosted by Microsoft is to expand my SPF record to include my ISP’s mail hosts, and route delivery through them.
Microsoft, and the other SMTP cartel thugs, are undermining the protections these protocols were designed to provide.
I’ve had to relax my SPF record to include the entire mail pool of my ISP to be able to send to anything hosted by Microsoft. I tried to liaise with them directly, and through Linode, but they refused to exclude the IP from their opaque blocklist. Their proposed solution was to change the IP of the VPS, but that’s just agreeing to play whack-a-mole with a bad faith actor.
There should be a path to greater transparency and accountability from the SMTP cartels, but I’m at a loss as to how that can manifest.
The merchant receives the same ‘random’ card number for transactions from the same device.
Of course, all of this needs to be included in a broader discussion around myriad vectors of tracking and fingerprinting to arrive at a meaningful conclusion.
A notable flow on effect is both of these products had helped with the management and improvement of my health, and these changes have had a measurable negative impact since I’ve been unable to use them.
Other examples are: Wahoo, who locked the control of their products behind an account and login requirement for devices which had been working perfectly fine for years prior.
Roche, who killed their blood glucose app at the start of 2023 and forced all their users to move to a third party app, developed by one of their subsidiaries, which requires you to accept a data exfiltration clause, if they wish to continue the automagic on-device logging.
[0] https://en.wikipedia.org/wiki/Carrier-sense_multiple_access_... [1] https://en.wikipedia.org/wiki/Carrier-sense_multiple_access_...
In summer, you could decouple it and use standard separate heat dissipation mechanisms.
The simplest example would be a heat pump with its own built in UPS style battery, but I also see it being built with coupling to a power wall style house battery.
Notable examples for myself are Wahoo Fitness[1], Water Rower[2] and Roche’s Accu-Chek[3], which all now require logins and agreements to leak health data to be hosted on external services in order to continue using the products I purchased from them.
In Roche’s case, they gave barely 5 weeks notice that their apps will cease to function at the end of the year, locking all data and functionality on January 1, and punting all responsibility to their subsidiary, mySugr[4].
[1] wahoofitness.com [2] waterrower.com [3] accu-chek.com [4] mysugr.com
Any charity which fails to prioritise putting itself out of business is functionally a grift.
If society truly valued what charities do, their activities would be intrinsically valuable, and not require a special economic status to be conjured for them to be viable.
I don’t want to develop my sociopathy to the level required to be mistaken for acceptable in what passes for society today.
It indiscriminately pollutes the environment, and inflicts harm on non participants by incentivising unbridled data collection.
Some locations I’ve had to create additional bespoke SSIDs for a specific band, but it’s only because the customer has explicitly requested it because they think it matters.
Multiple addresses/prefixes are a required component for IPv6 to function, which I suspect is often the biggest source of misunderstanding from legacy IP competency.
If you need a stable prefix for a host, use a ULA or your own GUA. If you need to provide services from 2 or more upstream networks, configure the host with addresses from each of the delegated prefixes from those networks. If you need to do all of the above, there’s nothing preventing you from configuring them all simultaneously. You can even use the IP and routing stack to provide selective service access and trust thresholds.
Prefix mobility is something that should have been anticipated when IPv6 was being hashed out, and would have made many things much easier, but it’s far from critical, and gives IPvA an easy killer use case.
They’re functionally indistinguishable, with mythology replaced by mathematics, and God replaced with GDP. Similarly, they’re both arbitrary rules; conjured, imposed, and protected from scrutiny by the ruling class.
That’s not to say it’s not useful, but I find it baffling that an imaginary concept is unquestionably granted veto over tangible and visceral phenomena.