For figuring the doomsday of a particular year, you can use the Odd+11 rule.

Let X be the last two digits of a year.

If X is odd, add 11.

Divide X by 2.

If X is odd, add 11.

Let Y = 7 − (X mod 7).

Count forward Y days from that century's anchor day to get the year's doomsday.

https://arxiv.org/pdf/1010.0765

This is a good point. Another problem with streaming services, specifically for music streaming services, is that they can change the track of a previously released album with no user choice to hear the original. Example: Track 4 of Elephunk by the Black Eyed Peas. It was universally replaced with the “clean” version of the song. I’m not a fan of rewriting history.

As long as you embed it with an SRI integrity hash, you're safe, even if the remote server is compromised.

I’ve been using Notepad Next on Mac: https://github.com/dail8859/NotepadNext

That's the "true"/original version; for Notepad++-like experience on macOS.

"Before NASA sends astronauts to actually land on the Moon in 2028, they need to be absolutely certain that the Orion spacecraft, the Space Launch System rocket, and all the life-support systems work exactly as intended in the deep space environment where no quick rescue is possible."

They did it 53 years ago. Right? So what’s the problem?

This looked interesting but the workaround might have been patched by Apple in newer iOS versions: https://www.reddit.com/r/iphone/comments/1p3e2bf/my_hacked_i...

The original iPhone ran OS X: https://youtu.be/x7qPAY9JqE4?t=522

It still does, they just call it iOS.

If you just need a simple local s3 server (e.g. for developing and testing), I recommend rclone.

rclone serve s3 path/to/buckets --addr :9000 --auth-key <key-id>,<secret>

It compiles the Go code to WASM, so it can be used browser side.