Hey now, some of us have standards.
We have shitty python scripts
Hey now, some of us have standards.
We have shitty python scripts
No, I’m arguing that the extra complexity is something to avoid because it creates new attack surfaces, new opportunities for bugs, and is very unlikely to accurately deal with all of the edge cases.
Especially when you consider that the behaviour we have was established way before there even was a unicode standard which could have been applied, and when the alternative you want isn’t unambiguously better than what it does now.
“What is language” is a far more insightful question than you clearly intended, because our collective best answer to that question right now is the unicode standard, and even that’s not perfect. Making the very core of the filesystem have to deal with that is a can of worms which a competent engineer wouldn’t open without very good reason, and at best I’m seeing a weak and subjective reason here.
The reason, I suspect, is fundamentally because there’s no relationship between the uppercase and lowercase characters unless someone goes out of their way to create it. That requires that the filesystem contain knowledge of the alphabet, which might work if all you wanted was to handle ASCII in American English, but isn’t good for a system which needs to support the whole world.
In fact, the UNIX filesystem isn’t ASCII. It’s also not unicode. UNIX uses arbitrary byte strings, with special significance given to a very small number of bytes (just ‘/’ and ‘\0’, I think). That means people are free to label files in whatever way they like, and their terminals or other applications are free to render them in whatever way seems appropriate, without the filesystem having to understand unicode.
Adding case insensitivity would therefore actually be significant and unnecessary complexity to add to the filesystem drivers, and we’d probably take a big step backwards in support for other languages
That’s going to be a problem whatever solution you come up with, because of the federated nature of the lemmy system.
There’s no central authority to hand out usernames, so if two people sign up to different instances with the same username, any design which didn’t attach instance name to each username would fail. The only way around it would be for each instance to contact every other instance which exists, including the ones which haven’t federated yet, and negotiate ownership of the new username, and that’s just not possible
The crew of Apollo 13 weren’t really stranded, as such. They were far from home and not sure if they had the means to get home before the supplies ran out, which is a different problem
That’s deeply unwise. Nothing you cobble together yourself using a raspberry pi is going to be up to automotive safety standards.
Anyone who sets up one of these has nobody but themselves to blame when it misbehaves and gives them incorrect information, or no information, or starts flickering distractingly, and they get done for speeding/hit a pedestrian/fail whatever inspections the law requires in their part of the world
Even that wouldn’t prove anything. You have to start a whole new conversation (ideally on a separate account so that OpenAI can’t play any clever games to make it look smarter than it is) and ask it there. Without doing that, the model will still have the context in which you told it to begin with
Because you might accidentally do something which breaks the system, or you might run a program which does something malicious without your knowledge.
By gating dangerous (or protected for any other reason) commands behind sudo, you create a barrier which is difficult to accidentally cross
Why shouldn’t they? Nose and toes do rhyme.
It’s possible there’s some accent I can’t immediately think of where they don’t, but all of the accents which come to mind use the same sound in both cases
There’s no need to leave earth, just lift it into a medium earth orbit. There are literally thousands of kilometres in between low earth orbit (where there are lots of communications, spy, navigation and weather satellites) and geosynchronous (where there are lots of communications satellites), and outside of those two there’s virtually nothing there
It’s a matter of perspective. To someone who’s job is to write the system which interprets ASM, ASM is high level
You declaring a debt isn’t meaningful because you don’t have legal authority to do so.
A licence statement is describing in what way you’re granting permission for something you do have the right to control, which makes it meaningful
Nah, we’re alright. I don’t think anyone has clearly defined the requirements of earth citizenship, we can assume it’s like Ireland who hand it out like candy
No it wouldn’t. Whoever touched it last is responsible for it, that’s entirely consistent with the metaphore
I’m pretty sure it means exactly what it says, but you lot are all misreading it.
I interpret it as “all rights, except the right to commit, are reserved” (which doesn’t mean you surrender the right to commit, but rather that it’s the only right you aren’t depriving everyone else of)
In principle they could have pulled out slightly, if there’s jostling and tiny movements in skull then you’d expect them to work loose over time if they’re not securely anchored
The default is as long as it is because most people value not losing data, or avoiding corruption, or generally preserving the proper functioning of software on their machine, over 90 seconds during which they could simply walk away.
Especially when those 90 seconds only even come up when something isn’t right.
If you feel that strongly that you’d rather let something malfunction, then you’re entirely at liberty to change the configuration. You don’t have to accept the design decisions of the package maintainers if you really want to do something differently.
Also, if you’re that set against investigating why your system isn’t behaving the way you expect, then what the hell are you doing running arch? Half the point of that distro is that you get the bleeding edge of everything, and you’re expected to maintain your own damn system
The question you should be asking is what’s wrong with that job which is causing it to run for long enough that the timeout has to kill it.
Systemd isn’t the problem here, all it’s doing is making it easy to find out what process is slowing down your shutdown, and making sure it doesn’t stall forever
Also, it’s probably possible to fix the partition so that it’s as big as it used to be. It’s likely that some of your data is corrupted already, but the repartitioning won’t have erased the old data except here or there where it’s written things like new file tables in space it now considers unused
No, basically. They would love to be able to do that, but it’s approximately impossible for the generative systems they’re using at the moment