Lambda

Out of curiosity, what is the original?

I think self hosting the proxy with the services at hobbyist scale mitigates most of the security risks. The single point of failure risk is another matter. I once had to effectively reverse-hack my services by uploading a Jenkins test job through an existing java project to regain access. Ever since then, I maintain a separate ddns address that’s just used for emergency ssh access.

I believe it stands for Free/Libre Open Source Software. I think the idea is to explicitly indicate both free as in beer and free as in speech. However, to me it just sounds like throwing in a romance term for the sake of it. But maybe I’m just ill versed on the whole free/libre divide?

Sadly front end, like “High Level” is a very relative term. For example, in compiler design, the bit that parses code is called the “front end” since the “back end” is what emits machine code. I think that’s what they mean here, the “front end” that understands D3D8 code has been added, presumably there is also a “back end” that converts the parsed/analyzed D3D8 code into valid opcodes for consumption by GPU/CPUs.

In the other direction, a UI/UX is sometimes called a “back end” when it is part of a more complex embedded project where physical controls are the “front end”.

That would be an excellent idea. But I feel like an even broader community should be created. Like a generic book club, but for code bases! Could even have a small handful of different code bases on the go at a time. I’d love to get to know lemmy’s, but also e.g. neovim, or even unciv :)

Maybe one day it could even start tackling Moby Dick!

If you read the linked document, it outlines how reverse engineering may fall under a certain level of fair use, e.g. for reasearch and/or backup/archival purposes.

It really isn’t as clear-cut as it seems at first.

Wait until you learn about the shell specific /dev “files” like /dev/udp and /dev/tcp (which can send/recv IP traffic as if from a file)!