According to a different source shared by @giriinthejungle, the attorney who has taken the case is suing the entire operating unit and expects whoever instructed the girl to drill the hole to be liable for assault. That is also the estimation of the chief regional patient attorney, provided the incident happened as reported by the media.

The neurosurgeon as well as one other doctor have already been let go by the hospital.
Police have not yet charged anyone, their investigation is still ongoing as of the time of the article (2024-08-26).

The point is not the difference between a fake memory and a real one (let’s grant for now that they are undistinguishable) but the fact that positive experiences are worth a lot more than just the memories they leave you with.

I may not know the difference between a memory of an event that I experienced and a memory of an event I didn’t experience. Looking back on the past, they’re the same.
But each moment of pleasure that I only remember, without having experienced it, was essentially stolen from me. Pleasure is a state of consciousness and only exists in the present.

Honestly, their comment reads like copy pasta. That first paragraph is chef’s kiss.
I initially thought they weren’t being sincere, something something Poe’s law…

(’ v ')/

The main difference is that 1Password requires two pieces of information for decrypting your passwords while Bitwarden requires only one.

Requiring an additional secret in the form of a decryption key has both upsides and downsides:

• if someone somehow gets access to your master password, they won’t be able to decrypt your passwords unless they also got access to your secret key (or one of your trusted devices)
• a weak master password doesn’t automatically make you vulnerable

• if you lose access to your secret key, your passwords are not recoverable
• additional effort to properly secure your key

So whether you want both or only password protection is a trade-off between the additional protection the key offers and the increased complexity of adequately securing it.

Your proposed scenarios of the master password being brute forced or the servers being hacked and your master password acquired when using Bitwarden are misleading.

Brute forcing the master password is not feasible, unless it is weak (too short, common, or part of a breach). By default, Bitwarden protects against brute force attacks on the password itself using PBKDF2 with 600k iterations. Brute forcing AES-256 (to get into the vault without finding the master password) is not possible according to current knowledge.

Your master password cannot be “acquired” if the Bitwarden servers are hacked.
They store the (encrypted) symmetric key used to decrypt your vault as well as your vault (where all your passwords are stored), AES256-encrypted using said symmetric key.
This symmetric key is itself AES256-encrypted using your master password (this is a simplification) before being sent to their servers.
Neither your master password nor the symmetric key used to decrypt your password vault is recoverable from Bitwarden servers by anyone who doesn’t know your master password and by extension neither are the passwords stored in your encrypted vault.

See https://bitwarden.com/help/bitwarden-security-white-paper/#overview-of-the-master-password-hashing-key-derivation-and-encryption-process for details.

This works as a general guideline, but sometimes you aren’t able to write the code in a way that truly self-documents.
If you come back to a function after a month and need half an hour to understand it, you should probably add some comments explaining what was done and why it was done that way (in addition to considering if you should perhaps rewrite it entirely).
If your code is going to be used by third parties, you almost always need more documentation than the raw code.

Yes documentation can become obsolete. So constrain its use to cases where it actually adds clarity and commit to keeping it up to date with the evolving code.

It’s a big deal IMO, particularly because at login it doesn’t do the same. From the user perspective, your password has effectively been modified without your knowledge and no reasonable way of finding out. Good luck getting access to your account.
When a bank does this it should be considered gross negligence.

If their password was actually good (18+ random characters) it’s not feasible with current day technology to brute force, no matter how few PBKDF2 iterations were used.

Obviously it’s still a big issue because in many cases people don’t use strong enough passwords (and apparently LastPass stored some of the information in plaintext) but a strong password is still good protection provided the encryption algorithm doesn’t have any known exploitable weaknesses.

There’s no need for something that complex.
Someone with access to a chess engine watches the game and inputs the moves into the engine as they’re played. If there’s a critical move (only 1 or very few of the options are winning/don’t throw the game) they send a simple signal to let him know. That can be enough to give you an advantage at that level. If you really want, you could send a number between 1 and 6 to represent which piece the engine prefers to move, but it’s likely not necessary.

That said, all the evidence he actually did anything like that is at best circumstantial (mostly statistical evidence supposedly showing how unlikely his performance was given his past performance and rating at the time, as well as known instances of past cheating by him - though the only confirmed ones were several years ago when he was still a kid and online rather than in person).

Extra steps that guarantee you don’t accidentally treat an integer as if it were a string or an array and get a runtime exception.
With generics, the compiler can prove that the thing you’re passing to that function is actually something the function can use.

Really what you’re doing if you’re honest, is doing the compiler’s work: hmm inside this function I access this field on this parameter. Can I pass an argument of such and such type here? Lemme check if it has that field. Forgot to check? Or were mistaken? Runtime error! If you’re lucky, you caught it before production.

Not to mention that types communicate intent. It’s no fun trying to figure out how to use a library that has bad/missing documentation. But it’s a hell of a lot easier if you don’t need to guess what type of arguments its functions can handle.

The point is that you’re not fixing the problem, you’re just masking it (and one could even argue enabling it).

The same way adding another 4 lane highway doesn’t fix traffic long term (increasing highway throughput leads to more people leads to more cars leads to congestion all over again) simply adding more RAM is only a temporary solution.

Developers use the excuse of people having access to more RAM as justification to produce more and more bloated software. In 5 years you’ll likely struggle even with 32GiB, because everything uses more.
That’s not sustainable, and it’s not necessary.

I think they meant the only language we transpile to for the express reason that working with it directly is so unpleasant.

Java is not transpiled to another language intended for human use, it’s compiled to JVM bytecode.

People don’t usually develop software directly in the IR of LLVM. They do develop software using vanilla JavaScript.

You don’t need to correct something everyone already knows is an exaggeration (and I agree it doesn’t seem very socially aware to do so) but this is a political discussion on the internet, so

1. Everyone does not know the original figure is an exaggeration, especially by how much
2. Providing the actual information ads value to the conversation and in this context this is more important than whether the commenter comes off as smarmy or socially inept

What if they said “Hey I know you’re being hyperbolic, but for anyone who’s interested, here’s the number estimated by experts…”?
The only difference here is tone.
 

I’m not sure why they only shared numbers for minke whales, as these don’t seem to be hunted anymore in Iceland in contrast to fin whales, whom the article was about.

Global fin whale population was estimated in 2018 by IUCN to have been around 100000.
https://www.iucnredlist.org/species/2478/50349982#population

Yes, correcting hyperbole with relevant information is bad, actually.

As always, the dose makes the poison.
A common scenario is people picking the wrong species and then not just eating a small bite, but cooking an entire meal and eating that.

A small bite may not kill you, but just one mushroom (50g) can be enough to do it.

There are some toxic mfs out there and they can be mistaken for edible lookalikes by inexperienced foragers.

I’d say generally speaking it’s more likely that issues stem from extensions than from Firefox itself, so maybe try looking into that.

Btw tab reordering is only missing for private tabs on the latest ff on Android.
Unfortunately there is still no acceleration when reordering so the ux is not great when you have many tabs.

Many of the programming languages that are regularly the butt of everyone’s jokes don’t just allow you to use them badly, they make it easy to do so, sometimes easier than using them well.
This is not a good thing. A good language should

• be well suited to the task at hand
• be easy to use correctly
• be hard to use incorrectly

The reality is that the average software developer barely knows best practices, much less how to apply them effectively.
This fact, combined with languages that make it easy to shoot yourself in the foot leads to lots of bad code in the wild.

I haven’t used a different browser in a good while, so I’m not sure that these issues don’t exist elsewhere, but here’s a few:

For a very long time after the rework, reordering tabs was not possible. Only recently was this added again. But there seems to be no acceleration, so moving an old tab to the front takes forever. Even worse, this feature is still not available for private tabs (since you can’t select those at all).

Quite often when I switch to the tab overview, it doesn’t automatically scroll to my current tab so I need to do that manually.

I’m also not a fan of the “jump back in” view that shows up every so often instead of the content of my tab. Why they would assume I’m interested in anything besides what I intentionally opened is beyond me.

Creating a new tab is more cumbersome than it needs to be. I think you were able to do that by scrolling to the right on the address bar of the rightmost tab. A dedicated button would be even better.

I think it’s a great browser, and pretty much the only one I use, but in my experience everything does not work perfectly.

Unsurprisingly, tools for the migration of basic stuff like subscriptions and block lists have already been developed by the community.

https://lemmy.world/post/1060796 (haven’t tried using it myself yet, but it’s probably much quicker than manual if you have a lot of subscriptions to migrate)

Oh neat, a real whoosh in the wild, on Lemmy!

On a more serious note, vim is one of the most initially unintuitive commonly used pieces of software I’ve encountered.

Sure, if you put in a little time and learn it, it’s not rocket science. But that seems like a weird standard for an essential tool used for one of the most common computing tasks of today.

In response to your initial question, obviously it’s a meme. But like most good memes, it’s born out of a common* human experience. What do you think is the most common reaction when someone is thrown into vim for the first time? My guess is “what’s this?” or something similar, followed very soon by “how do I exit this?”. And the answer is, by modern computer users’ standards, quite arcane.

IF you are somewhat familiar with the Linux terminal, you’ll try CTRL+C and IF you’re paying close attention you will notice that vim is giving you a hint. But if it’s your first time interacting with vim, chances are at least one of those conditions is not met. So now you’re stuck. And after an optional small moment of panic/disorientation, you google “how to exit vim” (provided you were at least lucky enough to notice/remember what program you’re in) => a meme is born.

Exiting vim is almost like a right of passage for fresh Linux enjoyers. It’s not a hard task but it can seem daunting at first encounter, which is humorous given that quitting a program is normally such an easy thing to do.

One more note, there is a group of people who will encounter vim quite unexpectedly and unintentionally: Windows users performing their first commit using git bash. They won’t even know they’re in vim, they’re dropped directly into edit mode and there’s no instructions for confirming the commit message, much less how to exit/cancel the operation.