Many other tools/platforms provide decent source control and issue tracking. Nothing else has the FOSS project market share of github, and this matters especially when you're looking for the canonical home of a project and trying to judge how popular/active/viable it is (stars/commits/issues/PRs).
If you want exposure and participation for your FOSS project, it's harder to not use github.
FWIW, Forgejo does the source control stuff well. I love it for self-hosted local mirrors.
Hard pass. Another Linux laptop with another sus distro won't teach anyone how to focus. Save a hand-me-down laptop from the landfill, install a known good distro, and do the hard work of culling distractions.
You're right to start with your requirements. Try to get detailed, like the list @WA wrote out, then match it up with appropriate tech.
I wrote a technical book and I also wanted multiple decent-looking outputs. In my case: HTML, EPUB/mobi, screen and print PDFs. I was struggling with Markdown+pandoc+custom scripts/styles, so I switched to Asciidoc. I wrote about that process here: https://adammonsen.com/post/2122/
Here are two examples where the author used Markdown and the result was beautiful and successful (although layout for printed editions were done with extra/other tooling): http://gameprogrammingpatterns.com , http://www.craftinginterpreters.com . I'm curious if Bob would/will use Markdown for his next book. My process is different than Bob's... I didn't need literate code and I didn't want to do _any_ layout/pre/post-processing, even for print. Asciidoctor worked for this, although there were some compromises (see my links above). Print-ready layout is a lot of work, however you do it.
Is this your first book? Do you have a publisher? Will it be printed on paper? Do you have a developmental editor / proofreader / etc? Do you have a plan for what you'll do after you publish e.g. talks/promos/tour?
Contact me if you want to chat. I'm happy to share my war stories. And good luck!
In the space of local-first finance apps, I've really enjoyed Actual Budget (as have many, based on what I'm seeing in other comments). I'll check out Wealthfolio but like @dw_arthur I'm concerned about looking at investments too much / too often. I try to invest based on personal experience / value and always go long. I use off-budget accounts in Actual to track investments/illiquid value changes and update them every 6mo-1yr. I'm sure a spreadsheet would work fine for this as well. But for someone who moves investments more frequently, Wealthfolio looks awesome.
For managing my life's data, this golden combination is always going to win: app that works well | full/local control of data | sane FOSS project governance | software license mitigates enshittification (e.g. AGPLv3)
Skimming that I'm thinking yes, sure, why not, but this repo is missing useful context. Who are you, authors? Why should I bother learning this protocol? Is anyone using or going to use this? If it's new, has it been shopped around at conferences? Any related research?
And specifically Sam goto (Google, fedcm) and Dick Hardt (hello, oauth2 spec writer).
This was originally thought up a couple (5-6) years ago along side fedcm and privacy sandbox, but before SD-jwt was full baked, so it wasn't as clean. The use of SD-jwt is much better for privacy.
But https://en.wikipedia.org/wiki/Money_Electric%3A_The_Bitcoin_... is a bit more compelling. Satoshi is Adam Back and Peter Todd.
reply