• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle
  • Ok so most monitors sold today support DDC/CI controls for at least brightness, and some support controlling color profiles over the DDC/CI interface.

    If you get some kind of external ambient light sensor and plug it into a USB port, you might be able to configure a script that controls the brightness of the monitor based on ambient light, without buying a new monitor.



  • You say that it is sorted in the order of most significants, so for a date it is more significant if it happend 1024, 2024 or 9024?

    Most significant to least significant digit has a strict mathematical definition, that you don’t seem to be following, and applies to all numbers, not just numerical representations of dates.

    And most importantly, the YYYY-MM-DD format is extensible into hh:mm:as too, within the same schema, out to the level of precision appropriate for the context. I can identify a specific year when the month doesn’t matter, a specific month when the day doesn’t matter, a specific day when the hour doesn’t matter, and on down to minutes, seconds, and decimal portions of seconds to whatever precision I’d like.


  • This isn’t exactly what you asked, but our URI/URL schema is basically a bunch of missed opportunities, and I wish it was better designed.

    Ok so it starts off with the scheme name, which makes sense. http: or ftp: or even tel:

    But then it goes into the domain name system, which suffers from the problem that the root, then top level domain, then domain, then progressively smaller subdomains, go right to left. www.example.com requires the system look up the root domain, to see who manages the .com tld, then who owns example.com, then a lookup of the www subdomain. Then, if there needs to be a port number specified, that goes after the domain name, right next to the implied root domain. Then the rest of the URL, by default, goes left to right in decreasing order of significance. It’s just a weird mismatch, and would make a ton more sense if it were all left to right, including the domain name.

    Then don’t get me started about how the www subdomain itself no longer makes sense. I get that the system was designed long before HTTP and the WWW took over the internet as basically the default, but if we had known that in advance it would’ve made sense to not try to push www in front of all website domains throughout the 90"s and early 2000’s.


  • Your day to day use isn’t everyone else’s. We use times for a lot more than “I wonder what day it is today.” When it comes to recording events, or planning future events, pretty much everyone needs to include the year. Getting things wrong by a single digit is presented exactly in order of significance in YYYY-MM-DD.

    And no matter what, the first digit of a two-digit day or two-digit month is still more significant in a mathematical sense, even if you think that you’re more likely to need the day or the month. The 15th of May is only one digit off of the 5th of May, but that first digit in a DD/MM format is more significant in a mathematical sense and less likely to change on a day to day basis.


  • Functionally speaking, I don’t see this as a significant issue.

    JPEG quality settings can run a pretty wide gamut, and obviously wouldn’t be immediately apparent without viewing the file and analyzing the metadata. But if we’re looking at metadata, JPEG XL reports that stuff, too.

    Of course, the metadata might only report the most recent conversion, but that’s still a problem with all image formats, where conversion between GIF/PNG/JPG, or even edits to JPGs, would likely create lots of artifacts even if the last step happens to be lossless.

    You’re right that we should ensure that the metadata does accurately describe whether an image has ever been encoded in a lossy manner, though. It’s especially important for things like medical scans where every pixel matters, and needs to be trusted as coming from the sensor rather than an artifact of the encoding process, to eliminate some types of error. That’s why I’m hopeful that a full JXL based workflow for those images will preserve the details when necessary, and give fewer opportunities for that type of silent/unknown loss of data to occur.


    • Existing JPEG files (which are the vast, vast majority of images currently on the web and in people’s own libraries/catalogs) can be losslessly compressed even further with zero loss of quality. This alone means that there’s benefits to adoption, if nothing else for archival and serving old stuff.
    • JPEG XL encoding and decoding is much, much faster than pretty much any other format.
    • The format works for both lossy and lossless compression, depending on the use case and need. Photographs can be encoded in a lossy way much more efficiently than JPEG and things like screenshots can be losslessly encoded more efficiently than PNG.
    • The format anticipates being useful for both screen and prints. Webp, HEIF, and AVIF are all optimized for screen resolutions, and fail at truly high resolution uses appropriate for prints. The JPEG XL format isn’t ready to replace camera RAW files, but there’s room in the spec to accommodate that use case, too.

    It’s great and should be adopted everywhere, to replace every raster format from JPEG photographs to animated GIFs (or the more modern live photos format with full color depth in moving pictures) to PNGs to scanned TIFFs with zero compression/loss.



  • For my personal devices:

    • Microsoft products from MS DOS 6.x or so through Windows Vista
    • Ubuntu 6.06 through maybe 9.04 or so
    • Arch Linux from 2009 through 2015
    • MacOS from 2011 through current
    • Arch Linux from 2022 through current

    I’ve worked with work systems that used RedHat and Ubuntu back in the late 2000’s, plus decades of work computers with Windows. But I’m no longer in a technical career field so I haven’t kept on top of the latest and greatest.




  • Good writeup.

    The use of ephemeral third party accounts to “vouch” for the maintainer seems like one of those things that isn’t easy to catch in the moment (when an account is new, it’s hard to distinguish between a new account that will be used going forward versus an alt account created for just one purpose), but leaves a paper trail for an audit at any given time.

    I would think that Western state sponsored hackers would be a little more careful about leaving that trail of crumbs that becomes obvious in an after-the-fact investigation. So that would seem to weigh against Western governments being behind this.

    Also, the last bit about all three names seeming like three different systems of Romanization of three different dialects of Chinese is curious. If it is a mistake (and I don’t know enough about Chinese to know whether having three different dialects in the same name is completely implausible), that would seem to suggest that the sponsors behind the attack aren’t that familiar with Chinese names (which weighs against the Chinese government being behind it).

    Interesting stuff, lots of unanswered questions still.




  • What does “maximize shareholder value” mean if not profits? You can dress it up how you like but that’s the way businesses treat it.

    It doesn’t mean short term profits over long term profits, or dividends/buybacks over reinvestment, or anything like that.

    The Delaware courts have repeatedly confirmed that majority shareholders, officers, and directors are allowed to do things like pay their employees bonuses, give corporate money to charity, demand less than the market-clearing, profit-maximizing prices, etc., even over minority shareholder objections that the corporation isn’t properly maximizing shareholder value.

    eBay v. Newmark doesn’t change that. That was a fight about shareholder rights to buy or sell shares (or majority shareholder powers to prevent minority shareholders from acquiring or selling shares without the majority shareholders’ approval), which directly affects the value of the shares themselves (without getting into the question of the corporation’s obligation to grow that shareholder value in business operations). It’s one step removed from what we’re talking about, about the directors’ power to control shares, rather than the directors’ power to control the company.


  • That’s not a requirement of publicly traded companies. Any corporation has the same obligation to put shareholder interests first, whether it’s closely held (like Valve) or publicly traded but still under the founder’s control (like Facebook) or publicly traded with no one owner that exercises significant control (like IBM). The court case that established that corporations have a duty to shareholders above everyone else (Dodge v. Ford Motor Company) involved a closely held corporation (not public) and also confirmed that the corporation’s management can exercise its own judgment and discretion in prioritizing long term over short term gains, or vice versa.





  • In the early 2010’s, daily driving Arch on a laptop was a bit of a pain. And maybe I just didn’t have the skillsets to be able to understand how I needed to maintain the system. My Arch install broke when they switched from Sysvinit to systemd. My system broke again when pacman started enforcing package signing. I also had some issues with a buggy wifi driver that would break almost every time I updated the kernel, so I started to hold back on regular updates, at which point I probably should’ve switched to a distro with a 6-month release cycle.