How did these work? Files were public, or just too-simple passwords?
Mostly people learning enough about the target to social engineer the password reset process and answer the "secret" questions.
With Google it's all [s]private [/s] google can look at it with machines to sell you things by default I think
😉
Private by default on Apple too.
Private by default on Apple too.
The default upload may be more of the issue, if it's online then expect it to be hackable.
Tricky one for companies though. The flip side of the "online by default" is when a customer is in tears cos they broke their phone and it's the only place photos of their child are stored you can give them a new one and they're all restored by magic (because normal people don't backup).
So by some measure, it probably helps more people than it hurts, it's a trade off someone somewhere has to make. It'll always be wrong for some people though.
With Google it's all private google can look at it with machines to [s]sell you things[/s] advertise things to you that you might actually want instead of random crap by default I think
Do people still plug storage in? For me it's all networked really, I guess if your hard drive is glued in and you can't upgrade it you might need one.
Why wouldn't they? Not everyone's storage needs are the same.
I use 2 thunderbolt (2-4 HD's in each) drives one raided for fast in/out of video (native not proxies) and another as a mirrored back-up that backs up every 15min whatever I tell chronosync the current shoot is. I need to move 10-100gb around at a time and often so don't want to wait for that or have the machine slow down while it's doing it.
And as for upgrading, no current drive is big enough for my needs so being able to change the drive (or not) is a moot point.
Main machine is only 500gb but I only ever keep the current shoots on it that I'm working on then they get removed, most people just keep filling their machine up to the brim then wonder why it slows down.
most people just keep filling their machine up to the brim then wonder why it slows down.
Why would that be? Are 1's heavier than 0's, then?
Why would that be?
Hard to say if this is a serious question, or if you're testing MrSmith....
I do know the answer though, how many points do I get? ;-P
Well,
If by 'full to the brim' we're talking about applications with services and components which run all the time taking up RAM then yes, that can have a performance impact.
But so long as there's sufficient space free for the OS to have a bit of elbow room to do its thing, a computer full of [i]data[/i] is just as fast as one that isn't (for practical purposes anyway, so long as we're not splitting hairs over things like seek time), the idea that you can somehow delete your music collection to speed up your machine is a myth.
If space on your system drive is critically low or non-existent however, that can give you a really bad day.
IA > are you thinking of something I've missed?
Well, the definition of "sufficient space" here is key.
On a spinning platter (where are we? A time machine to 10 years ago? 😉 ) the seek time and transfer rate suffers, not just because of where you are on the disk but also inevitable fragmentation. There are benchmarks somewhere (i forget, it was years ago) that I was looking at when I last bought a spinning disk laptop, showing that basically for a given data volume a larger 5400rpm disk was faster than a 7200rpm disk. Though of course there are platter density issues at play there too....
On an SSD it depends on the controller, but writes often get a lot slower and trimming time can increase. In particular you can suffer annoying jitter in access time which can be infuriating*.
I'll concede it probably doesn't make a noticeable difference to the sort of person likely to let their drive over fill though.
*I know modern controllers in theory solve these problems with various tricks, but in practice they don't. Makes a noticeable difference to my work, which is I'll admit niche (robotics/AI R&D), but still.
IA > are you thinking of something I've missed?
Scratch disk space if you don't have a separate one.
