

There’s an Australian Canadian co-production that goes into some of the atrocities the British got into:
Anything and everything Amateur Radio and beyond. Heavily into Open Source and SDR, working on a multi band monitor and transmitter.
#geek #nerd #hamradio VK6FLAB #podcaster #australia #ITProfessional #voiceover #opentowork
There’s an Australian Canadian co-production that goes into some of the atrocities the British got into:
There’s a whole range of cli tools to extract and query structured data like that, but you might consider loading it into something like sqlite3 and treating it as a database because those formats are really not intended for queries, they’re designed for sharing data.
For some workloads it’s true that you can do the heavy lifting on a more powerful remote machine and transport the results back to an endpoint device like a phone. Websites are a good relatable example of that, as are services like YouTube.
It’s not universally applicable for many activities that computers are involved with, data analysis, record keeping, simulations and a myriad of other processes.
Blurring of the lines between these different orders of magnitude is made possible by faster and faster networks, but that’s physically not able to beat processing done inside a single device.
The more powerful we make computers, the more complex problems we use them for. I suspect that this is unlikely to change as computers evolve.
One of the fundamental differences between phones, laptops, desktops, and beyond is size. While that sounds obvious, it also means that the amount of processing within the device is constrained by that size.
The constraints relate to how much energy can be used by each device and more importantly, how much cooling is available for the system.
It means that there’s a physical limit on how much work each device can do without being unusable.
While miniaturization is a factor, it’s not linear and you can only get so small before you fail.
So, depending on what you want to do in any given time, the device you use will dictate what’s physically possible.
This is a lesson that the religious fundamentalists currently running the USA have weaponised.
A search engine?
I work in ICT. Leaving Gmail is much easier said than done. It has the best spam filtering bar none and integrates with a whole host of other services that I use daily, like the mobile phone I’m writing this on for example, the one that integrates my calendar, tasks, contacts, photos, websites, YouTube channel, spreadsheets and, oh yeah … that other thing … Gmail.
So, if wishing made it so.
What I’d like is a Google Workspace tier that is entirely without AI.
With?
I run projects inside Docker on a VM away from important data. It allows me to test and restrict access to specific things of my choosing.
It works well for me.
Oh … you’re a dick … thanks for self identifying.
I’m guessing that being gay doesn’t turn off the part that’s looking for a beautiful mate.
I’m pretty sure that it boils down to successful procreation genetics. As in, the more attractive you are the bigger the selection of mates you have access to. It’s been happening for as long as life has existed here.
No doubt this has across history been heavily distorted by culture, art and religion and in more recent times by fashion, marketing, advertising and media.
Further down the article it talks about why it’s that colour.
What’s even more remarkable is that someone actually did that, in January 1998.
So … hot air doesn’t float … that’s a thesis right there.
Before you start consolidating, consider what might happen if the switch is in an unexpected state. For example, someone turned off the heater or pump and you were expecting it to be on.
In other words, you need to consider what a “safe state” is for each thing and how your code, when it fails, reverts to that state. This is an example of “failsafe”.
Note that I said “when it fails”. This is true for all software, even on mission critical systems.
Source: I write software for a living.
There’s a reason why there’s only privileged write access to /dev/sda.
If you run unknown software as root on any computer you get to experience first hand the impact of: “fuck around and find out”.
This article doesn’t at all explain what actually happens. There’s a hand wavey description including PowerShell scripts and the clipboard, but it doesn’t indicate how the code gets executed.
The article talks about a complex and sophisticated attack, but I don’t see any evidence of that assertion.
Also, given that it’s talking about PowerShell, I’m going to guess that this affects Windows only.
Finally, there’s no source links, no CVE allocation, no indication what the URL looks like.
I’m going with deep scepticism about this report unless more information comes to hand.