I believe there is an API to convert such a link, but detecting that a link is going to a Lemmy instance might be difficult (or non-elegant).
That may be due to "the Hacker News hug". This link had a high score in HN a few hours ago. High traffic may have caused scalability problems.
I don't know if you have seen it, but programming.dev has a "community request" community: https://programming.dev/c/community_request
You can suggest one for F# there, if you want.
To be honest, I cannot be sure that session invalidation actually worked. I could use the session from the day before as well. But the vulnerability was in lemmy-ui, and people not using the web site directly should be fine, I guess. If you want to be on the safe side, you can log out and log back in. It takes only a few seconds.
Are there any other distros that are flatpak-only?
Exactly. Even though one doesn't need it often, it's an important tool.
I don't think what you say contradicts with what I said. If we separate "identity providers" from "content hosts" a person could easily go get as many accounts as they like (just like getting many gmail accounts) and then use them to log in to any content networks they are interested in. I didn't suggest that everyone should have their own instances of anything.
Maybe I wasn't clear enough in my wording. I didn't mean to say everybody shoukd/must have a single account. And separating identity from content doesn't necessarily enforce it. Think about crypto wallets. They provide some sort of an identity, but anybody can have an infinite number of them. Now, I'm not saying crypto wallets should replace fediverse identities. I don't even have one. But, I could log into all fediverse instances with a single account, that would make things much easier for everybody:
What has replaced StackOverflow for you? Is it the IDEs getting better or something like Github Copilot?
My main concern is this: We have a wiki, each component has some sort of a README. If we add C4 to the mix, then we will have technical documentation in 3 different places. I would love it if C4 would eliminate the need for a wiki. Then in a CI pipeline, we would fetch component READMEs from their repositories and merge all of them into a single C4. When a developer tries to understand a component, they would go to its diagram and view different aspects of it (some text, links to external API documentations, other sorts of diagrams, etc.).
I guess I need to start experimenting first to see if things work better than I expect. As you say, developers will not have huge problems once the workflow is in place.
For us to be able to help you, I think you need to give us some more details about the organization of your work. If each chapter is a separate text file, then you don't really need to do any branching at all (assuming people will only make changes on their own files and not touch others' work). If it is a single text file, branching (or anything else, to be honest) will not help much.
I assume chapters will have their separate files. As long as you can control who touches which file, everybody can work on the same branch (also referred to as "trunk based"). But if you fear that people may interfere with each other's work (willingly or by accident), then it makes sense to create a branch per chapter to keep contributors at a distance from each other. But working on a single repository requires some sort of an agreement on the workflow.