I believe it actually is used in regular Mint (the Debian kernel doesn't include it, but it looks like Ubuntu's and Mint's do). But yes, I suppose it is still in the process of being adopted by various distributions.
To be fair here, no one's certain this will be cost-effective either. The new techs make it worth trying though.
As far as I know, Linux ignores NTFS permissions when given raw access to a disk, or rather, acts as thought it's SYSTEM or some other high-level user, working around anything Windows might have set.
I think that was the case for ntfs-3g.
I'm not certain that's the case anymore with the new kernel NTFS driver, though I havent tested it. If it isn't, it should be correctly handling the file premissions.
I'd try Heiboard again, but it didn't have built-in layout options, nor a clearly communicated way to get them last I tried it.
I think that's on the development plate for 0.5 if I understand correctly.
Sadly AnysoftKeyboard hasn't seen a release in some time either. Still using it for now, though.
I'm surprised it's not mentioned in the article, but also complicating this situation is the Chagos refugees seeking to take control of the TLD and/or receive reparations from the current registrar.
Their relationship had been kind of good until recently as there has been an uptick in dissatisfaction on the status quo of Taiwan's political status (unspoken independence) — mostly on China's side, but also from some Taiwanese.
They remain important trading partners for each other, though.
It's not that it's a threat, it's that there's a difference between archiving for preservation and crawling other people's content for the purpose of making money off it (in a way that does not benefit the content creator).
Not all applications on your computer may be encrypting their packet traffic properly, though. That goes especially for the applications that might be trying to reach out for resources on your local home network (like printers, file shares, and other home servers) as well as DNS requests which are usually still made in the open. I would not recommend eschewing an entire security layer willy-nilly like that. On public Wi-Fi, I would definitely still suggest either a VPN or using your cell phone as a tether or secure hotspot instead if possible.
Sony holds the rights to a bunch of them.
MZLA makes Thunderbird. Mozilla Corp makes Firefox. Mozilla Foundation owns both.
Well, first of all, K9 regularly holds beta tests for their new versions before release already.
Being launched under the Thunderbird brand, though, is expected to hit a much wider audience than just K9 users. And being a first impression, they want to do everything they can to make that impression a solid one.
I believe Thunderbird is K9's current beta, rebranded.
Rant incoming:
This was spurred by having just read https://www.androidpolice.com/google-tv-streamer-questions-answered/ , particularly this bit:
>When I asked directly, a Google representative told me they couldn't confirm which chipset powers the Google TV Streamer — essentially, Google declined to answer.
I've been noticing an increasing trend by device makers to not disclose the SoC their devices run on. I've been seeing it with e-readers, network routers, media streamers, etc.
It's incredibly frustrating to have devices actively exclude important information from their spec sheet and even dodge direct questions from tech news reporters. Reporters shouldn't have to theorize about what chip is in a released device. It's nuts.
If you're wondering why this infomation is important, it can be for several reasons. SoC vendor can have significant impact on the real world performance and security of a device. It also carries major implications for how open a device is as SoC vendors can have dramatically different open source support and firmware practices.
I've had to resort to inspecting the circuit board photos of FCC filings way too much lately to identify the processors being used in devices. And that's not a great workaroud in the first place as those photos are generally kept confidential by the FCC until months after the device releases (case in point the Google Streamer).
If there were a way I could load Lineage on it, maybe. Not interested in a device locked to Amazon's firmware.
I was expecting idiotic rules screaming "bureaucratic muppets don't know what they're legislating on", but instead what I'm seeing is surprisingly sane and sensible
NIST knows what they're doing. It's getting organizations to adapt that's hard. NIST has recommended against expiring passwords for like a decade already, for example, yet pretty much every IT dept still has passwords expiring at least once a year.
It’s been about a decade of me, at least, hearing that the only problem is they’re just not relevant enough, and if we just target them better/make them more personalized/whatever that’d solve all the issues everyone has with it.
They're not referring to the issues you and I have with. They're referring to the issues their ad customers have with it. More relevant ads mean ads can be more effective and valuable for advertisers -- not less annoying for viewers.
I don't recall Qualcomm trying to buy ARM. That was Nvidia. (though, yes, it likely would also have been prevented if it had tried)
But they'd probably have a better (but still slim) chance of getting a purchase of Intel through. That'd be a more horizontal acquisition than a vertical one as Qualcomm doesn't make x86 chips so they can at least argue it wouldn't be anti-competitive.
They don't mention what the offer is. Very easily could be a stock-based deal where Intel stockholders get a portion of the combined company. That's how T-Mobile bought Sprint.
GenAI = Generative AI
AGI = Artificial General Intelligence
You are talking about the latter. They were talking about the former.
NetSurf is a very barebones browser. It can fill a niche, but is not a daily driver where other options are available.