The entire package manager repository could just be in an offline cache. They don't need Internet to give their agents access to tons of software.

https://elevation.fandom.com/wiki/Sabbath_service_(SHO)

The next line is critical for context, as it defines what "things in the world" means.

> [...] For everything in the world—the lust of the flesh, the lust of the eyes, and the pride of life—comes not from the Father but from the world. The world and its desires pass away, but whoever does the will of God lives forever.

Seems clear to me this isn't about creation (ie not saying don't cherish nature / animals).

So these resellers get a ton of accounts on subscriptions and sell the cheaper tokens.

https://code.claude.com/docs/en/auto-mode-config

The summer resort games (iirc one big trade quest) were nice too.

> In the end, I learned (and accomplished) far more than I ever expected - and perhaps more importantly, I was reminded that the projects that seem just out of reach are exactly the ones worth pursuing.

Couldn't agree more. I've had my own experience porting something that seemed like an intractable problem (https://news.ycombinator.com/item?id=31251004), and when it finally comes together the feeling of accomplishment (and relief!) is great.

Mobile

https://github.com/settings/billing/licensing

EDIT:

https://docs.github.com/en/copilot/how-tos/manage-your-accou...

> If you have been granted a free access to Copilot as a verified student, teacher, or maintainer of a popular open source project, you won’t be able to cancel your plan.

Oh. jeez.

Maybe you'll find the resources I link to in the documentation for my project helpful.

https://github.com/ZQuestClassic/ZQuestClassic/blob/main/doc...

Or perhaps you'd find reviewing my usage of asmjit helpful:

https://github.com/ZQuestClassic/ZQuestClassic/blob/main/src...

My main high-level advice would be to have an extensive set of behavioral tests (lots of scripts with assertions on the output). This helps ensure correctness when you flip on your JIT compilation.

You'll eventually run into hard to diagnose bugs - so be able to conditionally JIT parts of your code (per-function control - or even better, per-basic block) to help narrow down problem areas.

The other debugging trick I did was spit out the full state of the runtime after every instruction, and ensure that the same state is seen after every instruction even w/ JIT enabled.

Good luck!

I've come to accept input lag, but mostly play games where it doesn't matter (simple platformers, turn-based games, etc). I know steam link from my home desktop to my ~5 year smart TV is adding latency to my inputs – though I can't tell if it's from my router, desktop, or TV – but I've come to accept it for the convenience of playing on the couch (usually with someone watching next to me).

I know some blame is on the TV, as often if I just hard-reset the worst of the lag spikes go away (clearly some background task is hogging CPU). And sometimes the sound system glitches and repeats the same tone until I reset that. Still worth putting up with for the couch.

Can anyone suggest a good archive tool? The open source project I help run has ~10 years of conversations, bug reports, feature requests, etc. sunk into Discord, and obviously I want to preserve all that (not sure we'll end up leaving the platform, but it's good to have backups anyhow).

Our bug reports / FRs are in forum channels, and I've written a script to extract those and potentially import them into some bug-tracker. But I'd like something good that can archive the entire thing in a reasonable format.