jmercan

No matter the situation, no good can come from hatred. The RfL situation has already come from anger and bad, derailed arguments.

Instead of having beef with a stranger online and comparing him to an alt-right figure (which is very much not okay) I think having a good faith reply to a good faith personal opinion will at worst do nothing and maybe result in something at best.

Focus your hatred to the injustice of the world instead.

edit: pronoun fix

Sounds like this is how my life will be like for a couple years if I get accepted :p

There is an upper bound in the number of private keys available even if it isn't an issue in practice.

You can target anyone's wallet in O(1) time, no proofs needed :^)

side note: I was 3 when the original GNOME file picker thumbnail issue was created. I'm (hopefully) graduating this term.

I gave GNOME a chance after 40 and personally I don't regret it the slightest, things just work in an intuitive way.

Though I will admit the only GNOME app I use is the image viewer and sometimes folders. My workflow consists of a couple terminals, a browser and sometimes binja. But unlike window managers, oddball programs like Vivado, Matlab, Zoom, etc. work well too.

I would say "Effective C" is a good book (and Robert is awesome) but personally I feel like I learned the most by writing and disassembling small quines under different compilers and flags more than anything else.

Also, reading through some codebases gave me good (and horrible) ideas and habits. However, C projects are usually messy and I am not sure whether recommending it would be helpful or just confusing. But I would say TenDRA, BearSSL, pkgconf, s6, kivaloo, apk-tools, libsodium, musl, OpenSSH and cosmopolitan libc are worth checking out.

Finally increasing my tiny understanding of architectures, memory models and decades of safety issues was significantly helpful as well.

Frankly, if you have to ask, just use a (system) CSPRNG.

People massively overblow the impact of the speed difference for most scenarios. Yes, A simulation running on a large scale etc. will probably need a statistically good RNG w/o any security properties but (say) a game generating a seed occasionally will not be bottlenecked by using a CSPRNG. I would say it is worth it just to not have any mental load and slightest change of misuse.

Also, if the salt part is for salting and hashing passwords, forget about the whole idea and use a proper password hash be it Argon2id, scrypt, PBKDF2, whatever. It doesn't really matter which one and ideally a library should have chosen one of the algorithms with good parameters and nonce generation.

(I know Argon2 calls its nonce a salt too but that is irrelevant. It should come from a CSPRNG)

Personally I feel like shrinking images by guessing unused parts is an a good way to have an image explode in your face randomly in the future. (Probes and heuristics missing critical but rarely used parts and more) Also wouldn't it hurt reproducibility? Temporary runtime monitoring doesn't exactly sound like a deterministic metric.

A containerizable project probably has its requirements known and well-specified? I think building on top of a base with a smaller unused surface is a better idea than using analysis that might backfire. These days I am using apko + melange for my personal images and they are super neat.

From what I see, most Wayland aware applications have converged on using PipeWire (through XDG Portal) for screen sharing.

Personally I use PipeWire anyway but I'll admit telling people to replace more of their setup as a solution isn't very nice.

Also there might be oddballs like how Zoom used to use the GNOME screenshot API for a while.

I had to do my first two internships in office (started before the vaccine rollout reached my age group, eek) and my experience was pretty similar to what you said. I was given some time in the beginning to get familiar with the codebase but not much mentorship.

Most questions I could only get an answer from was about business requirements because they were either too busy or didn't knew much more about the part I was working on.

Not sure if my situation is usual though, even for interns after COVID started.