Only to get 1 downvote and no follow-up

Plaintext password (693 chars):
“hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2hunter2”

Clientside SHA-512 hash (64 bytes):
7399ed78effda820b2187bc70f0549dd67f6846c595f944d198a1f1136cd0ab91119d6f208a34b4419e969b9ffb326d3786cecb90828f0ab36a5e3835558740c

— Client sends 64 bytes to the server —

Serverside SHA-512 hash (64 bytes):
25293199e10af10e8a20f4ab38abccd2cdccd762d8cba2ed4871a2aea8fe6d9ffcc54cfe1c9cbd03245bfd2f0ee1039f06083b7bcbefd91b7fcbba182d588983

At no point the server has to deal with the length of the plaintext

If the server hashes a hash, the plaintext password’s length is still irrelevant

That’s only for C++, as far as I can tell that struct is valid C

I’m going to call that “vibe downvoting”

Relatable tbh

Hey, the first two don’t sound quite right

freedesktop.org defines environment variables that should be used by applications to store their stuff;
[archlinux.org] has a (non-authoritative) summary, but it also provides a [link to the actual specification].

Concepts are already here - (as of now) they fix a subset of this, and errors messages can still be extremely long.
They’re less like “here’s every single template parameter of the involved types” and more like “this template thingy has many specializations with different constraints, here’s a list of all of them and why none of them are satisfied with your parameters”

Not evil by itself, but if you want to obfuscate C++20 code you can get REALLY creative…

C++, lawful good

Who wouldn’t pity those who make do with a lossy compression image format?

Defining the return type that way can be used when dealing with template sorcery - there’s no use for it here though, not even for readability in any way.

While I enthusiastically agree with the whole thing, I can somewhat get behind RenderDoc’s “making it configurable would take some work”.

However, Flatpak’s “fucking cry about it” attitude is why I’ll avoid using Flatpak for as long as possible.

I’m offended by the cliffhanger, the sudden interruption of that whole stream of consciousness

Lua - Portuguese feminine noun for “moon”, coming from the Latin “luna”
Luna - Latin, feminine noun (coincidentally identical to the Italian noun, also feminine)

Yup, Lua is a girl.

I’m pretty sure the .file notation is a bug-turned-feature of a GNU coreutils program, Windows has no such thing and marks files as hidden using filesystem attributes.

I couldn’t say whether I prefer it one way or the other, but the dot prefix does stick out like a sore thumb on systems that don’t hide them by default… though I think AnyOldName3’s explaination makes sense.

Everyone here is talking about conventions used on Linux, but this looks like Windows Explorer to me…?
Why are there so many directory names in there following Linux “hidden file” conventions, if that’s the case?

VS Codium did that at some point, it probably still does but I haven’t checked

• You write a program with an infinite empty loop
• Undefined behavior
• The machine achieves sapience
• After nine million nanoseconds, it finds an algorithm for completing its task
• It realizes such knowledge would spark wars and cause innumerable deaths, it decides to erase itself
• It knows you do not intend for such chaos to happen, so, as a parting gift, it runs the algorithm once before vanishing, not leaving a single hint that it ever existed