Thanks. I looked into it a bit more and it looks like they actually want to increase what can be done in userland, to reduce the reliance on kernel mode. That’s still a good solution, if things the anti-cheat code needs to do can be moved into userland.

AFAIK Microsoft have plans to block kernel level anti-cheat on Windows. After the CrowdSec issues last year, they’re rethinking which types of programs should even be allowed to run in kernel space.

Edit: I was wrong. They actually want to increase what can be done in user mode, to reduce reliance on kernel mode code.

Thanks for the reply!

preliminary NOVA driver code merged for the future Rust-written open-source NVIDIA kernel driver.

Is this based on the existing open-source driver (https://github.com/NVIDIA/open-gpu-kernel-modules) or will it be entirely new?

Cute. I love it!

Web is a bit easier than native since the browsers handle all the platform-specific details across all common platforms, and you mostly just have to follow some guidelines that aren’t overly technical or arcane. Some examples:

• Use ARIA roles where appropriate
• Ensure sufficient contrast between text and background colours. Should at least meet the WCAG level AA which is a 4.5:1 contrast ratio, but ideally meet AAA which is a 7:1 ratio for body text and a 4.5:1 ratio for headings.
• Ensure you use <label> tags to label for all your <input>s, alt attributes on all images, title attributes where appropriate (e.g. on <table>s to describe the data contained inside the table), etc.

If you use Firefox, its developer tools have an “Accessibility” tab that can audit for common issues - things like missing labels on checkboxes and radio buttons, colours that don’t meet WCAG contrast ratio requirements, etc.

It’s a good time to learn more about building accessible sites and apps given it’s becoming a legal requirement in some jurisdictions. For example, the European Accessibility Act (EAA) goes into effect later this year, and it mandates that sites and mobile apps for various industries (like ecommerce, airlines and other transport, media streaming, social media, banks, and some others) meet accessibility guidelines.

I’m on an all Linux machine and the only accessibility software I know of is Orca and it’s so and so last time I tried it.

It’s probably worth spinning up a Windows VM to test in NVDA. It’s one of the most popular screen readers and probably the most popular open-source one, but only works on Windows since it deeply hooks into the Microsoft Speech API, accessibility APIs, and and other Windows APIs.

This is a really well written article. It’s unfortunate that this person has to deal with all these issues.

I suspect the reason that both MATE and the Debian installer have good accessibility support is because their codebases are quite old. In general, it seems like older software is more likely to have better accessibility support than newer software.

Accessibility should be something that’s built into software from the very beginning, but I totally understand that not all developers have time for it or properly understand it. It’s unfortunate.

Edit: I forgot to mention that accessibility is going to be mandated for some types of sites and apps in the EU thanks to the European Accessibility Act (EAA) coming into effect later this year, which should help somewhat. Won’t really help with Linux itself though.

Same with industrial automation. There’s some robotic arms, assembly lines, etc in use today that still use PCs with ISA slots - the predecessor to PCI, which was the predecessor to PCIe. Old 16-bit bus with a max speed of around 5Mbps. That’s why you’ll occasionally see newish “industrial” motherboards that have ISA slots and parallel ports.

They also often have a lot of the hardware in stock and ready to deploy, to handle replacements.

A project I worked on at university (way back in 2010) was for one of the largest providers of air traffic control systems. Our project was interesting - overlaying eye tracking data from Tobii eye trackers they provided (thousands of dollars each at the time) on top of screen recordings taken via VNC, to aid in training of air traffic controllers.

It was even more interesting to learn about some of their processes, though. Whenever they built an ATC computer system for a client, they’d build one or two spares at the same time, with exactly identical hardware. They did this for two reasons:

1. If the hardware breaks down, they can supply a new system that exactly matches the hardware that was verified.
2. If a client has an issue with their system, they can try and replicate the issue on a clone of that client’s system.

We got to see a storage room with a large number of these systems. Lots of different PCs anywhere from a month to maybe 15 years old. :)

These seem to be the two most commonly supported distros by laptop manufacturers. Framework officially support these two distros, too (they have unofficial guides for a bunch of other distros though)

Wow, a post from 2001 that’s still online today. You don’t see that often any more!

Encryption would prevent it - that’s what I meant :)

I think the trick is to convince someone to send that string, so the modem sees it coming from the computer. Similar to tricking someone into pressing Alt+F4, or Ctrl+Alt+Del twice on Windows 9x (instantly reboots without prompting).

XFree86 was such a tacky name

+++ath0 is a command that tells a dial up modem to disconnect. I’ve never seen it used in IRC this way, but my guess is that the modem would see this coming from the computer and disconnect.

This was back in the days when everything was unencrypted.

Standard riser cable is fine if the cable won’t be exposed to sun (UV) or water. If any of the cable run is exposed to the sun then I’d use outdoor (CMX) rated cable like this: https://a.co/d/gOOUBGW

Cat6 is fine for home use - you really don’t need Cat6A. Cat6 can do 10Gbps up to 55 meters (180 feet) and it’s very rare for residential use cases to require cables longer than that.

When you terminate the cables inside, use keystones. If you have a lot of cables that go to one place, use a patch panel with keystones. Also make sure that the cable is pure copper, not CCA (copper clad aluminium).

with rootkits

These are eventually going to be blocked on Windows. Microsoft are making changes to what’s allowed to run in the kernel after the Crowdstrike issue last year.

Yeah it’s unfortunate. The nftables syntax is a lot easier though!

The same thing has happened before, around 15 years ago… Before iptables there was a system called ipchains. Migration took a while, but it was eventually done, and nobody talks about ipchains any more.

Docker really doesn’t like firewalls, and doesn’t seem to play nicely with them.

These days it’s a frontend for nftables. iptables is a legacy system that’s eventually going to be removed (just like ipchains before it).

On modern systems, iptables is a wrapper around nftables. So you’re essentially using nftables except without the ability to use any of its more powerful features.

iptables is a legacy system that’s going away. If you don’t learn ufw, you’ll have to learn nftables.

Edit: Not sure why I’m being downvoted for telling the truth lol

PyCharm is cross-platform, so you can use it on Linux.