Not just third-party, but pre-existing solutions. The PR is announcing what's new, it's that simple.
4,800 karma · joined December 20, 2010
For example, a common topology in offline UPS is that the inverter and the charger are the same circuit driven differently[0] - so you can't charge the battery while the inverter is carrying load. This is popular at the low-end because you have literally half as much UPS, but makes what you're describing impossible.
Another common issue at the low end is that the inverter isn't thermally sized to run non-stop, they know they can cut a corner because your battery presents a finite and known duty cycle.
There are ways around this, but at some point you end up fixing the wrong problem - eg, it's cheaper, safer, and more resilient to buy a transfer switch instead of uprating two UPS to be capable of daisy-chaining.
Hopefully now that the refund entitlement is automatic, vouchers will only make sense if they can beat the cash offer.
The idea that 25% of us have goods that aren't worth selling, does not blow my mind.
As silly as this sounds, I wasn't aware there was a spec. That's half the fun!
For example, https://www.ebay.com/itm/225315397038
The label of this drive gives us CHS figures for three different models:
cyl * h * s * B
127MB = 919 * 16 * 17 * 512 = 127,983,616B (124MiB)
170MB = 1011 * 15 * 22 * 512 = 170,818,560B (162MiB)
340MB = 1011 * 15 * 44 * 512 = 341,637,120B (325MiB)
For some reason everyone remembers it, but no-one's been able to show me.
I believe that where the disconnect has occurred, is that when home computing started - RAM is pretty much all you had. We didn't have megabit networking, we didn't have harddrives, if we were lucky we had cassettes. So the binary prefixes were absorbed in isolation.
But a more interesting point here, is that this issue was caught by someone running debian unstable. So I'm glad someone is using them, even if they don't have your approval.
There's two maintainers, one is on an "internet hiatus", the other is either suspected of being the bad actor, or is otherwise so thoroughly compromised to destroy any short-term trust.
I assume if homebrew had such an egregious issue, they'd have someone able to respond to it.
Next, the affected codepath skips itself if it's not executed under just-so conditions. Specifically testing to see if it's being run interactively to avoid diagnosis, and testing to see if the executed binary is sshd.
Lastly, what good reason could a compression library possibly have, for overriding encryption routines in sshd?
It's a fair question, but it doesn't survive inspection at all. This is like finding someone in a ninja suit, wearing night vision equipment, creeping around a museum in the middle of the night, with the crown jewels in a bag slung over their shoulder - and asking yourself if they're perhaps a lost tourist.
I followed it through to the accompanying blog post[1] and I found the examples for "we close at 6pm on Friday" interesting because none of them work. They fail the stated problem (they don't test for Friday) and the unstated problem (when do we re-open? the examples re-open at midnight). And of course, without the prompts I can only guess whether the fault was in the answer or the question.
If the complex version worked and the simple version was naïve - or vice versa - it'd make for a much more interesting conclusion.
[1] https://koenvangilst.nl/blog/keeping-code-complexity-in-chec...
“Māma qí mǎ, mǎ màn, māma mà mǎ” - “Mom rides a horse. The horse is slow. Mom scolds the horse.”
My desired feature set otherwise doesn't differ too much from yours. Flac, BT for headphones, wifi to sync (from something that isn't itunes), support for larger sdcards, and maybe charging over anything but the 30pin. And then that one annoying bug - it'd be nice if 'shuffle all' didn't internally create a playlist that contained every song, creating an artificial limit on how many tracks can be used because that playlist fills the ram.
But what the full-size ipod really benefits from at the moment is aftermarket parts - chassis, shell, screen, touchwheel, batteries, etc. The logic board is really the only supply-constrained part left, and just addressing that one part cuts down the manufacturing dramatically.
Unfortunately the Nano doesn't garner the same aftermarket. Largely because it's dangerous & near-impossible to remove the innards once the battery starts swelling - so the biggest driver to rebuild it comes hand-in-hand with the inability to do so.
But being logged out is more efficient for cached responses. The more load the site is under, the more this pays off.
It makes sense that they're both true - it's not a case of which is more recent, it's what problem they're solving.
An example would be the number of people who don't want to issue perfectly valid chargebacks against Amazon because they'll lose access to digital purchases (kindle, audible, etc) in retaliation.
So more on-topic, it's conceivable that, for example, you have a dispute over a Google Play purchase, and in trying to exercise your consumer rights, you lose your access to your gmail account.
You don't need to be a troll to be violating a TOS, "if they're being punished they must have deserved it" is no more valid online than off.
Generally lithium UPS win in a 10-year TCO, but SLA wins in up-front costing. Which leaves us with two issues - most consumers look at the sticker price not the TCO, and no-one wants to market their products as "Our lead acid offer only /looks/ cheap, until you see what we charge you for consumables!"
The serial port serves dual-purpose. Along-side the obvious serial, you can also provide some inputs by grounding certain pins, and some outputs by sinking current from others. This has got me through some unorthodox integrations by having the UPS signal that it's on battery by having these "simple signals" close a contact/relay on the load. It's not quite a full suite of dry contacts, but it's pretty serviceable.
The problem is that 9 pins doesn't leave many spare, so to achieve this they've repurposed some. I really wish they'd implemented this as an alternate mode so you'd, for example short tx to rx to change the behaviour - instead of having the 'alternate behaviour' sitting on standard DTR/RTS pins.
Getting industrial interfaces at SOHO prices was awesome. The unintended consequences .. less so.
They're increasingly rare - which makes sense, given they have to be 100+ years old by definition. But they're out there.
It's pretty neat, and pretty surprising, that I can still sync my iPod in 2024. But having a large collection of audiobooks means there's a lot of data clogging up my system drive - where audiobooks would otherwise be an ideal candidate to be offloaded almost anywhere else (they're slow, they're infrequent, etc).