Forgot your password?
typodupeerror

Comment Re:Pretty simple (Score 1) 120

Easy to read "Prop 13 (1978)" between the lines, which is California specific. IIRC[citation needed], Prop 19 (2020) while eliminating inheriting the assessed value (Prop 58 (1986)) make it possible to transfer the assessed value to another property statewide (previously available only where individual counties had made agreements). Why Modoc isn't being bought up in order to transfer the assessments to Beverley Hills is a mystery.

The main impact of prop 19 is making it possible for the elderly to not be forced to move to another state if they decide to downgrade to a smaller home. It likely has minimal impact on people's ability to move closer to their jobs, because it is limited to people 55 and older, so less than a quarter of California's workforce qualifies for transferring the cost basis to a new property.

More to the point, the people most likely to change jobs are younger workers, and none of them qualify.

As for Modoc to Beverly Hills, the difference in market value is added to your assessment. So if you bought a $50,000 home in the middle of nowhere that has appreciated to $300,000, and you trade up to a $3 million home, your new tax basis value is $2.75 million ($3 million minus $300k plus $50k). So it really doesn't make much difference in that case, practically speaking.

Comment Re:Defective by design (Score 1) 50

Which doesn't really work as users routine confuse their accounts and upload files to the wrong account, and then confusion ensues when files are stored partially on a work account and on a personal account.

And that's when the corporate systems are configured to warn if you try to share something with or from the wrong account, and you shame the user into doing it right. Besides, this is usually only a problem for brand new users. Once you have a bunch of files uploaded to both accounts, you're not going to suddenly see the files from your personal account, and think, "Oh, this is where my work stuff goes".

It's only confusing if you have access to the same files from both accounts. And then, yeah, you'll get confused about which account is editing the file, but it's not as if it really matters in that situation.

Comment Re: If I were OpenAI... (Score 2) 16

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.

Comment Re:End of End-to-End Encryption (Score 1) 27

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.

Comment It's the crazy alphabet nonsense for me... (Score 1) 82

I was auto suspended because I quoted a 30 year old statement supporting the rights of gays and lesbians that made reference to "LGB communities". I was accused of Trans erasure or some other stupid bullshit.

I hope the stock price falls low enough for Elon Musk to buy it for a song.

LK

Comment Re:Who's providing the "incentive" to do this. (Score 1) 159

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.

Comment Re:Defective by design (Score 2) 50

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.

Comment Defective by design (Score 5, Insightful) 50

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.

Comment not really (Score 1) 84

I'm fairly sure at least one entire department at MS is tasked with making sure people don't switch to other formats, that despite on-paper "open" XML it remains incompatible and no competitor software can flawlessly read and write it.

So no, unless you can hire a dozen people full-time to counter that, you don't have a chance to break through that.

Slashdot Top Deals

Men love to wonder, and that is the seed of science.

Working...