d2wa

The version number is part of the font name (e.g. “TeamViewer15”). Websites can apply a list of known font names to an element and see which are available based on whether a test element changes size after applying the font.

> Even if windows indexing aint malicious, it certainly behaves as if it is.

The problem is that closing files takes a lot of time on Windows. https://www.youtube.com/watch?v=qbKGw8MQ0i8

Arial Nova, not installed by default, is better. Free download in the Microsoft Store. Like Helvetica Neue, it’s slightly more readable by increasing the size of some punctuation marks, lengthening horizontal strokes (e.g. t), and greatly improving kerning.

Browsers are all moving towards origin-isolation. So, even when you download a font from fonts.example.com from example.net; that downloaded font won’t be available to example.org.

The local cache is, unfortunately, also an unintended source of fingerprinting and cross-origin communication.

> I don't understand why they don't just ship a huge set of fonts by default.

It takes a lot of work to draw a reasonable large set of all the Unicode characters for a given language. Time is money and fonts are ridiculously expensive.

That being said, Firefox has funded a few fonts over the years but they don’t bundle them with the browser. Google has a huge collection but doesn’t bundle them either. It makes more sense with Google as it can collect user data from its WebFont as a service system.

navigator.brave.isBrave()

It is not unique per system. As mentioned in the article, the font only changes version number between TeamViewer updates.

That setting can cause weird rendering issues in PDFs.

Most of Amazon’s regional websites offer machine-translation (although the language selection varies by region). Click the Flag next to the search field on the front page.

French, Polish, and Ukrainian are included in the beta versions of the extension.

Possibly it has to do with who provided funding, or selection by a certain type of language families.

It requires x86/64 because it runs on WebAssembly.

It also depends on where you live, allergies, seasons, …

Plus the whole problem of “the dimensions listed have no relation to real life measurements”.

Having to force myself to keep the house neat is the reason why I got a robot vacuum in the first place. You make a deal with it: you keep the floors tidy, then it manages the dust bunny population.

Roombas don’t use magnetic boundary tapes. It uses infrared beacons to set boundaries.

It takes up a lot of space in a small apartment.

A problem is a problem.

That works for services but not apps. For apps, Flatpak tries to solve this.

Sysadmins are just regular people with more experience. Sometimes, regular people even become sysadmins! ;)

Or more likely: insert a cryptocoin miner script or ads.

> I've always found that the concepts are not the difficult part of SELinux.

There’s tons of good information on this part.

> Instead it's the complexity of the configuration and tooling which is always a headache.

There’s practically nothing on this. `man selinux` lists some of the tools (last updated in 2005) in “see also” section. On Fedora, half the referenced man pages are missing, though. You’ll need to read a book (or a book’s worth of man pages) to get anywhere.

Amen.

But what am I, as the sysadmin, supposed to label things? Even if I know that I probably need to apply some labels, how do I find out what the policies are? What labels can interact with this program? You can turn to Google and find some incantations in a blog or forum post from ten years ago, but you can‘t easily see which labels a program is allowed to interact with or not. (If you even know to ask that question.)

> The gist of the problems is that the policies are not transparent

Yes.

> (probably due to security reasons?) to the user/admin, did I get that right?

No, that isn’t the reason. They’re open source. The policies are, simply put, compiled binary blobs from a comprehensive set of allow-rules and label-path definitions. The complexity of analyzing and difficulty in overriding these complex rulesets is the problem. There are tools for interacting with the system, but good luck figuring out what they’re even called. All the tools are optimized for the ruleset developers and not the sysadmins that have to play by the rules (and are never told what the rules are).

Answering the question, “What do I need to label files that should be read by program X?” is waaay to hard. You’re expected to put your files in certain locations and then some things work out-of-the-box. However, there’s no documentation on where you’re supposed to put the files.

Sure, /var/www is where you put your website files by convention. Apache can read from that directory. But what if you put it in /var/web? You can relabel the directory, but it’s not at all apperent why everything grinds to a halt when you do. The /var/www dir is owned and readable by the apache user, but Apache still says complains it can’t read it. That’s the SELinux MAC in action blocking you from doing something totally normal just because you didn’t follow the strict rulesets (that no one told you about).

The earliest confirmed case is 2010. The author/I couldn’t get hold of any earlier sample files. Do let me know if you happen to have a local copy of some older files.

It’s the SI and ISO standard decimal separator. It’s also the world’s most commonly used decimal separator. (Everywhere but the US uses space as the thousand separator.)

> One is that it stores a "play count", the number of times you've played a song, directly in that song file. So it's always re-writing the source file of the track in the library.

It writes ratings to the file, but not play count. I don't believe any player does that.

Probably not.

The practice developed around the GDPR looks something like this: You keep a separate record of deleted accounts. If you ever need to use or restore from backups, you need to filter the import or other use against that list. You can only do data-integrity checks against the backups and not use it for any purpose, of course. You must notify your local data protection authority if there are any exceptions. Like, if you restored a backup but you can't guarantee that deleted accounts remains deleted.

In other words, you don't need to wipe backups but you can't use them without processes in place to ensure you comply with your customers' rights granted under the GDPR.