I'm younger than you, and probably haven't been working in tech as long, but I've been having similar thoughts. No kids, so I'm maxing retirement accounts, saving as much as I can, and trying to start my own small software company for niche applications.
Hopefully in a few years I have a couple mildly profitable applications, and I can pull the rip cord on working in tech and coast while I figure out next steps for myself professionally.
Oh no, I'm being genuine. Documenting the process itself wasn't what I was curious about, I was wondering how you'd go about your last bullet. Accepting lots of currencies can be hard, but I guess I'm not super familiar with online escrow services. I'm not sure how simple they can make that process, or who would pay the cost of using them (I assume they're not free).
I was also wondering how automated or manual you would envision the review process. I'm guessing your hope would be that the small deposit would stem the flow of submissions enough to make it all possible to review manually again, and you would also manually return all the payments sent to escrow?
Agreed, I would love that. With how varied screen readers can act between systems and web browsers I would like to have more "good" examples of what screen reader users would expect to encounter and consider a good experience.
Gonna pile on to other's suggestions, and say Todoist can do this. You can schedule a task to happen every four weeks, and the next occurrence happen four weeks after you complete it (even if you're a few days late) or four weeks from when it was last due. Pretty nice for my needs, might fit yours too.
Hopefully in a few years I have a couple mildly profitable applications, and I can pull the rip cord on working in tech and coast while I figure out next steps for myself professionally.