Re: Snark .....
Perhaps finding a local museum curator/archivist to talk about the issues would help. Someone who can be a "neutral third party" might get more response.
23 posts • joined 10 Oct 2019
I gave up on the advertising "social contract" you're talking about, once things like malicious ads started showing up on otherwise reputable websites. Ones that look like they're dialog boxes, error messages, blink like crazy, claim that 'OMG you have a virus'... or that install malicious software if you happen to click with an un-secured browser. Friend clicked on one, wound up calling into one of those fake tech support companies and getting his computer locked down enough for me to have to come fix it.
All of those things exist. I'm not making it up. Ad sellers did not do a very good job preventing any of these sorts of ads from showing up.
If you want to pretend there's some sort of social contract, I'm not sure why you think it should be as one sided as "view this ad to see this content", and not "view this safe ad that's not ridiculously intrusive and not targeted directly at you with data collected from everywhere you visited... to see this content".
Quite disappointed when they stopped doing firefox sync with no registration required. Enter about 14 letters to match those shown by your main browser, and then they'd link with no account information required. Supposedly encrypted on the server, too.
Now it's "login to Firefox to sync, so we know where you are."
Bose isn't the only one breaking their products. Every HP printer "security update" is very likely to stop you from using third-party ink cartridges, until the ink cartridge vendors find a new way around it. They do this quite regularly now.
Thanks to this method of security, and the abilities of 3rd party ink hackers, I will never use HP ink in an HP printer aside from the required "setup cartridges".
Rock solid, unless the previous IT guy makes the mistake of putting all the drives in the same array with enough redundancy to handle 2 bad drives.
Due to the nature of "MTBF" across 28 or so drives, we could count on approximately one or two drive failures per month, possibly stopping the whole array (and most work) until we could get another drive in. Rock solid, for soft sandstone values of rock.
Thanks to a version control system (check out entire source onto a different network drive), when one of our network drives failed completely, we could just restore it from backup. When devs checked the changes back in, all the previous changes were "automatically" included because they had the full sources. No work lost, just some change history missing for a few days.
This seems much more sensible than relying on just one network drive for the whole business.
Worked for a company once that had an internal phone system for a particular department. Pick up one phone, and the other 4 automatically rang. Useful if you know you're usually going to be calling particular areas. They were also the oldest-looking phones in the place.
Nope. The cartridge's DRM chip doesn't actually know how much ink is in the cartridge. It estimates when it is empty, and stops the printer from using the cartridge once the "number of dot equivalents remaining" counter decrements to 0.
There are no sensors on the newer cartridges to tell how much ink is actually left in the cart.
Thanks to HP's over-reliance on DRM to sell expensive supplies, I only buy 3rd party ink.
Biting the hand that feeds IT © 1998–2021