That's not how that term works. Input latency/lag refers to the time differential between triggering some kind of input and the action of that input showing up on your screen.
I'm curious, what amount of input lag does this introduce?
The original Ishkur's Guide is even more similar, here's a modern recreation of it: https://igorbrigadir.github.io/ishkurs-guide-dataset/
I absolutely love Tailscale, it's been a game changer for accessing my home gear from anywhere.
There are no polling locations in Oregon, everything is by mail you goof.
Try the other direction, call it "First Life".
Yeah this one was pretty bad, I had the same reaction.
I've got my homelab participating in Folding@Home, it'd be interesting to run some commercial workloads in a similar manner to help offset energy costs.
Just wanted to say I'm a huge fan of this.
There are two levels of AWS Shield, "Standard" and "Advanced". You are correct that all instances receive "Standard" protection from Shield by default. https://aws.amazon.com/shield/
That's not how that term works. Input latency/lag refers to the time differential between triggering some kind of input and the action of that input showing up on your screen.
I'm curious, what amount of input lag does this introduce?
The original Ishkur's Guide is even more similar, here's a modern recreation of it: https://igorbrigadir.github.io/ishkurs-guide-dataset/
I absolutely love Tailscale, it's been a game changer for accessing my home gear from anywhere.
There are no polling locations in Oregon, everything is by mail you goof.
Try the other direction, call it "First Life".
Yeah this one was pretty bad, I had the same reaction.
I've got my homelab participating in Folding@Home, it'd be interesting to run some commercial workloads in a similar manner to help offset energy costs.
Just wanted to say I'm a huge fan of this.
There are two levels of AWS Shield, "Standard" and "Advanced". You are correct that all instances receive "Standard" protection from Shield by default. https://aws.amazon.com/shield/