You just have to wait the correct number of milliseconds until it becomes public information, then execute your trade. I'll bet someone has figured out the delay to allow enough time for some model or another to run. All nice and legal, just like how the two term restriction only applies to consecutive terms.
Something like that might deter high frequency traders who are basically exploiting noise. This is different. It's advance insider access to announcements that cause real changes. Well, that and the usual Trump noise, but even that usually takes well over 24 hours before it's obvious TACO.
If Apple wasn't able to keep their critical employees from jumping ship, then that's really on Apple for not recognizing or being willing to retain their employees at market price.
And now, by suing a bunch of former employees, they're giving employees who might be thinking about jumping ship a reason to pause. Whether Apple wins or loses the lawsuit, Apple wins.
So the UK is doing a great disservice to citizens of all countries, not just their own, by pushing on this.
They know what they are doing. The UK government has never believed in privacy rights. They know they're doing a disservice to everyone. They don't care.
And the only rational answer is to cut them off. No more iCloud storage for anyone residing in the UK. And for anyone else, immediate denial of access from the minute you set foot in that country to the minute you leave. This is the only reasonable option.
E2EE is really a dog and pony show, not real math, because the apps we install are all opaque and built by opaque build systems we inherently trust, whose vendors can insert a new backdoor any time they want.
And ultimately, this is the reason why Cloud storage shouldn't even exist. The minute you depend on someone else for storage, you can't completely 100% guarantee that your data is not in someone else's hands. If you store it on hardware you own, not built by the company that sold the backup software, then people will be able to verify that data is getting pushed to only a single destination, and if they started cheating and sending it to two different services, folks would likely notice. It's not perfect, but it makes back doors a lot harder to pull off without detection.
We need Time Machine for iOS, backing up over encrypted SMB to servers on our home network that we control. Fix that gap, and none of this matters anymore.
Right, lots of institutions send PDFs specifically because you can lock the text, provide specific form entry boxes, and get a reasonably secure signature. All of which are features of PDF, which is an open standard.
They don't send you a Word document which is arguably not an open standard because Word doesn't actually conform to it's own standard.
AI companies want quantity. If they wanted old, rare books they'd download the public domain copies provided by everyone from the Internet Archive to Google.
Fans don't like big camera drones flying around in front of the action they paid ridiculous prices to sort of see. Stadiums are also both big and loud.
One small book seller said that in April,
It's right there. The last story on Slashdot about this was an ad from a company trying to sell books to AI companies. It makes a good story. Ad in some credulous people who suppy their own adjectives like "exponential" and there you go.
Probably a few (as in count-on-one-hand) companies are buying bulk books, one copy of each.
Because nobody was every "first" on any land.
Are we talking Wheel of Time, Battlestar Galactica or some version of Hindu or Buddhist infinite cyclic time?
Hawaii is in the middle of nowhere. Finding it is a very long shot that seems to have happened only twice. By the best evidence we have, Hawaii was first settled by Polynesians around a thousand years ago and stayed pretty isolated up until James Cook stumbled upon it in 1778. The queen of Hawaii was overthrown in 1893 by US marines and US fruit growers, and annexed by the US in 1898.
It didn't start with Trump. The US has a lot of enemies and sometimes has difficulty distinguishing between a dispute with a competing nation and individual scientists from that nation. Trump definitely made it worse though.
Astra correctly answers all 10 questions in the $2000 lightning round!
And now on to the final round. To win $32,000 cash, a brand new Oldsmobile Vista Cruiser, and an all-expense paid vacation for two to Puerto Vallarta, all you have to do is answer this single question to the satisfaction of our judges:
The Riemann Hypothesis: True or False?
I smell a rat.
Not sure anyone is having to provide an incentive. While in small quantities, old models of Chromebook might cost as little as $200 on sale, chances are good that schools are spending more like $400 to $500 on average for their devices.
At just $600 for the Neo (the current educational price), the cost difference is minimal now. And if your teachers are already using Macs, that's one fewer platform to support. And if the hardware lasts longer (to be determined), then that could easily make up the remaining cost difference.
I agree that it's a frustration to only have access to a single account at a time (in this case, an Apple ID), but I'll point out that this is the use case for probably 99.9% of their users. And there are some exceptions to this rule: Apple does have a mechanism in place that lets you use one Apple ID for music and a different one for their various App Stores, for example. However, this still doesn't let you use two Apple IDs for a single service at the same time.
I think the reasoning behind this is pretty solid: the UI problems involved in allowing multiple simultaneous logins to the same service are extremely complex, and if you're only looking at a frustration for a vanishingly small percentage of your userbase, it doesn't make sense to make it more complex for everybody.
It really isn't complex. Google does it just fine. You have an account picker in the upper right corner, and you choose which account you're using to interact with that app. No big deal.
Having a mechanism to use one account for music and a different one for app stores? Now that's complex. That's adding special-casing for each app that needs to handle a separate account, instead of designing the auth system correctly to support multiple accounts to begin with. It's almost always easier to do it right than to add a bunch of special-case workarounds everywhere.
I also disagree with the claim that 99.9% of users only have one iCloud account — not because it isn't currently true, but because it is true only tautologically. If the system is designed so that no person can meaningfully use more than one account, then no one is ever going to create or attempt to use more than one account. What this means is that no businesses will ever use iCloud accounts for their internal messaging system, etc. Apple is basically shutting themselves out of the business ecosystem altogether by design.
They've designed the system in a way that makes what you're saying true, so of course it is true. But that doesn't mean that 99.9% of users would not *benefit* from it not being true. In an ideal world, iCloud would compete head-to-head with things like Office 365. They have the tech, but limiting it in ways that make it useless for business purposes means they aren't actually competing.
The root cause comes from these twelve words:
Since only one primary account can be signed in at a time
Authentication systems that allow only a single signed-in account are defective by design. Approximately 100% of all people have more than one account that they need to be signed in with.
I have half a dozen Google accounts for specific purposes — one for work, one for personal, one for electronic music tablets to which multiple people share physical access, a couple of old domain-specific accounts that got converted from free work profiles, and I'm probably forgetting some. Not all of these are useful, but if I could not have continuous access to work and personal, it would be a tremendous pain in the backside.
And encouraging people to merge profiles like that is nuts. It all but guarantees leaks. A confidentiality agreement typically protects things you learned in the scope of your employment, but after you are employed, if they continue to send you confidential information, there's a decent chance that you aren't under any legal obligation to keep that secret.
This is just a really bad way to do things, driven by a fundamental flaw in their architecture. And it doesn't just cause problems for Apple. It causes problems for their customers as well. I can't have a separate iCloud account for my work. I have to use a Google account. And more than that, when I hit the maximum number of AirTag devices (which I'm about to reach), I can't add additional iCloud accounts. I'm hard-capped at a single account.
While we're at it, the limitation of a single user per iPad stems from the same defective design process. All of those sorts of 1:1 mapping decisions between accounts, users, and devices need to be fundamentally rethought, because they were always a mistake. Maybe now that Apple is being bitten by it, they'll finally do the things that users have been asking them to do for the last decade. Bonus points if they lose their lawsuit because of a lack of a modicum of care on their part, because that just might be enough to wake the sleeping giant and get them to fix this mess.
BC search and rescue has lots of very good reasons why they don't charge. It's a public service like police, fire and health care.
Old programmers never die, they just become managers.
