For me, once Apollo officially stops working I won't have any ingrained habit for reaching out to reddit. I stopped using the website years ago except for reading search results that point there.
cark
joined 1 year ago
I'll admit I'm not the biggest FOSS evangelist, so this comes with a grain of salt. From a right to repair standpoint, I don't care for Apple's policies at all. But from a security and (perhaps counterintuitively) user experience standpoint, I agree with Apple's walled garden approach, locked down OS, and single app store. We see the alternatives in Android, and we see how much worse its security is.
Current place:
- Work is done on a feature branch on a personal fork of the repo
- Codebase requires 100% functional coverage, and you're responsible for writing the tests for your code and including that in the same PR
- Run pre-commit hooks for style auto-formatters before you can commit and push your code to your origin fork
- Ideally run local tests as well
- Create a PR to pull feature branch into the upstream repo's main branch, which triggers the CI pipeline for style and tests
- At least 1 other person must review the code before a PR can be approved and merged into upstream main
- There's a separate CI pipeline for testing of publishing the packages to TestPyPI
- Releases to PyPI are currently done manually
That is not true. Many attacks (e.g. the recently revealed Operation Triangulation) do not have persistence.