PeopleSoft -> Workday

You should have used the `--deploy-hook` on certbot. I use this to copy the cert to Synology NAS and trigger a reload of the cert on the NAS.

BTW: The easiest way to run certbot in a container is to mount a renew script (some shell script as simple as `certbot renew`) to /etc/periodic/daily/renew, then change the container's entrypoint to `crond -d6 -f`.

> The A9, in 2015, benchmarked comparably to a two-year-old MacBook Air from 2013. More impressively, it outperformed the then-new no-adjective 12-inch MacBook in single-core performance (by a factor of roughly 1.1×) and was only 3 percent slower in multi-core.

Too bad that performance is (still) locked in the walled garden and cannot be used as a small Linux server.

https://github.com/charmbracelet/bubbletea has a couple screencast worth checking out.

Not sure if it's a good comparison (never used both in depth) but think of this a Go version of all the goodies from https://textual.textualize.io/

I don't see the example would be different in conveying the same meaning if you omit the whole "85 turns out that".

if you include "it turns out that", you're implying that maybe you thought the same as them in the past, but looked into it, and learned something interesting. if you omit that, you're just correcting them and subtly implying that they aren't as smart as you (e.g. it was obvious to you)

I think Pixel phones are also unlockable/relockable?

Samsung did restrict side-loading recently,

- https://news.ycombinator.com/item?id=47202808

I'm sure that Google will do something like that as soon as it faced the US's carrot and stick they signed-up for.

That's not really sideloading, though. The stock recovery doesn't let you install apps or anything like that, it's meant for loading official versions of Samsung operating systems onto devices that got corrupted somehow.

You can probably try to use the stock recovery to flash a custom ROM, but I doubt it'll work. Custom ROMs rely on tools like TWRP or LineageOS Recovery for a reason.

This is how you can install GrapheneOS on these. Also, if you're wondering how does the security of something like this work: if you change the boot hash then the phone forgets all the hardware-stored secrets, for example the disk encryption keys.

My friend once told this joke:

> "A good programmer, when encountering a debugger bug," he paused, cleared his throat, and said solemnly: "should immediately drop the program they're debugging and start debugging the debugger instead!" The auditorium once again erupted in thunderous applause.

I think people commenting misunderstood what CEL offers.

Remember the famous https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule?

> Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.

CEL is a well specified, reasonably fast "embeddable" language with familiar syntax. I'm sure there are other languages that fits the description though.

Are you suggesting to compile CEL into native code and run the compiled code at runtime (i.e. as a predicate function)? I think this is doable and I vaguely remember this was how it's implemented initially.

But most use cases are treating CEL as a user provided config, which requires runtime parsing and execution.

I was thinking of something like this:

type MyType{ myName: string where size > 8, year: number where number > 2000 }

Then, whenever this type is used, at compile time, an evaluation is done to ensure that the type restrictions are enforced.

The author tried running rsyncd demon so it's not _just_ the ssh protocol.

Great point, and even beyond that I think (based on the paths) it was just a command line invocation, with something like NFS handling all the networking.