There are glasses that do only captions, no recording or camera.
The article says "any eyewear with video and audio recording capability" which makes sense. Although even that is unreasonably specific and should just say "recording or transmission device" to ban the activity and not the item.
I wonder if it's possible for a regular machine with two high speed ports to do a cable test by itself. Maybe it can't test all the attributes but could it at least verify speed claims in software?
Apparently the USB driver stack doesn't report the cable's eMarker chip data back to the OS. However benchmarking actual transfer throughput is the ultimate test for data connections (vs charging use cases). Unfortunately, TFA doesn't really go into this aspect of cable testing as the tester seems to only report eMarker data, which pins are connected and copper resistance.
Since a >$1,000 automated lab cable throughput tester is overkill, my thumbnail test for high-speed USB-C data cables is to run a disk speed benchmark to a very fast, well-characterized external NVMe enclosure with a known-fast NVMe drive. I know what the throughput should be based on prior tests with an $80 active 1M Thunderbolt cable made for high-end USB-C docks and confirmed by online benchmark reviews from credible sources.
There would be too many factors involved for a proper test. Many laptop USB controllers would probably not even have the capacity to run two ports at full speed simultaneously.
That seems to imply concern for the gambler, who at least has chosen to play.
A much bigger problem might be when these markets bet on a meatspace event and then a bunch go out and try to influence innocents in meatspace, to great detriment of society. Like this journalist https://readwrite.com/threats-israeli-reporter-polymarket
The marketers did this for 5G also, calling their product 5G before it was actually deployed, only because theirs came after 4G but wanted to ride the upcoming 5G buzz.
It seems marketing /depends/ on conflating terms and misleading consumers. Shakespeare might have gotten it wrong with his quip about lawyers.
There was soooo much intentional disinformation around 5G. Everyone who wanted to sell anything intentionally confused the >1Gbps millimeter wave line-of-sight kind of 5G with the "4G but with some changes to handle more devices connected to one tower" kind of 5G. I wonder how many bought a "5G phone" expecting millimeter wave but only got the slightly improved 4G.
From a standards design perspective, there is nothing wrong with it. It's the same protocol running on two very different frequency bands. They co-exist and support each other.
They should share a specification (I know this is correctly called a 'standard') but the should have been a separate logo for each non-interoperable group of useful features (a different concept also often called a 'standard'); as USB has proved.
5G and 4G are not terms applied to WiFi. We have 802.11a/b/g/n/ac/ax and WiFi6/7
WiFi operates in the 2.4, 5, 6GHz bands, but those frequency bands are not used to differentiate WiFi standards because you can mix and match WiFi 6/7 on all three bands.
There are also more WiFi bands below 2.4 and above 6GHz, but they're not common worldwide.
The good news is this domain doesn't call for cutting edge, 2 nm process.
There are more than a half dozen fabs in the US which can produce networking chips like ethernet controllers, line drivers, SOC, etc: Intel, TI, Samsung, et al. If US wanted to onshore routers, we could make it happen.
a router produced in the US from foreign-made parts - like controllers, drivers etc. - is not in the "covered list". Although I admit the wording is vague: "produced in the US".
You can pin actions versions to their hash. Some might say this is a best practice for now. It looks like this, where the comment says where the hash is supposed to point.
Old --> uses: actions/checkout@v4
New --> uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
The problem is actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 probably doesn’t do this same pinning, and the actions ecosystem is such an intertwined mess that any single compromised action can propagate to the rest
This is true specifically for actions/checkout, but composite actions can have other actions as dependencies, and unless the composite action pins the versions of its dependencies, it is vulnerable for this attack.
This article[0] gives a good overview of the challenges, and also has a link to a concrete attack where this was exploited.
Does it solve anything? I don't see this as a GitHub problem, it's a "we built a dependency management system with untrusted publishers" problem.
GitLab's `include` feature has the same concern. They do offer an integrity check, but it's not any more capable than hash pinning to a commit.
Fundamentally, if you offer a way to extend your product with externally-provided components, and you can't control the external publishers, then you've left the door open to 'these issues'.
See also pinact[1], gha-update[2], and zizmor's unpinned-uses[3].
The main desiderata with these kinds of action pinning tools is that they (1) leave a tag comment, (2) leave that comment in a format that Dependabot and/or Renovate understands for bumping purposes, and (3) actually put the full tag in the comment, rather than the cutesy short tag that GitHub encourages people to make mutable (v4.x.y instead of v4).
I've always been worried about their backend changing and somehow named tags with a previous commit hash working for an attacker to give something you didn't expect for the commit hash.
Checkout v4 of course, released in August 2025, which already now pollutes my CI status with garbage warnings about some Node version being deprecated I could absolutely care less about. I swear half the problems of GitHub are because half that organization has some braindead obsession with upgrading everything everywhere all the time, delivering such great early slop experiments as "dependabot".
The article says "any eyewear with video and audio recording capability" which makes sense. Although even that is unreasonably specific and should just say "recording or transmission device" to ban the activity and not the item.
reply