True, that should have occurred to me. That’s what I get for not touching a compiler since the Christmas holidays started

That’s easy. The 2038 problem is fixed by using 64-bit processors running 64-bit applications. Just about everything built in the last 15 years has already got the fix

Using that fix, the problem doesn’t come up again for about 300 billion years

It is guaranteed, actually. US law imposes requirements on telecoms providers to support wire taps

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

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

Exactly, that seems like the reasonable reading of the statement to me

While we can all agree Trump is an ass, I think you’ve misunderstood this statement.

He’s not saying “it’s important that republicans don’t vote if we fail to solve the election fraud”, he’s saying “it’s important to solve the fraud, because otherwise next time republicans won’t be allowed to vote”.

He’s claiming that republican votes won’t be counted, or that they won’t be allowed to place a vote at all, because the democrats will have rigged the system and/or deprived them of the right to vote

Fair enough, I didn’t consider compute resources

The actual length of the password isn’t the problem. If they were “doing stuff right” then it would make no difference to them whether the password was 20 characters or 200, because once it was hashed both would be stored in the same amount of space.

The fact that they’ve specified a limit is strong evidence that they’renot doing it right

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

True, I didn’t consider that. He’d still have to convince them though, which would be easier said than done if he wanted to entirely disregard the constitution

No. The ruling seems to have said that he can do anything he likes in his capacity as president, and he can’t be convicted of any criminal offence for it. It didn’t say that the people around him would have to go along with it, or that they’d be immune from prosecution.

It also left convenient wriggle room for the court to arbitrarily decide what constituted “official” actions, rather than him doing something privately, so they’ve effectively granted themselves a get out of jail free card to decide case-by-case in the future

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