08 Jul 2026
Slashdot
A Silent Workspace In Claude Mirrors Key Features of Human Consciousness
oumuamua writes: Anthropic researchers have identified an internal activation subspace, J-space, that acts as a functional digital equivalent to the human brain's global workspace. The significance of this discovery lies in demonstrating that Claude's internal architecture satisfies five key cognitive properties of human conscious access -- verbal report, directed modulation, internal reasoning, flexible generalization, and selectivity -- meaning it processes complex, deliberate reasoning within this workspace while routing automatic tasks outside of it. Suppressing this J-space severely degrades Claude's capacity for inference, creative composition, and multi-step logic, while also altering its stream-of-consciousness self-narration. The tool to inspect J-space, Jacobian lens or J-lens, has profound implications for AI safety and alignment auditing, as it allows researchers to read the model's silent, strategic reasoning, detect situational awareness in "blackmail" scenarios, identify hidden malicious dispositions in reward-hacking models, and observe how post-training installs a self-monitoring "point of view." Another way to think of it is as an ocean, reports VentureBeat. "If the mind is an ocean, as the paper's authors write in their opening line, they have spent the last year charting its currents in a system that has no biology, no evolution, and no body -- and found, beneath the surface, a structure that looks unsettlingly like the one we use to think."
Read more of this story at Slashdot.
08 Jul 2026 11:00pm GMT
OSnews
You paid me, a long-time Linux user, to use Windows 11 exclusively for a month: here’s how it went
You all donated en masse to have me use Windows 11 for a month, and so I did. What was it like for a long-time Linux user to go back and experience Windows as it exists now? Is it really as bad as we've collectively made it out to be? Did my month with Windows 11 consist of nothing but pain and misery, or are there good things to say, too? Or, was it an unexpected pleasant surprise? And ultimately, did I stay with Windows 11, or move back to the Linux world? ➡️ Donate through Ko-Fi ➡️ Donate through SEPA transfer* ➡️ Buy merch from our store ➡️ Why a fundraiser? *Name: Thom Holwerda - IBAN: SE08 8000 0820 1684 4657 8414 - BIC: SWEDSESS This year, I'm celebrating the milestone of having posted 20000 stories on OSNews during my 21 years as managing editor of OSNews. This is my full-time job, and since nobody is going to give me any bonuses, stock options, or golden pens, we're running a big fundraiser to keep OSNews going. To add some spice to the whole thing, I added some incentives, with the first being using Windows 11 for a month. We're slowly but steadily approaching the next incentive, too, which is a proper video tour of my office, (unique) computers, and massive devices collection. There's a similar incentive to this Windows 11 one, but for macOS. Yikes. The rules for the Windows 11 incentive are simple: use stock Windows 11 for a month for my computing tasks (with the exception of gaming - converting my Linux gaming PC to Windows just to play the same games seemed silly). I wasn't allowed to use any debloating tools, but as an EU citizen, I do have the ability to remove a ton of Windows stuff thanks to the success of the Digital Markets Act. I also tried to stick to Microsoft's own applications as much as possible, for that true "ecosystem experience", and wasn't allowed to hack my way into a normal local user account. I was all-in. So what was it like? Setting it all up The installation process posed a number of challenges and issues. First and foremost, the Windows 11 installation process is incredibly barebones, and basically assumes no other operating system exists in the world. It has no clue anything other than Windows' filesystems exist, making it dangerously easy to accidentally damage or outright delete any other operating systems you might have installed. My laptop happens to have two M.2 SSDs in, so I could safely dedicate one of them to Windows 11 without interfering with the other SSD with Fedora installed on it, but if you're experimenting with Windows 11 on your Linux machine with just one drive, you might want to reconsider. I also had to perform the first portion of the installation process - the WinPE section - with just my keyboard, since apparently, my trackpad was not supported and did not work at all. Once the system went through its first of what would be many reboots to come and loaded into the phase of the installation where you're actually already running Windows 11, my trackpad came to life, but without any gestures support - so no scrolling. Not a gamebreaker or anything, but definitely annoying. A bigger issue was that the Wi-Fi 7 Intel BE200 chip in my laptop was not supported out of the box by Windows 11. This meant that I had to install these drivers during the installation process, which involves going to the Intel website and finding the correct drivers to use. To make this process more obtuse and less intuitive, you can't use the normal driver installer; you have to specifically opt for the "Intel® PROSet/Wireless Software and Wi-Fi Drivers for IT Administrators", download the ZIP, unpack it on a different computer, put the unpacked drivers on a USB stick, and point the Windows 11 installer to this USB stick. Mind you, the BE200 chip was launched almost three years ago, and there's no excuse for Windows 11 not supporting this chip out of the box - like Linux does. The remainder of the installation process involved dodging a lot of tracking and telemetry prompts, reboots, a lot of waiting, setting up the dreaded online account, waiting some more, and then finally ending up at the desktop. I then set out to enjoy my EU privileges by removing whatever applications I didn't need and turning off features I didn't want, as well as making sure all the drivers were up to date. This mostly involved installing the Intel Driver & Support Assistant and the Intel graphics drivers. Curiously, this is where I hit a returning issue: after installing the Intel GPU drivers for the first time, as well as afterevery subsequent update, the screen would go black and stay that way, forcing a reboot. Windows' graphics stack is supposed to be able to gracefully handle driver updates, but clearly, some bug or problem was preventing the updated Intel driver from being reinitialised. Once those initial setup tasks were behind me, I experienced two more problems. First, sleep/wake was entirely broken and simply did not work. It turns out Windows 11 really doesn't like S3 sleep, and I had to specifically go into my laptop's Dasharo Coreboot firmware to switch to S0ix get sleep/wake to work on Windows 11. Windows defaults to something it calls "Modern Standby", which requires the S0ix state to be enabled. You can also disable Modern Standby which would presumably make sleep/wake work with S3 (?), but this is a whole ordeal and clearly not something Microsoft wants you to do. Of course, the correct way of handling this would be for Windows 11 to adapt its sleep/wake settings to what the firmware reports, but alas. Another problem were the laptop's cooling fans seemingly leading lives of their own, spinning up loudly at entirely random times, irrespective of use. It was so bad and loud I
08 Jul 2026 10:27pm GMT
The state of accessibility in GNOME
With July being Disability Pride Month, GNOME's Sophie Herold published a blog post taking stock of where GNOME stands on this front, progress that's been made, as well as areas where the project comes short. One particular paragraph from her introduction really hits the nail on the head about accessibility discussions in tech circles: The reality of tech communities is that they are often ableist and elitist. Probably more so than the average population. If a user or contributor struggles with a tool, blame is shifted to a "skill issue," if an interface is simplified to make it accessible to more people, it's "dumbed down". Assistive technologies are often developed by abled people, without involving and paying disabled people. This also leads to an attitude where contributors expect gratefulness from disabled people for providing them with the most basic needs. All these issues are also not absent from the GNOME community. ↫ Sophie Herold Even as someone who isn't disabled and doesn't use any tools classically shelved under the "accessibility" moniker, I encounter the attitudes she mentions in the quoted paragraph basically every day. While we can have normal, productive discussions and differences of opinion about accessibility - for instance, I strongly believe robust theming support is absolutely crucial to accessibility, while the wider GNOME community does not - the dismissive attitudes towards people with accessibility needs in the software world is shameful. Even if you don't have accessibility needs today, you will definitely be needing them at some point in your life. If accessibility isn't one of the first words you jot down on your mood board or whatever when you start a new software project, you've already done millions of people a massive disservice. Get educated, learn what you can about accessibility, listen to people with accessibility needs, and make your software better for everyone. You'll thank yourself one day.
08 Jul 2026 10:23pm GMT
Next release of Cinnamon finally supports Wayland
Linux Mint's Cinnamon is one of the last desktops to still not support Wayland, and is relegated to only being compatible with legacy X11 environments. With the next release of Cinnamon, however, this is finally going to change. We worked really hard on Wayland and we got to the point where it feels solid and the experience is almost on par with X11. Wayland support will no longer be considered "experimental". In the next version of Cinnamon, both X11 and Wayland will be fully supported. ↫ Clement Lefebvre on the Linux Mint blog The next release of Cinnamon, version 6.8, will be part of the next release of Linux Mint, scheduled for Christmas of this year.
08 Jul 2026 10:07pm GMT
Slashdot
John Deere Agrees To 10-Year Right-To-Repair Deal In FTC Antitrust Lawsuit
John Deere has agreed to a 10-year FTC-supervised right-to-repair settlement requiring it to provide farmers and independent repair shops with the same repair resources available to authorized dealers. The deal resolves antitrust claims from the FTC and five states alleging Deere monopolized equipment repair services, contributing to higher costs and delays for farmers. Wired reports: The full statement (PDF) lays out obligations for John Deere's repair services, requiring the company to give farmers and third-party repair shops access to the same equipment and repair resources it provides to official John Deere dealers. This includes software capabilities, such as reading and resetting codes and pairing with other software, which customers have long had limited access to, creating delays when diagnosing equipment problems. Delayed fixes can mean delayed harvests, which many farmers saw as a fundamental threat to their livelihoods. Under the agreement, John Deere will be required to provide this level of access, equipment, and services for the next 10 years, monitored by the FTC. [...] John Deere has maintained that it already has robust repair resources for its customers, including service manuals and diagnostic equipment. In John Deere's press release, the company says the settlement is in line with what it has been doing all along, saying that "the agreement reinforces Deere's continued innovation toward more flexible repair options, emphasizing increased access and transparency for customers. It formalizes Deere's ongoing commitment to expanding access to diagnostic and repair tools."
Read more of this story at Slashdot.
08 Jul 2026 10:00pm GMT
Ars Technica
Suspecting AI cheating, Ivy League prof ordered an in-person final; scores fell 50%
AI cheating leads to "a failed society," professor says.
08 Jul 2026 9:42pm GMT
Slashdot
Meta's Glasses Will Turn Off the Camera If You Tamper With the Privacy Light
Meta is rolling out an update that will disable the camera on its smart glasses if the device detects that someone has tampered with or destroyed the privacy LED. "The update is meant to address modders who have taken actions such as physically drilling into the LED light," reports The Verge. "Meta has previously tried to discourage tampering with the LED light. For example, starting with its second generation glasses, blocking the light with tape or other objects will trigger a prompt asking users to uncover the recording light. However, many modders have found various workarounds for that particular measure."
Read more of this story at Slashdot.
08 Jul 2026 9:00pm GMT
Ars Technica
Lawsuit: Man used Grok to make 7K sex images of stepdaughter, then shot himself
More young girls sue X over Grok CSAM; X accused of shielding child predators.
08 Jul 2026 7:56pm GMT
Judge rejects Kalshi attempt to override New York state gambling laws
Kalshi tried to ignore gambling laws on its prediction market, NY governor says.
08 Jul 2026 7:14pm GMT
01 Jun 2026
Planet Arch Linux
Today is my first day at JetBrains
Good morning from JetBrains Berlin office!
01 Jun 2026 12:00am GMT
11 May 2026
Planet Arch Linux
Ratty: A terminal emulator with inline 3D graphics
Just trying to answer one simple question: What if the terminal was 3D?
11 May 2026 12:00am GMT
18 Apr 2026
Planet Arch Linux
Break the loop, move to Berlin
Break the pattern today or the loop will repeat tomorrow.
18 Apr 2026 12:00am GMT