zootboy

I meant the latter; I'm fine with Youtube getting a cut, I'm not fine with Mr. Beast getting a cut.

That sure sounds like they divvy up the money based on total viewership, not my individual viewership. I don't like the thought of a large chunk of my subscription money going to channels I don't personally watch.

I pay the creators I care about, but I do it through Patreon, not Youtube. Of those $14 of Youtube subscription fees, approximately $0 would go to the creators I care about. If Youtube made some guarantee that the money I spent would only go to the creators I watch, I'd subscribe instantly.

I'd go a step further: if you change the UI for no functional reason, you are a bad person who is causing needless consternation, confusion, and productivity loss. Even if you believe you have a functional reason, you had better think really long and hard about whether the supposed improvement you want is worth the pain of every single user needing to adapt to that change.

I've been using this macro with GCC / GDB for years without running into the issue you're describing:

#define DEBUG_BREAK() do{__asm__("BKPT");} while(0)

I can continue just fine with it. Granted, this is on the various Cortex M0/M3/M4 chips, so I can't say for sure if it works on any of the bigger, fancier ARMs.

FLOSS = Free / Libre Open Source Software. It's meant to be a more specific version of FOSS, making the point that it's using a properly "libre" license, and not just free of charge and source-available.

Personally, I prefer Windows 93:

http://www.windows93.net/

Like, say, OpenStreetMap?

https://www.openstreetmap.org/

That is a separate state in both of these systems, though. My complaint is that a perfectly valid tracking number isn't immediately in the "awaiting pickup" state after being generated by their systems, and is instead in the scary limbo state of "I dunno, that might be an invalid tracking number".

The "invalid tracking number" thing drives me nuts. Both Fedex and UPS do it. How hard is it to stick a record in the database the moment a tracking number is generated so that I don't get a "This tracking number is invalid" message? And it's not like it's invalid for a few minutes; I've had tracking numbers remain "invalid" for almost a day. Absolutely insane.

This headline could really use the word "hurricane" in it. I had no idea what Otis or Acapulco were, and my initial guess was wildly off: some sort of space probe experienced a catastrophic failure on the way to an asteroid.

I left out things that a typical battery management system will prevent, like over/under charging, or operating outside safe temperature limits. But yes, charging a typical cell below 0 degrees Celsius will immediately and permanently damage it. Here's a ref with some details on why:

https://www.bonnenbatteries.com/lithium-battery-low-temperat...

Li-ion chemistries that are tolerant of charging at low temperatures are a subject of active research.

The world of lithium-ion battery chemistry is quite complicated, but in my experience, the top contributors to battery wear-out are, in decreasing order of severity:

- Charge cycles (including partial cycles, e.g. 100% -> 50% is half a charge cycle)

- Depth of discharge (deeper discharge cycles are worse)

- Extended periods in hot conditions (over 40 degrees Celsius)

- Extended periods of being held at 100% state of charge

In essence, your charging behavior dings the first two items: higher number of charge cycles, and deep discharge cycles. If your goal was battery longevity, keeping the phone plugged in as much of the time as possible would be the best strategy. Bonus points if your phone supports a "stop at 80%" mode, but still the winner even without this feature.

Anecdotally, I've found OSMand's search functionality to vary between OK and completely unusable. Especially when entering addresses, OSMand really struggles to interpret what should be quite straightforward entries.

While I haven't extensively used OrganicMaps, I found its search functionality to behave much better.

Probably for the reason the author speculates about in the article:

> For example, would it not be cool if there was a game with a stack buffer overflow bug that allowed us to run arbitrary code remotely? That could potentially enable us to softmod an Xbox over the network, without the need of any special hardware.

I would assume so. I tested on one of my private domains that generally isn't linked to anywhere, and it just returned the few domains that I generate Let's Encrypt certs for, plus my nameservers.

Interestingly, I did not receive any DNS queries on my authoritative nameservers during the query, so they don't seem to be doing any active DNS probes.

Honestly, I don't agree with this. The evolution of computers seems to have sharpy dwindled, to the point that I regularly switch between a 2016 Lenovo and an 2021 Framework and hardly notice the difference, at least performance-wise.

Indeed. The point of linking the first one was to indicate that the issue has been reported for 3 years without being fixed.

I would be wary of using their calendar app. It has had a long-standing bug in basic timezone / DST handling:

https://github.com/SimpleMobileTools/Simple-Calendar/issues/... https://github.com/SimpleMobileTools/Simple-Calendar/issues/...

My new favorite punching bag for this is Discourse. It's literally just a forum. Some text and maybe a few images. Nothing crazy. But their "new and improved" system has a stupid lazy-load design that takes 7 _seconds_ to load. The root document https transfer completes in 500 ms. What the flying fuck is going on in that remaining 6500 ms?

And it's not just the first time. Every time you refresh the page, 7 seconds. And they have the audacity to call this towering pile of javascript nonsense "simple": https://www.discourse.org/about

That feels like trying to get by on a technicality. The casual reader would reasonably interpret "after" to imply some causation the way this headline is written.

Sadly, this isn't over. The appeals court simply overturned a lower court decision and remanded the case back to the lower court.

Oh dear, indeed. Why not offer the option to make an account directly? That would offer at least some solace that your data is not being shared outside the walls of 8x8.

My guess would be pornography. That seems like the most obvious use of a video calling service, and something that would cause them to run afoul of various legal requirements (e.g. age verification / records keeping).

The control key should be the bottom-most, left-most key on the keyboard. It should also be a different size or shape from the FN key so that you can tell it by feel.

In a way, this is kind of an indictment of modern software overall. Why doesn't the average person think that tasks can complete quickly? Because so much of the software they interact with is bloated, slow, terrible crap that they all think that's what is normal.

But on a more constructive note, perhaps instead of introducing artificial delays, you could instead show the user proof that the action has been completed?

I've noticed an obnoxious new UI anti-pattern showing up more frequently as of late: a loading page that renders a fake UI made of nothing but light grey boxes. More often than not, it's not even the actual UI layout of the page, just an artful rendition of a blank UI. These sorts of things drive me nuts, especially when it's a page whose contents could easily have been served as a static HTML page instead of rendering this silly fake UI via javascript then using more js + requests to replace that garbage with the actual content I want.

I use a randomized PIN pad on my phone, and I've gotten quite used to it. I can enter my PIN almost as fast as I could on an unscrambled pad; it's definitely not hunting and pecking.

Lol, not my 2005 Toyota. It doesn't even have anti-lock brakes, much less a GPS phone-home system.

I got 66% for Gmail, but a bunch of these did feel a little difficult to judge. Like "Bugs are not fixed." Is that any bugs? All bugs? The majority of bugs? Important bugs? Etc, etc. I went with no for "bugs are not fixed", but yes for "bugs are not acknowledged."

Honestly, the biggest potential avenue for being screwed by Gmail is being locked out of all your other accounts that use your Gmail address as a login credential. That's sort of covered by a few of the options, but I think it deserves a question of its own (e.g. "My access to other services is mediated by this service.")

I also drew a line between Gmail and GSuite. GSuite would obviously win back some points in the "I pay for it" category.