Good question. I care only about POSIX compatible shells, so the escaping just follows the POSIX rules. In practice that means it works on any actually used system except windows, which is fine with me.
I was told you don't need to subscribe to the mailing list, but I've sent mailing list messages with patches, discussions on technical issues that were never accepted.
Bit annoying is that when companies ask for a portfolio, they often mean GitHub. Lot of non-technical hiring people I discussed this with were confused by the fact that there are other ways to contribute, like mailing lists.
What I find interesting is that the project claims MIT license, but if it is "almost entirely" AI generated, I am not sure it even is copyrightable. So either the licensing terms deserve some large disclaimers, or it is not "almost entirely" made with AI. Based on the name I assume it is your project, could you shed some light on which of those two options is correct?
I guess copyright laws treat AIs as tools. If you paint a picture with a brush it's also almost entirely "brush created", and still you can claim copyright for it.
If you (the company) send me a company laptop to use for that shit, sure, we can interview that way. It is the same deal with Teams and Zoom. None of that shit is touching my personal devices, it is strictly limited to the work machine.
you might be slightly more receptive to this idea if you have, the company administering the exam needs to ensure no cheating is happening so app starts, all your other apps are shutdown, you get a call through the app to show your surroundings with the camera on your laptop etc before exam begins. at no point in time did I find any of it intrusive or strange, I wanted to get the exam done remotely, they need to ensure that I wasn’t cheating
I assume this "app" is not open source, correct? Is is compatible with Linux systems? Can it run on non-FHS distribution?
> all your other apps are shutdown
I admit I am curious about this bit. Does it just start killing all other processes belonging to the same user ID? Or of all users (since you could get "assist" from process owned by an another user)? At least PID 1 needs to survive the slaughter, but it can be used to run arbitrary code to assist with the cheating. So how does it tell what is "an app" it needs to stop?
> Unicode case folding decisions can also be made at that point
Ok I will bite. How do you indent to do case folding without knowing the language the string is in? Will every filename or whatever also have its language as part of the string? I am not sure what the plan is there.
It's probably not. You can put any domain you want on the "from" address. Just because it says it was from Gmail doesn't mean it actually was, unless it's signed with DKIM etc.
I had a domain for a while that people got spam "from" all the time. It had nothing to do with me and there was nothing I could do about it.
I run mail servers for myself, a couple of side projects, and some friends and family. A double-digit percentage of all spam caught by my filters is from Google's mail servers, not just forged @gmail.com addresses.
Of the "too big to block outright" spam senders, behind Twilio Sendgrid and Weebly, Google is currently #3. Amazon is a close #4. None of the top four currently have useful abuse reporting mechanisms... Sendgrid used to be OK, but they no longer seem to take any action. Google doesn't even accept abuse reports, which is ironic because "does not accept or act upon abuse reports" is criteria for being blocked by Google.
Most spam from Google is fake invoices and 419 scams. This is trivially filtered on my end, which makes it perplexing Google doesn't choose to do so. I can guarantee that exactly 0% of Gmail users sending out renewal invoices for "N0rton Anti-Virus" are legitimate.
The Spam I get from "gmail" and ends up in my spam folder is spoofed. The Spam I get from gmail and ends up in my inbox is from gmail. Spammers will mass-create accounts and mass-sell them to spammers.
I believe for example in rust you should be able to do the same.