Less than a terabyte out of over 100, so I'm sorted :)
Aren't Apple devices and many Android photo apps after configuration already using very efficient image formats? Seems much better to avoid two steps of lossy compression.
> Support for QUIC and HTTP/3 protocols is available since 1.25.0, it is included in Linux binary packages. Please refer to the ngx_http_v3_module documentation.
So the phrasing seems to conflict with the nginx docs.
Is there an accurate, if biased, feature grid I can look at?
As a hobby I can afford so far. If it starts costing me a lot of time or money, I'll be in a much better position to understand who needs what else, and what that's worth to them. Some link-in-bio services integrate the sale of goods, physical or digital, for example.
Being truer to reality where movement is continuous is not a subjective assessment. It doesn't look different, it looks more like what it's supposed to if realism is the goal. That's not a matter of taste.
It's so many things, starting with the North American electric grid, NTSC, etc.
Yes my graphics card + monitor could theoretically run at more than 60 Hz. When I got to choose between resolution and refresh rate, I picked resolution. Hence 60 Hz.
As to how you can perceive the difference between 120 events per second and 240, I have what I hope is a fairly simple explanation.
It's like lightning strokes of tens of microseconds making a lasting impression on your perception of the scene. You don't "count" strokes over time, but in space.
When you make circles fast and large enough on screen, you can evaluate the number of cursors that appear before your eyes. At 4 circles per second, is each circle made of ~60 pointers or ~30? Belief not fact: it's not hard to guess.
As per the post, I wrote this tool to confirm I was getting jerks of ~10ms every few seconds on one USB port and not the other. This would _suggest_ I can catch differences around the ballpark of 100 Hz.
I'm game for a randomized blinded test on 120 Hz refresh rate vs 240 Hz refresh rate. I would indeed be very curious to confirm I can tell the difference with a proper protocol.
Many years back (we were on CRTs), I was in similar shoes, convinced my friend couldn't tell the difference between 60 Hz and 90 Hz when playing video games.
Turns out he only needed to look at the pointer through one push of the mouse to tell right away, successful 100% of the time in a blinded experiment.
Yes, I rely on pointerrawupdate. Thanks for letting me know! Unfortunately pointermove is typically synced with graphics in my limited experience, and I think I'd rather not show anything than provide wildly inaccurate numbers.
Are you talking about R2? If so, requires a credit card, doesn't support atomic deploys or rollbacks, etc.
I'm a CloudFlare user who's used Workers, and trying to sign up for it fails silently here. Bad start for me, doesn't say much, but makes it hard to review further.
That being said, yes, there are competitors. I don't think any offers quite the UX I've built for small teams of experienced developers, but I could be wrong or misguided in my efforts.
Fixed, thanks! Yes, longevity is an issue with anything online. On the other hand, in this case recovery is not a huge issue for anybody technical enough.
https://zat.is uses uppercase base32 for URL checksums, as alphanumeric QR codes can contain 0–9, A–Z (upper-case only), space, $, %, *, +, -, ., /, :. Overhead is only 10% (5.5 bits / 5 bits). All links fit in a 33⨯33px image, margins included, so little point in improving on that for URLs so short. The tradeoff is that the checksum to URL mapping is stored in a backend and networking is required to learn anything about the real URL.