People should stop posting StatCounter, it’s so unreliable and noisy.
But I am surprised by the Cloudflare numbers, which are a lot more reliable, and still have Linux at ~5% worldwide, which is still higher than I thought! And even ~6.5% for the past two months, though I imagine that’s a seasonality effect - maybe Linux users in the northern hemisphere are more likely to use their computers at home during summer? :P
I didn’t really like it on first sight, but I’ve been trying it every now and then and it kinda grew on me. But if I had to bet I’d still predict that it’s going to get a lot of backlash.
Well, brace yourself for the Nova redesign, which is going to change a whole lot :)
Yes, you can upgrade to beta or developer edition and move over your data. That article uses Firefox Sync, which is the easiest method, but I think it would also be possible to copy over the contents of your profile folder if that’s what you want to do.
Beta is generally very stable, so the main thing you’ll notice is a different icon. And you’d even be aware of changes before your customers see them :)
In that case I’m fairly sure that what I described is the issue: Qwant doesn’t support trending search suggestions, so it’s great out and doesn’t do anything.
If you want to uncheck it, temporarily switch to Google, uncheck it, then switch back to Qwant.
What is your default search engine set to? My guess would be that the one you’re using doesn’t support it?
If so, for your sanity you could change it to, say, Google, uncheck it, then change it back?
No, I was already convinced that relying on colour alone is insufficient. I still think they can be useful helpful if they don’t rely on colour alone.
True, there are exceptions (that’s why I keep saying most), and I think the pattern is more common on web than on desktop. (Though I think Gnome also compensates a bit with their boxed lists as an additional affordance.)
Note that I am 100% on your side in saying that there are annoying toggle boxes that are unclear. In your image, I can only tell that the second is probably on because the right-hand side is usually used for the on state in LTR locales. But they can be better, e.g. with an on/off label integrated. Ironically, GNOME has a toggle to enable this:
Well, I’d encourage you to keep an eye out; I think you’ll find that the majority of controls on the web behave as I described. And I think that’s a good thing, too: it’s far quicker and easier to be able to deduce behaviour from the control you’re handling at the moment, than having to scan the complete context. And especially if e.g. you’re visually impaired, the latter can be a major hassle.
(And indeed, the other controls you mention almost never apply instantly, so their behaviour is still predictable. When they do, they’ll often still have some other affordances to indicate that they do apply instantly.)
I was trying to make the point that the way a control looks gives you some information on how it will behave, because software has generally been consistent with associating those looks with those behaviours.
So if you see multiple options with a circle in front of them, selecting one, then selecting another will usually deselect the first one.
On the other hand, if those options have squares in front of them, selecting one, then selecting another will usually result in both of them being selected.
And in both cases, usually they will be part of a form and will only take effect when you submit that form using a button.
On the other hand, something that looks like a toggle usually takes effect immediately on toggling.
Of course it is technically always possible to have each of those behave like any of the others, but you will be breaking conventions if you do so. Styling is an affordance to inform the user about the behaviour.
I mean, they can, and they can also be made to be mutually exclusive - but it’s better to use radio buttons in that case. If that pattern is used, there’s not really a good way that a checkbox will take effect immediately beforehand, or whether it will require submitting a form, except scanning the full page to look for such a button.
It’s nice to be able to know that they take effect immediately though, instead of needing to click a submit button.
Yeah I think that’s fair. As far as I know, it’s also mostly been used for detection, not patching, and possibly it’ll be better at exploiting than at patching.
I don’t think these are all Mythos, but it’s more than 2 fixes: https://infosec.exchange/@tomrittervg/116443139069130293
The author seems to put a lot of stock in the whole “the blue team has access to these AI tools that the red team doesn’t currently have access to” argument
I didn’t read it like that. I think the point was that the red team had an edge over the blue team (by being able to spend a lot of effort on a single exploit), so when both teams have access to these same tools, it’ll be more of an equal fight.
That makes sense!
That sounds like exactly what I meant; where the GPL is viral on the project level, MPL is viral on the file level. So if code, under MPL, is added to a file, that whole code becomes MPL.
AFAIK MPL is viral, but only at the file level. In other words, if you modify an MPL-licensed file, your modifications need to be MPL-licensed, but if you add additional files, those can be a different license.
(In practice, I suppose that that’s fairly weak?)
Wait a minute, what is the Flatpak Nvidia package? Do you need that for GPU acceleration for Flatpak apps on Nvidia? How do you even know whether GPU acceleration is working?
(I recently got a new laptop and it’s the first time I have a dedicated GPU, and I have no idea how it all works. Sorry for hijacking your thread.)
Yeah I know, I’d much sooner trust those numbers - but those are pretty good numbers! Desktop only of course, but still!