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.
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.
I may be mistaken, but AFAIK, all Apple’s apps auto-save on quit and restore state on open. If so, what do you suggest they do about making third party applications do that as well?
With these two, most applications behave as they did in the pre-Lion document model.
The details in TFA are that you can add an external IMAP account to the gmail client app in Android. This does nothing for the gmail web ui, meaning you need something else for your external email.
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. If if synced to desktop/mobile apps and/or had a decent mobile web UX, that would be gravy.
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.
Self hosting your own mailserver is almost always a bad idea unless you're really a dyed-in-the-wool mail nerd - I worked for one at a small startup one summer during college, but they're a rare breed.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 doctorI was always a little disappointed with how most web browsers choose to render HTML pages that had no explicit styling information. I'm not necessarily saying web browsers should have defaults as opinionated as simple.css, but the default page margins, padding, text styles, headings, etc that they picked aren't particularly attractive.
Opinionated web developers will override the defaults no matter what they are, but if the convention was to have more attractive defaults I wonder if that would have resulted in a larger share of personal websites and blogs created using plain HTML.
[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;
}> No Forking: You may not create, maintain, or distribute a forked version of the software.
There is no meaningful difference between the words "patch" and "fork"; and the act of creating an edited codebase is explicitly disallowed.
If that isn't what they want, then they had better write more clearly.
Someone smarter than me can answer that.
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.