Great point on accessibility, a guarantee of screen reader support is a benefit that would be lost with screenshots or text without the correct semantics.
A nice improvement! An unfortunate side-effect of it is that it introduces some jitter during macOS's smooth scrolling in Firefox at time of first render, though.
Happy rsync.net client here, thanks for the great service; the ability to use rclone for exactly this purpose, without having to worry about ingress/egress charges, is a huge value-add.
Edit: Will free-of-charge ingress/egress always be a feature of the service? With more customers using rclone for shifting data to/from/between other services, I'd hypothesize that bandwidth use could be creeping up.
Edit 2: A feature I'd love to see would be the ability to setup automated cron-like jobs directly from the admin portal, for e.g. automated rclone backups, eliminating the friction of having to setup another service to periodically run a command on rsync.net. (Tricky to do in a serverless fashion for long-running commands like rclone.) Is this something that might be in the pipeline?
Yes, exactly. The procedurally generated world is predictable* if you know the world seed -- land forms, structures and items/loot spawn the same way each time. You can specify the seed when creating a world, if you like.
There are certain things that are nondeterministic, such as where mobs spawn (that depends on player position, etc.) or how they behave.
* There may be parts of world generation these days that are nondeterministic even with a known seed; I'm not too up to date with recent world generation changes.
A brief summary: pack.png [0] is a 128x128px image of a scenic mountain within a Minecraft world, and is used in in-game menus. The goal of this project was to discover the world seed used to generate the Minecraft world that pack.png was taken in. This was no small feat, with 2^48 possible seeds the procedural world generator could have used, and required much analysis, trial-and-error and distributed computation by many volunteers to obtain the seed.
The process involved exploiting identifiable world features such as the position of clouds, orientations of certain block textures, and more, to discover the exact coordinates of the blocks in the image (insane in itself); figuring out the exact camera perspective via regression fitting; creating and training a machine learning model to upscale the image in order to better discern details and manually create a reconstruction; deducing how the image was taken (print screen -> cropped to 512x512 -> 4x downscaled with specific resizing algorithm); and more. Through these efforts, they had significantly reduced the number of candidate seeds; distributed computing power provided by 3,500 project volunteers' GPUs was then used to obtain the final 700,000 candidate seeds, and from that a brute-force approach was used to isolate the actual pack.png seed.
The YouTuber SalC1 produced an excellent video on the project [1].
> You have to be a non-blind person to pass the Turing test, as Cloudflare does not offer a handicap option.
(Edit: not sure if the above is true.)
I was quite surprised to see this. Much effort has been put into making the web more accessible; it’s a shame if an otherwise accessible site is blocked behind a non-accessible captcha wall.
Seconding this.
I don't know if it's a fair comparison but Instagram is removing publically-visible like counts because of their associated consequences, and embeddable banner services for tracking GitHub profile views seems inevitable.
