It's not different on Linux, every App can access any key in kwallet. To make this not possible the os would need to generate some kind of unique app id that can access only what it stored. This would probably result in a lot of lost passwords for normal users.
hashes by definition are not reversible. you could store a timestamp together with a hash, and/or you could include a timestamp in the digested content, but the timestamp can’t be part of the hash.
Sure they are. You could generate every possible input
Depends entirely on what you mean by reversible. For every hash value, there are an infinite number of inputs that give that value. So while it is certainly possible to find some input that hashes to a given value, you cannot know which input I originally hashed to get that that value.
that's why they're taking the dual-availability approach, with a separate 'mini' edition. it's easy to perform a progressive migration without messing with the package manager.
consumers uninterested in the 'mini' edition don't have to bother with that part.
but, the benefits of the 'mini' edition are so drastic for tree-shaking that it was driving development of alternatives - zod had to either do it (and benefit), or deprecate.
Was just looking at their release strategy. This is being handled by people that have experienced the hell that is dependency management in the JS ecosystem. Kudos to them.
yeah, but they do nothing to stop a locksmith in a fugue state from rekeying all the bolts to match the neighboring property and vice-versa, and then the realtor can walk right in, and you're locked out!
You’re proving the other persons point - the reason why the a thief doesn’t trivially pick locks isn’t because of the lock, it’s because it’s illegal and there’s a consequence.
The point of a lock is that it's something to break. That takes skill and visible equipment. The more skill yoo require the more likely the smart guy would do better things to earn money than crime. the more visible equipment the easier it is to track.
PR staff will talk about the insurance liability and mandated action to improve infrastructure (wildfires keep starting on power lines and then burning down cities) but it's hard to look away from the record profits
My impression was that the California utilities were being operated in revenue extraction mode for decades and prioritized paying shareholders over infrastructure maintenance leading to the crisis situation we are in today. The enormous costs today are due to the need to keep paying owners as well as catching up on the deferred maintenance, and in classic fashion the owners are still gobbling up most of the money and starving the operations budgets.
PG&E is guaranteed a rate of return, meaning its profit margin is basically state-guaranteed. A large share of blame falls on CPUC and the structuring of the utilities. CPUC must decide whether they approve of rate before pge implements them, and I think it almost always does.
I'm by no means excusing pge, they were pretty clearly negligent and failed to meet their obligations. But it's a state-backed operation, which pretty much always means less punishment for failure to operate effectively.
No. Capital expenditures are profit (or really, count towards earnings).
They're long-term investments in fixed assets, not expenses that get subtracted out when calculating net income. You're just swapping cash with assets of equivalent value, so profits don't change.
I'm not sure how PG&E would possibly not increase their profits if they got a rate increase meant to cover infrastructure investments. If they spend 100% of that increased revenue on infrastructure, then 100% of that counts towards profit - not in the future - immediately.
It's radicalizing as a twenty something who hasn't had social media in over a decade. Almost everything revolves around it or some friend Discord server. I hate it.
Don't worry by late 20s all that will quiet down in your friend group as people "adult" themselves into their boring 30 year old years. Tale as old as time.
They needed to have proper defaults and they needed to let their social network grow organically and they needed to have an actual sane, proper, feed https://news.ycombinator.com/item?id=14147719
There's a reason everyone is on Facebook (one reason is that everyone is on Facebook): Myspace legitimately shot themselves in the foot (I guess Friendster too by lack of proper site performance, even though it was cleaner) by having 'messy' pages. There's real value in being able to find the people you want/need to find by their real names (except, Google, maybe don't you know, hijack people's Youtube accounts in order so that they use Google+)
But then Facebook introduces shifting privacy settings, tagging without permission, not giving people control over how information is displayed generally
I understand it's about beating the competition and about growing and 'connecting the world' but some companies' DNA is set a certain way from the beginning https://news.ycombinator.com/item?id=1692122
...as demonstrated by the analogy in the original post here, where he explains the concrete concept of knitting stitches by reference to the much more abstract concept of garbage collection in computer programming!
on linux that’ll be kwallet or something, on mac it’s the keyring. it’s as secure as your password manager
edit: okay, you’re right, on windows it’s useless lol https://www.electronjs.org/docs/latest/api/safe-storage
> [on Windows] content is protected from other users on the same machine, but not from other apps running in the same userspace.
reply