At some point you have to assume some kind of knowledge though. If you have to explain everything from the basics, the moment a concept is slightly complicated, the blog gets thousands of pages long.
You don’t need to explain how an integer is represented in binary in memory in a blog post about atomic integers. Most people that read about atomic integers already know how integers are represented in memory.
Daily reminder to block every instance ending in @lemmy.ml
All the content you see there has been censored out of any criticism to china/Russia/north Korea. If you don’t look at the content that passed their censorship filter, their censorship loses all its power. Look at and support communities of other instances instead.
I once found a full pack of cigarettes on the ground at age ~10. I quickly figured out that lighting it on fire and using the cigarette to set off fireworks was so much easier than using a lighter. I didn’t even think of smoking it, I just left it lit on the ground and used it as a lighter.
I didn’t understand why my parents were so worried when they found out lol.
The investors know too. They just need to hype it up so the next is bigger than them and bail them out.
It’s a pyramid scheme for billionaires. They just hope they’re not at the bottom of the pyramid.
Same as NFTs and every other bubble where it was clear that it was a bubble
As a user of the internet. I don’t think I’ve ever done something in response to receiving an email from a product/service I don’t use.
The only marketing emails I read are about products I already use daily.
EDIT:
If what you want is to give resources to get started, the moment to do that is when signing up.
“Thank you for registering with our services, here are some learning resources that will help you getting started: <link>”
Good practice != Something that ensures security. As I said, it’s an even better practice to just host your own fork if what you want is security. The reason to use git hashes is mostly so you don’t have to trust the author following semver in there version number. It’s a matter of ensuring that your code will always compile, not a security feature.
Have you read the article? Your arguments derive from an assumption of “sha1 is mutable, sha256 is immutable”. First of all, every hashing algorithm is going to have collisions, that’s an unavoidable “feature” of hashes. And sha1 is in no way “mutable”, it takes a great amount of effort (and money) to generate a collision. Furthermore, those collisions are not arbitrary. You have to calculate them beforehand. As the article says: what is more likely? Paying 40k€ in compute time to generate a single collision? Or just paying an open source maintainer 40k€ to let you do 1 new commit that most people are going to download anyway?
I’ve never heard of anyone relying on git’s sha1 hashed for security
If someone has access to write to a repo you are downloading code from, and you don’t trust that someone, you shouldn’t be running the code in that repo.
The only “security” vulnerability is: I have audited and verified that the code in commit 05682ab36ca. And I will use only that version.
What you do then is: download that commit and store it in a local repo, and package it so you can distribute it to your clients.
Auditing external software is tremendous effort, even if it is open source. Using your local repo instead of downloading that commit from GitHub every time is very little extra effort in comparison.
And if you really need it. You can always hash with sha256 yourself and verify that the commit with that sha1 still produces the same sh256. So you can keep downloading it each time, just need to store the sha256.
standard pc
64GB of ram on a laptop
I tried to implement my own git from scratch. And when I got to choose a hashing algorithm, I reached the exact same conclusion as the author pretty fast.
The hashing algorithm doesn’t really matter as long as it’s good enough to prevent accidental collisions. And if there is a collision, it is extremely easy to check.
If you are about to create a new object and an object with that hash already exists, you compare the 2 objects. If they are the same, nothing happened. If they are different, you just found a collision. Throw some obscure error that will only be witnessed once in the lifetime of the universe and be done with it. Tell the user to change a single bit of the input and be done with it.
The purpose of object hashes in git was never to provide security. Security is achieved through other means.
But don’t turn on the “display seconds” in the clock option. That would be an energy and resource waste, as the clock widget would have to be redrawn every second instead of every minute! Also, here’s copilot. Talk to it, we need you to use it to justify all the resources we’ve wasted on it’s development.
It seems you’ve also seen a sphere being turned inside out
Feels so awkward to jack off in the shower. I much prefer doing it sitting in the toilet.
When I say special shampoo I mean it. Like the one time my dog got fleas so I used anti-flea dog shampoo just in case. It took forever.
She admitted it in court.
Not being found guilty for it doesn’t mean it didn’t happen.
If you’re at a carnival where one of the games is throwing axes at a board. And somehow a child suddenly teleported in front of the board after throwing the axe, you might not be guilty for it. But you still killed the kid.
Tbf, since I have done this some 2-3 times:
Some special shampoos require you to be sitting there for like 10 minutes until it does its thing. I thought it was safe since water was no longer coming out of the shower, I didn’t consider the high humidity environment.
Easy.
Replace “manager” with “prompter” and “employee” with “LLM”.
The manager told the employee to do something.
Afterwards, something bad happened.
Did the employee do what the manager told it to do. And the bad situation is a consequence of following those instructions? Yes -> manager’s fault. No -> employee’s fault.
Did the employee do something illegal (or against some other rule)? Yes -> employees fault
The thing requested was illegal to request (or against some other rule)? Yes -> Manager’s fault
Note that more than one thing can be true at the same time. So even if the employee does whatever the manager told it to do. If that thing was illegal to do, both of them are at fault.
If it’s the “manager”'s fault -> the prompter is liable
If it’s the “employee”'s fault -> the LLM company is liable.
Easy as that. It works like any other situation.
If any machine has been properly maintained and malfunctions, the maker of that machine is liable. If the operator was using a chainsaw to cut through concrete and the chainsaw malfunctions the operator (and whoever (if anyone) ordered the operator to do that) is liable.
CRTs did break. And they did suffer from burning.
Just buy a non-smart modern TV, you won’t need a replacement and it won’t connect to the internet.
It makes you almost qualified to answer why the damn printer won’t work.
Why do they express disappointment?
What they should express is criminal charges and an extradition request.
Nvidia is not paid 100% in cash though. If the bubble pops, they might not get paid even if they deliver the card.