I don't want AI. I am preparing for a jump (back) to Linux. "Choice" disappeared, and yes, I know about the "fix" [0]
Maybe this idea may be foreign to many, but personal computers were something I built from bags of parts socketed and/or soldered onto S-100 cards, and that experience was the foundation of most of my career.
I was a Henry Higgins, and proud of my Eliza(s). While I get along cooperatively with Eliza (the happy ending to "My Fair Computer") I don't want Eliza to be my caretaker. This morphing of computers and internet into nannies and caretakers is IMO reverting to the "good old days" of servants. While some inventions are truly liberating (ask the guy who missed his Mom at an airport and freaked out for hours until she showed up at my home, courtesy of a cab or bus) how many are just replacing people with machines?
I could seriously use some friendship of the human variety, rather than a humanoid in a box (or an especially nice robot as in "I Sing the Body Electric" by Ray Bradbury, memorable on The Twilight Zone) Try being older and living alone, typing away.
I don't even use GPS any more, since I trashed Apple Maps when they kissed the Emperor's big fanny.
> A pilot phase with 38 ministry employees kicked off last year to trial Collabora's suite with Office documents. However, this trial was terminated when elections took place earlier this year. A spokesperson confirmed that the experiment had concluded, and would not resume again. They also confirmed that no evaluation benchmarking Collabora's performance against Microsoft Office had taken place either.
I read the article on "The Signal Chats That Cost OpenAI Researchers Their Jobs" [0] and the (former) employees were asked for their phone password.
Accessing Signal, OpenAI discovered (the absence of) disappearing messages to an external researcher.
So, if an application is password protected either by the OS or another app which demands a password to launch another app, would the official just ask for the application's launch password, or is that beyond whatever overly generous powers granted to them? Perhaps this is rhetorical, because what we called laws are merely ignored these days.
Laws for which there is no charge, no prosecution, and no consequence (I can give 34 examples) are merely suggestions.
CBP believes it has the right to files saved locally on your device itself. However explicitly cloud-hosted data (that is not stored on the device) is supposed to be off-limits, as I understand it.
And keep in mind that American citizens cannot be denied entry to the country for refusing to unlock or hand over their devices. They might hold you for a little while, but they cannot stop you.
People are getting arrested for all sorts of excuses. The Cop City protestor with the GrapheneOS phone was detained for "a routine search for child porn" - not something they routinely search for, and some people think they were going to plant some if they could get into the phone.
They have also arrested citizens simply for driving in their own car proximate to an ICE kidnapping. But if we preemptively act like we have no rights then they've already won.
Isn't this just giving in if your only reasonable backup location is a US cloud that regularly has to negotiate with the US federal government. The only difference I see is that they have to resort to parallel construction.
> Isn't this just giving in if your only reasonable backup location is a US cloud
my backups are not in a US Cloud.
Contacts and calendar on self hosted carddav
Pictures and files on self hosted drive.
Deltachat on mail servers (non us hosted provider) and XMPP conversation backups.
I don't backup whatsapp automatically, only do manual exports once in a while of important conversations that get copied to my self hosted server. Whatsapp pictures and vids are automatically synched with syncthing.
I host encrypted backups for another tech savy relative on a server of mine and in exchange he also host space for me on his own local backup server. We are 2000km appart so it allows us to keep a safe backup in remote location in case of fire or natural disaster without relying on the cloud.
Only thing I have missing is an automatic backup test of random files to compare checksums. I have done test backups manually but last was a bit more than a year ago so it is time to run a new one and add this automation as well.
That's quite an approach, thanks for sharing. I still don't think it mitigates restoring within the US since they claim to have search rights within 100 miles of any international airport. Personally, I try not to fall into the trap of believing I need retention of data that doesn't fall into a few categories, most of which I would assume I will already be sharing with authorities through taxes, etc.
Musk is a naturalized immigrant. What if Democrats started behaving like the current administration and de-naturalizing selected people? (I doubt that they would.)
Forget the artwork and check out the accompanying song and lyrics for the new release.
I think it's one of the funnier ones so far.
https://www.openbsd.org/lyrics.html#80
To me that cringiness is oh so wonderful. Everyone is so weirdly afraid of their image, of how others think of them.
We've become sterile; caricatures of ourselves so that we can adhere to the groupthink. It's refreshing to see people unashamed to be themselves, with all of their weird parts.
Alles touristen und non-technischen looken peepers! Das computermachine ist nicht fuer gefingerpoken und mittengrabben. Ist easy schnappen der springenwerk, blowenfusen und poppencorken mit spitzensparken. Ist nicht fuer gewerken bei das dumpkopfen. Das rubbernecken sichtseeren keepen das cotten-pickenen hans in das pockets muss;
I can't see why; it's a goofy 20th-century colloquialism popularized by Bugs Bunny cartoons as a substitute "damn". I sincerely doubt the original author meant anything else.
You can't see how using "cotton-picking hands" as a negative term can cause backlash? If the phrase was something like "don't break anything in this cotton-picking rack", I would understand, but "keep your cotton-picking hands away"?
I'm not a native speaker, so I might have genuinely missed something here. Still, if I had this warning printed on my cubicle I would be fearing for my job everyday.
You are not supposed to, it is intended to represent(and probably is) a machine generated image.
I have not really formalized my thoughts on the matter, but it boils down to. It feels great to get the machine to generate a thing for you but it feels terrible to receive a thing from somebody that is machine generated.
The worse part is the paranoia, Now I am seeing "tells" of machine generated content, and it may or may not be. But I have already lost interest.
The real irony would be that it is a hand drawn image carefully animated to feel machine generated.
I mainly don't like the self-destructive aspect. Even if it's a spoof.
Especially when I see all the self-destructive goings-on in the world, based on senselessly divisive beliefs or just the power-seeking that generates them to divide and conquer.
I once met Ken Bering, "The Wheelchair Guy" whose foundation provided wheelchairs for people who could not afford them. The wheels weren't spiked, nor were they like a Seinfeld episode, where George donates a cheap wheelchair with poor brakes that sends its occupant down a steep hill.
> I am not on board with the graphic, whatever the heck it is.
They are purposefully iconoclast with whatever aesthetics are "socially acceptable" for mainstream nerds. For example, their use of comic-sans in official presentations. Here they use ridiculous slop in front of an audience of conservative unix hackers. You can find it funny with the right mindset.
The upgrade mechanism from 7.9 to 8.0 is still gloriously simple, and exactly the same as it has been for many years :
ssh myopenbsdbox # log-in to your machine
doas sysupgrade # will log you out, go drink some coffee
ssh myopenbsdbox # log-in to the upgraded machine
doas sysmerge # (optional) solve merge conflicts of your cfg files
doas pkg_add -u # (optional) upgrade local packages
> What window managers is everyone running? I’m thinking i3 or dwm
everyone is running different managers... I use evilwm on linux and cwm on openbsd. They are very similar (keyboard-driven, floating windows with no frames) with different default keybindings.
The best place to go for curated patches is here. You can customize these or roll your own once you have a chance to examine the source code. dwm is very simple.
The false distinction between the OS packages and user local (/usr/local) packages during upgrade causes much unneeded complexity. FreeBSD is making this go away which is welcome.
For a rolling release like Arch Linux you just always use pacman -Syu.
But yes you are correct, if you want to upgrade a Ubuntu distribution like 26.04 you do need to issue a command like `sudo apt dist-upgrade` which is admittedly an additional command. But then you could run 26.04 for many years. In OpenBSD anytime the base system/kernel is upgraded for a security fix or point release you need to do a slightly more complex dance.
The correct form is `apt-get dist-upgrade` but that's just the command to update all packages to the latest versions in the same release of the OS. It is the equivalent of `apt full-upgrade` if you have the more modern `apt` command rather than `apt-get`.
So, no, that will not upgrade your distro.
The recommended course of action for Debian is to edit the repository config files, change to the new release names, and then do a full update.
Arch upgrades are really fun if you don't run pacman for a year or more. It rarely works in your favor to not run pacman on a extremely frequent schedule.
I don’t think the theme is “anti‐AI.” I think what it’s trying to express is something along the lines of “take responsibility for your code,” where one’s code is the code one unleashes upon the world.
Even Xen (VM used by Qubes) periodically has CVEs, although they don’t always affect Qubes due to additional layers of defense and/or limited hardware targets.
CPU flaws are even more daunting. OpenBSD's BDFL, Theo De Rhaadt, had what some called harsh but accurate words for Intel CPUs when Meltdown was uncovered.
Rhaadt and Stallman have something in common in that they have been vindicated in near biblical proportions, often far long after presenting their stance and having been casually derided for it.
There is today still no real mitigation for the side channel flaws collectively named Spectre flaws. A look at Jonathan Perry's work, adjacent to the side channel stuff, tells us that most modern CPUs still not end of life today are truly single-tenant.
When reading AWS' writing on side channel flaws, someone who skims that writing will leave with a different conclusion than someone who reads what AWS has shared in its entirety and reads it slowly.
The only truly effective way to isolate applications effectively, in a way accessible to people in average financial stature, is to put them on different CPUs (hello dual and quad socket server boards). Thanks to the prevalence of inexpensive ARM and Risc-V based single board computers, although this requires advanced skills with operating systems and relevant tooling this is practicable (as ugly as it is).
There are some new general purpose processors made from ISA that don't use any form of speculative execution. These may be undoing decades of bad-assumptions cruft. Those who deserve these processors won't wait for retail channels to deliver them.
I won't give up agency in life.
reply