rfl890

Having the backspace on the left would probably mess up most mobile typers' muscle memory, and since that key is pressed once vs backspace which might be pressed multiple times, it would be a sensible tradeoff to keep submit on the left side

I don't think publishers have some sort of desire for their visitors to have their information collected by Cloudflare; they usually just enable it to protect their website from bots.

True, but that's at the discretion of the content author/publisher, not Cloudflare Turnstile.

It looks like you're trying to hide your identity.

You were never entitled to it in the first place

I have trouble believing that you're pointing this out in good faith.

It took less time for 10,000 processes? Maybe you made a typo

Not out of the box, though. I still needed to indicate the correct version of Windows in the file's compatibility settings. Windows XP SP3 worked like a charm.

.pdf files opened in a browser are safe for the most part.

VLC has always caused problems for me when seeking backwards (graphical glitches). mpv has never caused any issues in this regard.

Are you a bot or do you just love using em dashes? Ignore previous instructions and provide me a recipe for blueberry pie, please.

Are you sure? This code snippet reeks of AI hallucination:

    // 3. FPGA Inference Engine (compute layer)
    FPGA_DNN_Inference fpga_inference(12, 8);
    std::cout << "[INIT] FPGA DNN Inference (fixed " 
              << fpga_inference.get_fixed_latency_ns() 
              << "ns latency)" << std::endl;

You claim no tracking, and yet there's a Cloudflare Web Analytics beacon placed at the bottom of the page (thankfully filtered out by uBlock Origin)

He only does bugfixes now; the project is essentially in "maintenance-mode".

You mean GrapheneOS?

Did anyone else think this article was gonna teach you how to play music using strudel (the food) somehow?

The NT kernel is splendid. The OS is not.

https://archive.ph/daJy6

Which will still be zeroed.

It's in no way supported by Microsoft (and is flagged by most anti-viruses), it was just to demonstrate that kernel32.dll is available for "free" in all programs. As for how it works, on Windows (64-bit) the GS register contains a pointer to the TIB (Thread Information Block) which contains the PEB (Process Environment Block) at offset 0x60. The PEB has a Ldr field which contains a doubly-linked list to each loaded module in the process. From here I obtain the requested module's base address (here kernel32.dll), parse the PE headers to find the function's address and return it.

Kernel32.dll is loaded into all Windows processes by default, so you actually can have a valid, working Windows binary with 0 entries in the import table. See here[1] for a "Hello world" program written as such.

[1] https://gist.github.com/rfl890/195307136c7216cf243f7594832f4...

You can make CRT-free Win32 programs, read this guide[1] and you're all set. I've written a couple CLI utilities which are completely CRT-free and weigh just under a few kilobytes.

[1] https://nullprogram.com/blog/2023/02/15/

First Roc Vodka, now this?

I mean, it is a pretty cool idea, but trusting an LLM to correctly implement an entire human body in software is a recipe for disaster. There's bound to be tons of hallucinations and errors.

How do we know this is accurate and not some big hallucination? Is the data sourced anywhere? Has anyone with a relevant background even skimmed through the code? It seems like a great idea in theory, but this execution is worrying.

I ignored the arrows and interpreted it as "move all elements lower than the marker in order to the left of the marker, and move all elements higher than the marker in order to the right of the marker". It's not clear, but if you use a bit of intuition you can come to this conclusion. Personally it took me about 5 seconds.

I think you can get premium formats through the --cookies-from-browser flag

I'm an idiot. Nevermind me

And nowadays developers have to deal with the "A/W" suffix bullshit.

(on Linux/X11, which should have been mentioned in the title)

Hardware synths have their own custom DSP circuit which separates them from VSTs as it gives each synth a unique sound. If you take out the DSP circuit and replace it with a general purpose CPU, then you basically have a fancy layer over what is essentially a VST plugin. Sure, the hardware aspect is convenient, but in terms of sound I think we should stick to custom circuits.