tdknox

thrang said:

Velops lets you create your mesh with a wired backbone like Apple's routers...other may also, but I find this important.

Eero does also.

I used to live in the apartment complex literally across the street from the new campus (Look at any map of the new campus. See the bottom left corner where it's not part of the campus? That's the apartment complex). It boomed my rent prices so much I had to move.

loopless said:

Related to this...

Can someone explain to me why when I ask Siri in iOS 10 while I am driving ( I do not have car play)
"Hey Siri, give me directions to home"
And Siri says " I cant help you while you are driving"?
Why cant 'she' start voice directions?

"Hey Siri, take me home" has always worked for me.

melgross said:

The only thing that bothers me is the file copy. When I copy a file, I'm doing it for a reason. I want an exact copy. If I alter one, I don't necessarily want the other altered. If one gets corrupted, rare, but it does happen, I want the other pristine one to replace it. I'm not sure how this will work.

its a reason why I'm not fond of de-duping. My copies are intentional.

I don't think you understand how this works.

1) Make a "copy". Yes, this is not a true copy. This points back to the original.

2) Make changes to the file, either the original or the "copy".

3) APFS will record the changes and only make the changes necessary to the appropriate file. And data not changed will be unaltered in either file, but there will be a list of changes made. 

So, to sum up, if you make a copy of a file and then change either file, the file that you changed will show the changes while the other file will not. In the meantime, data that is not changed between them will continue to be shared. But reading either file will result in the correct data being read.

How is this a bad thing?