For some reason, people feel like this should be a replacement for traditional luggage tags.

I do not understand this mindset.

I’d prefer to have a dedicated loop for my bag and the inside attachment points just aren’t big enough. I’d feel more secure if it wasn’t loose in a pocket and could easily fall out or be removed by an unscrupulous (or inattentive) airline or TSA employee.

My current carry-on doesn't have large enough attachment points to easily accommodate the Apple leather case's keyring, so an updated loop would have been welcome.

Apple collects data, but they usually keep it for their own use, that's the difference.

Third parties trying to do the same level of collection and also share it with partners is the issue. As such, the platform owner putting constraints on them by applying rules related to privacy shouldn't surprise anyone.

If it does, you're not paying enough attention.

With these two, most applications behave as they did in the pre-Lion document model.

Native clients continue to improve, and the mismatch between how I handle Gmail on iOS vs (for example) Fastmail shows that they're so wedded to this particular mindset that it's unlikely to ever be fully solved.

I look at people like my Dad -- early 70's, who spent most of his career as the "desktop infrastructure" manager at a midsize insurer -- who still wants to have Outlook available because he likes how Outlook does mail. It's just how his mind works. IMAP exists, but it's an implementation detail that's separate from the specific client features they add.

    Wouldn't mind exploring something akin to a web-based, self-hosted Thunderbird mail client giving a server hosted web UI for multiple email and nntp services.

IMAP "defeated" POP long ago if you wanted to use a third-party client but still access mail from anywhere.

By definition, this doesn't work in a POP environment, but that's increasingly an outdated mindset.

For historical reasons (intertia, and being early enough that I was able to acquire a "firstname.lastname" address), I don't plan to leave Gmail unless things really go south. My personal domain (Fastmail) is used for other things and I've never anything other than Mail.app and their own web interface.

makeLinks does most of the work, then sets Homebrew's zsh as the default shell -- this currently runs in bash, so it probably will need to be updated at some point -- and everything gets reloaded.

    makeLinks && chsh -s /usr/local/bin/zsh
  
    exec $SHELL && brew doctor

[1]: https://meyerweb.com/eric/tools/css/reset/

As you point out, people who care will use some of the defaults and override others as they go along, but a small bit of effort goes a long way:

    html, body {
      margin: 0;
      padding: 0;
    }

    body {
      line-height: 1.6;
      -webkit-font-smoothing: antialiased;
    }

    img, picture, video, canvas, svg {
      display: block;
      max-width: 100%;
    }

    input, button, textarea, select {
      font: inherit;
    }

    p, h1, h2, h3 {
      overflow-wrap: break-word;
    }

Someone smarter than me can answer that.

So, while you can send a patch to add a feature, you couldn't release that modified version on its own.

For the record, I don't have a great answer to this either -- genuinely curious.

The existence of comments about how certain elements were rendered on export made me think that something was missing when compared with CM.

This isn't to say I prefer CM -- because Markdown came into being from Gruber's script. In a literal sense, "Markdown" is defined as whatever `markdown.pl` is, warts and all -- however, contact with the outside world forced things to move in a direction that is (so to speak) more organized that what John originally wrote.

https://github.com/opendevise/downdoc

I'm not saying you're wrong, but let's be clear about what these are. I would point out that Linux inherited some, but not all of its naming conventions from Unix (as did macOS), but at least here, that is a secondary concern.

Carry on...

[1]: https://arstechnica.com/gadgets/2001/08/metadata/