I think it is more likely they shifted a power of two over implicitly by a base 10 place value instead of a binary one. Or multiplied by 10. Unsure why. But, seems simpler.
52 is notable as 2^4 + 2^3 = 24, 24 + 24 = 48, 48 + 2^2 = 52. But 57?
Err, have you asked them not to do that? About the only communication use for my smartwatch I've found is sending people voice snippets, because heaven knows you can't type on those screens. It's not too hard for the recipient to read them, and if you turn whatever you were going to type into your voice snippet there's no issue with length. (This genuinely seems useful for the people who get a cell-enabled smartwatch. Could exercise without anything in your pockets.)
Can also read text messages; can't see pictures very well, though they try. The speech to text is another option but less reliable than just sending your voice. It's gotten pretty good though.
Those problems were solved for cars, they can be solved for planes. We shouldn't use it. Bioaccumulation of heavy metals was understood very early. Everything has a cost, spraying lead everywhere should be higher than what we are willing to pay.
I am guessing it's still allowed because people who fly planes can afford to lobby.
I was astounded to find TEL was still allowed in aviation fuels. Rates of cancers etc are higher near military bases due to fuel handling incidents.
I don't need to demonstrate that. What I said was: Many people who are proponents of Wayland act like it solves all security problems you get while running X11. It doesn't.
> It is not sufficient but noone said so and it would be stupid to even assume that
Err, no, a bunch of people who bother talking about Wayland propose it as a solution to everything. Now that they are being called out on it they are walking back their positions.
That's fine, I know. But acting like Wayland is feature complete when it obviously isn't is pretty ridiculous. Instead of solving hard problems the Wayland maintainers are acting like you're stupid to want to have the features solving the hard problems enables.
> So my new approach is “fuck you”. None of the Wayland detractors have a clue.
Lumping everyone who may not have a rosy view of Wayland together.
There's a good comment by an (alleged) pentester mentioning how Wayland doesn't really buy you that much. He's right. The bigger issue is lack of isolation within a gid. I can still debug your terminal and try to get your root password.
> I’m saying that because if you ever type in your password, e.g. into a screenlocker, into a terminal with sudo, or an apt-get gui, every application can listen to those input events.
And any program can (on a relatively default box) trace arbitrary programs under your gid and scan memory for passwords. The real issue here is that there are very weak process boundaries within a gid (because it is historically most convenient), not necessarily a lot wrong with X11.
Because then you end up with something like X11, which we already have.
The codebase could be re-engineered, sure, but a lot of people championing Wayland tend to see this duplication of effort as good for some reason, and at least last I engaged with them did not like the idea of a "new X11."
Personally I think something like that is an inevitability.
52 is notable as 2^4 + 2^3 = 24, 24 + 24 = 48, 48 + 2^2 = 52. But 57?