What keeps me from updating that I am confused about the way forward regarding FileVault & APFS. I currently have FileVault enabled as I need my drive to be fully encrypted (liability for my clients). I want my backups to be encrypted as well. But now APFS solves disk encryption on FS layer instead of going through CoreStorage. And I'm confused about the way forward for me. Is there some documentation that explains 1…
MacOS High Sierra
221–230 of 630 posts
Re: MacOS High Sierra
#222Earlier quoted context omitted.
> This isn't a criticism of you, but when a major OS update comes down to trivia like this, it seems a bit of a shame to me. There's a whole new FS that went into production in something like 4-5 years (unheard of) among lots of over things...
I am very skeptical of a new filesystem that is going out to users that fast. I haven’t tested the beta yet, but I would imagine we still have the option of using HFS+? Otherwise I’ll wait six months or more to even attempt it.
Re: MacOS High Sierra
#223Earlier quoted context omitted.
Your typical Android phone calls home around 1200 times per day. Getting that number down to zero means making it pretty much unusable.
The difference between Android and Google Play Services/Google Apps Suite is, that the latter use Google servers and the former does not. If removing these apps makes Android unusable for you, it means you are hooked on or locked-in to them. Asking for open-sourcing the client parts will not help you anyway, because the server parts are still running on Google servers and you won't be able to replace them.
It wouldn't be ideal, but a big improvement. Providing a clear API to Store, Maps, Mail, etc. would (1) allow developers to publish their own client for these services (that e.g. don't display ads, or don't track the user, or obfuscate/anonymise the information they send to the servers), and (2) allow competing backends to be developed and allow the users to choose between them without having to change the mobile OS.
Re: MacOS High Sierra
#224Earlier quoted context omitted.
Yes, American dates are confusing and illogical at the best of times, I wish America would standardise on the international ascending order date style of 25/09/2017.
I hope we'd all standardize on the opposite: 2017-09-25.. it sorts properly when used in file and document names :-)
Re: MacOS High Sierra
#225Earlier quoted context omitted.
How is that unusable? If you just don't upgrade it still works.
Except for those, who upgraded their machine and the old OS release doesn't run on it. Or myriad other reasons.
It's just too slow a beast, all of that. GPG (and especially email integration) is dying. Let's hope it gets a new life one day in the future.
Re: MacOS High Sierra
#226Earlier quoted context omitted.
argh! i can't believe people are still arguing about whether we should do MM/DD/YYY or DD/MM/YYYY or anything similar to that. here's how you should write a date that you are going to show to a user: Jan 11 2016 if you accept that premise, it doesn't matter (much) what order you put the elements in, because none of them can be confused with any other. a word is a month, a one- or two-digit number is the day of the mo…
Don’t you mean 11. Jan 2016? ;)
the real problem is displaying both the month and the day of the month as one- or two-digit numbers, which leads to ambiguity. display the month as a three-character string, and the year as a four-digit number, and we are all on the same page again.
Re: MacOS High Sierra
#227Does anybody have more information on this claim of a keychain vulnerability in High Sierra... just saw it fly past on Twitter. https://twitter.com/patrickwardle/status/912254053849079808 >on High Sierra (unsigned) apps can programmatically dump & exfil keychain (w/ your plaintext passwords) vid: https://player.vimeo.com/video/235313957 #smh
When you go to facebook.com, your device must surely decrypt the keychain to plaintext to prefill the password field so it can send your password to facebook.com - Thats how it works.
So this seems like normal functionality to me, someone has just put it in a command line. Someone has just reverse engineered the keychain decrypt that happens all the time.
Am I missing something?
Re: MacOS High Sierra
#228Earlier quoted context omitted.
I remember the first time I saw Spotlight. It was magic. Then came Expose. Wireless that worked. Sleep that worked. Trivial configuration of things like sshd, apache and samba. Amazing days. Lately I only upgrade when forced. I ran 10.8 until earlier this year when I finally upgraded my machine. Then I spent a week trying to figure out how the hell to get gdb working again because binaries now require code signing an…
Remap single tap CAPS to ESC and when used in combination with another key or long-pressed - CTRL. This has changed the way I use my keyboard in vim and tmux. I'm doing this on Ubuntu, but there are ways to get it done on OSX too.
Re: MacOS High Sierra
#229Will Aperture still run on High Sierra, or is Photos already a viable replacement?
Photos will never be a viable replacement for the full Aperture professional use cases -- they have different goals. Aperture might or might not run on HS (not sure), but holding to it until Photos catches up is not very good strategy, at some point it will just stop working (and it's not getting any new fixes, updates, etc). Better move to Lightroom or something similar.
I don't want to rent software, and I don't want to install the dreaded Adobe installer. What other good alternatives are there? Darktable doesn't pass the test.
Re: MacOS High Sierra
#230Earlier quoted context omitted.
The difference between Android and Google Play Services/Google Apps Suite is, that the latter use Google servers and the former does not. If removing these apps makes Android unusable for you, it means you are hooked on or locked-in to them. Asking for open-sourcing the client parts will not help you anyway, because the server parts are still running on Google servers and you won't be able to replace them.
> Asking for open-sourcing the client parts will not help you anyway, because the server parts are still running on Google servers and you won't be able to replace them. It wouldn't be ideal, but a big improvement. Providing a clear API to Store, Maps, Mail, etc. would (1) allow developers to publish their own client for these services (that e.g. don't display ads, or don't track the user, or obfuscate/anonymise the…
The much better approach is bring your own backed. E.g. I'm using Sygic (because it is offline and the roaming fees were killing the online maps) and it works in the all places where the original Maps work. If I click in the Booking.com app to navigate to the hotel, for example, Sygic (and other alternate maps) work seamlessly in place of Google Maps. All that without having to use their back end. The APIs for doing that are already there since v1.
In other words, (1) developers could publish for years alternative implementations, with any back end that allows that in it's TOS (though Google's doesn't) and (2) this was always possible.