The Linux kernel has/had the ability to create network interfaces for AX.25, NETROM (on top of AX.25) and other protocols besides IPv4/IPv6. Routing of said protocols also was supported.

You could use ethernet adapters, packet modems with KISS serial interfaces, a soundmodem driver, etc. Linux would manage the interfaces, and the same netstat/route/etc. commands you use manage other network connections worked with AX.25 as well.

But relatively few Amateur Radio programs ever offloaded this work to the Linux kernel, instead connecting to relevant communication hardware directly. And depending on the Linux distribution, they may or may not compile these lesser-used modules by default (which can be important depending how a Linux distribution treats secure boot signing).

Funding has been restored by CISA for MITRE to run the CVE program.

Which direction things go given the creation of a few alternative structures remains to be seen.

(Obligatory IANAL)

Technically, the record labels have a point.

The US Copyright office has assigned a 95-year copyright to anything published prior to February 15, 1972, with the possibility of 120 years if it had not been published before that date.

So recordings at least 95 years old (1928 and prior) at this point may be allowed to be published.

The last recording covered under this rule will enter the public domain February 15, 2067. If it is readable at that point is anyone's guess.

Reading the story and looking at the video, it looks like there is a memory chip storing calibration data about the screen and pencil. This corrects for where the screen detects the pencil (and how strongly) versus where it actually is.

Third party repair firms either lack the software to recalibrate the touchscreen, or don't know how to put the iPad into a mode which allows this.

The need to calibrate a touchscreen is not unusual. So I'm curious why it was not a problem before.

The version numbering may due to end-user expectations, not actual major feature adding.

Other products have had to jump version numbers or change version schemes because users asked "Why is your competitor at version 70 while you still are at 10.1?" (For example: Slackware Linux from version 4.0 to 7.0, etc.)

The United States Constitution prohibits "ex post facto" laws. These retroactively make things illegal.

This is not exactly that. But it punishes firms for past behavior with a punishment that was not known at the time. The legislature will have to be very careful writing this to avoid having the law thrown out.

A constitutional lawyer would have a better idea of what is allowed.

Actually, no.

In the United States, there are loopholes for political speech.

You would think they could not send you text messages. But as soon as a human is in the loop, they can send as many as they want.

All you need is an app that shows the message, adds the name and phone number to send to, and has a "Send" button to send the text message. Click "Send" and the next target appears, ready for you to click "Send" again. I've seen a volunteer using such an app and clicking it rapidly while bored in class.

And since people stopped picking up the phone for strangers and have spam filters on their email, text messages are the way many political campaigns try to reach voters.

Companies (and academia) having their own language has been known for decades.

Your role in a society or organization, and what they consider important also control how you speak.

During the 1970's and 1980's, Richard Mitchell published a series of newsletters known as The Underground Grammarian about abuse of the English language.

The opening to his book Less Than Words Can Say describes how a professor's language became more verbose and indirect the higher they were promoted within the organization. Another chapter goes into detail about how rulers and the ruled speak differently and how that is enforced.

Richard's works are freely readable online, although the website's formatting is a bit old-fashioned.

The problem is *not* that Verizon has decided to go after one particular School SMS provider.

Rather, Verizon has decided to charge bulk SMS providers (in this case, Twilio) a per-text-message fee. This fee is said to help pay for Verizon's anti-spam efforts.

Twilio then decided to pass this fee to customers in the exact amount Verizon charged.

Two other providers in Canada (Rogers & Bell) already charge Twilio similar fees, and other carriers are expected to do so soon.

Remind just happens to be a Twilio customer. But all Twilio customers {and customers of similar SMS services} are affected.

While there may be tax credits at the Federal level, at least 17 states charge additional registration fees for electric vehicles once the battery gets above a small (hybrid) battery size.

They do this to make up for loss gas taxes, but charge for such at a flat rate that does not factor in mileage or if you have a plug-in hybrid.

So if you purchase your electricity from charging stations which try to be gas-price equivalents, you end up paying more to fuel an electric car than had you just fueled a gas one.

When Georgia implemented their fee (one of the highest at $200/year, $300/year for commercial use), Tesla sales fell 83% and did not recover. This was true even though the state also had an electric-car income-tax purchase discount.

"Test is dead" was the keynote presentation of a Google Test Automation Conference six years ago.

My personal view is that if you are doing web development where your company rapidly & repeatedly deploys releases on behalf of customers, you might be able to get away with not having much of a QA department so long as the impact is low. If a problem arises it can be quickly fixed without much of a financial loss.

But if you are in a regulated industry, failure of your software will result in significant lost revenue while its being fixed, or your software is deployed only every few weeks or months by customers who do their own acceptance and integration testing, then you probably need to do more QA work & dedicated QA work upfront. In such scenarios the software producer and their customers may encounter significant losses and/or inconvenience because something faulty snuck through.

There is not enough aligned ramp space there for you to see if there is any oncoming traffic on the main road before you have to collide with it. Extending the ramp would require expanding the bridge at its terminus.

So they expect you to stop, look backwards for a gap, and accelerate hard to get into it. Which can get quite tricky at hours when there is a lot of traffic.

At other intersections you may have to quickly get on before the on-/off-ramp gets you off again, or slow down prior to sharp curves on an exit ramp.

If you are not used to this (or anything about New York City/Long Island traffic for that matter) it can take some getting used to. Many roads were originally designed when speed limits and cars were slower, and there is not much room for expansion.

"...there's no reason to have a certain sign on certain roads (Stop sign on an interstate highway)."

What about here? (Cross Island Parkway, New York USA, Exit 31)

Stop signs often do appear on highway entry ramps, especially where they are short. This is true in construction areas, as well as on some older entrance ramps around New York City.

Technically this is a 50 MPH (~80 km/h) Parkway and not an Interstate, but rather than randomly searching the area this was the first that came to mind.

HTTP/2.0 actually does this for HTTP headers as part of the HTTP Header Compression specification.

While it isn't residential, Knight Center Station in Miami, Florida (USA) was built into a pre-existing building.