- So everything I say in this comment is unlikely to have any real impact if you were to replace the cables and retest, but I'm saying it for educational purposes. The reason the specs are strict is not because it cannot be done on less but because the acceptable margins for error and risk are lower in non consumer settings.
That switch does have metal around the ports but I could not find any indication in a datasheet that it designed to accept shielded cables. I also don't know what other devices you are connecting to the switch. Proper usage of shielded twisted pair needs the shielding to make contact to ground on both sides of the cable. I was taught years ago that using a shielded cable with neither side grounded or just one side grounded had the potential to turn the shielding into an antenna and make interference worse than with an unshielded twisted pair cable.
The flat cable is concerning. Flat cables are not part of any twisted pair spec. There tends to be two kinds of flat ethernet cables. The first being completely flat with no twisted pairs at all and the second kind having each pair twisted around each other but then the four pairs are parallel in the falter sheathing. The second kind is better and from the pictures that cable might be the second kind. However 33 meters is very long for a flat cable. Ideally you shouldn't use them but if you have to keeping them very short like under 2 meters is ok.
The pages for the other two cables never even show the cables but what looks like 3d renderings. I personally do not like that and it makes me think less of the vendors. I doubt any of the three cables would pass a full qualification test for Cat7 but they are probably completely indistinguishable from qualified Cat5e (since you are only using 1g) unless you are using them next to high voltage power conduits or next to a high power broadcast antenna. This just comes down to "Cat7 consumer products are a marketing scam."
- At least now instead of just theory we have one study of the results and a data point to use in the next attempt at a similar project. The idea is probably still solid and could be attempted again but with a more refined implementation.
- Absolutely agreeing with you but replying to you instead of multiple others below with my views on this.
Cat6A can do 10Gbps at 100m. Cat7 and Cat8 can do higher speeds in short runs but those technologies are DEAD in DC tech now. 40G is legacy tech using four lanes of 10G, replaced by 100G which is four lanes of 25G. Copper patch cables are not used with these, everything is fiber or DAC.
If you use a Cat7 or Cat8 cable the higher MHz support listed on the spec will never be used. When using a real cable of these qualities all you are really getting is better protection from outside interference.
When buying premade patch cables only buy Cat6A. Anything you see online saying Cat7 or Cat8 has probably never been properly tested by the manufacturer.
When buying a spool of wire do your research on the manufacturer. There's plenty with false labels out there. I once saw a spool of 'Cat6e' which is not a real standard.
When paying others to run cables find out what brand and what warranty the installer is providing. If they only use Cat7 and cannot provide a good explanation on why they might not actually know as much as you should be expecting them to.
- This is on forbes.com/sites/, I'm pretty sure anyone can pay to post on it now.
- Thanks for the link. That's great info to know but it's only part of the problem. If they think changing out the renderer will fix everything then they haven't learned anything.
Their build action creates seriously flawed AppImages for Linux for multiple reasons that have nothing to do with the renderer but with the AppImage creation process.
- In the sovereign citizen cases they are talking about, the typical case is that the vehicle is not registered/doesn't have plates and the driver refuses to identify themselves. They only barely lower the window if at all. They usually go back and forth a few times until the police tell them they are under arrest for multiple reasons relating to driving without a license and failure to identify.
The glass breaking happens after multiple offices have arrived for backup as the person usually gets dragged from the car screaming. The videos are extremely entertaining to watch.
The combination of unregistered vehicle, failure to prove the driver has a license, and the drivers insisting they should be allowed to drive away is absolutely a combination where arrest is legal.
- I think the blank window bug was caused by a change in the libraries used by the webview on Ubuntu 22.04 used by suggested build action. Details and fixes were spread across bug reports in multiple downstream projects but afaik it was fixed in an Ubuntu update.
- AppImages are supposed to be able to handle all of that and I have used a number of them that do. In the case of Tauri though it seems nobody on the framework team knows Linux well enough to fix the build process to not constantly break as libraries update on the GitHub Ubuntu VMs or to make all the required dynamically linked libraries get included in the AppImage. And finally most of the downstream app developers have never written an app for Linux and chose the framework expecting it to solve the problems it clearly isn't.
- The author has obviously never tried Tauri on Linux. I've never seen one of their AppImages work correctly. Every project uses the upstream GitHub action to build binaries and it compiles dynamically linked binaries limited to the glibc from the Ubuntu 22 or 24 VM used. Xdg-open is often broken too from broken environment variables in the AppImages, so you can open a link in the default web browser. The entire build process needs reworked.
- Steamdeck doesn't use Wayland.
- The OG Steam Controller didn't really fail though. Valve stopped production and sold the remaining stock because of a patent lawsuit over the rear paddles. With more time on market it probably would have grown and evolved.
- But just this year there was CVE-2025-62518 in tokio-tar.
- A lot of doorbell cameras use infrared for night vision and motion detection. You could probably just drive down a street at night with a camera tuned to show infrared and they would all be bright beacons.
- The problem with this tactic is the need to go get the Yubikey every time you make a new account.
- The Elora I use follows the circular thumb cluster format so I have three keys per thumb that can be used with little movement the rest are for rarely used layer switches and such. One of those three is for often used layers.
I have homerow mods configured but still need to work on using them more. Unfortunately a lot of what's best for typing conflicts with what's best for gaming. Almost every example split layout puts space on the right half and I move it to the left. Still need shift and control on pinky holds. And the Elora has an exaggerated pinky stagger but swapped to WQSD makes an almost perfect diamond, but at the expense of the old Q now being A is below instead of above and Z is really far away.
- Thumbs are one of your stronger fingers. In contrast the pinky is by far the weakest but we have dedicated it to almost every modifier and outlying key. I currently use an Elora from SplitKB so I can't speak to the Moonlanders thumb cluster, but if you find one you like it's a massive difference in how much usage you can get out of your thumbs while typing.
- I'm in the middle of submitting PRs to multiple projects because they are compiling on ubuntu-latest and forcing a glibc 2.38 requirement. These are multiplatform projects where most or none of the devs use Linux.
The first project I was able to change their workflow to build inside a 20.04 container. The other project uses tauri and it requires some very recent libraries so I don't know if an older container will work.
Do you have any documentation or generic recommendations for solving these issues caused by blindly using GitHub Actions for all compilations?
- I'm pretty sure it was done on the first one, Halo CE for the original Xbox. The last times I've played it have been coop in the MCC though which skips that part.
- I had this happen with fucking Google.
I called them about my Fitbit warranty and the rep needed to verify my account and wanted me to give him the code from SMS that explicitly said in the SMS not to give it to anyone!
No my account did not get hacked afterwards. Yes it was a legit service rep because afterwards he was able to pull up info on my previous warranty claim.
The actual names for each data transfer level are an absolute mess.
1.x has Low Speed and Full Speed 2.0 added High Speed 3.0 is SuperSpeed (yes no space this time) 3.1 renamed 3.0 to 3.1 Gen 1 and added SuperSpeedPlus 3.2 bumped the 3.1 version numbers again and renamed all the SuperSpeeds to SuperSpeed USB xxGbps And finally they renamed them again removing the SuperSpeed and making them just USB xxGbps
USB-IF are the prime examples of "don't let engineers name things, they can't"