DIDs are rooted in ECDSA keys (secp256k1). Each user identity is a non-PQ cryptographic commitment. These ecosystems must start migrating very soon because if CRQCs arrive before they're done, they face a choice between user compromise and bricking accounts.
I've been writing notes on Heroku alternatives (mostly Fly, Railway, Render) at https://croaky-webstack.deno.dev/ Maybe something useful in there for others.
If you're a Rails developer, you probably have a config/initializers/backtrace_silencers.rb file in your app. Think of James the next time you see that file. He wrote the initial implementation:
I knew James mostly online and a little in person from various programming conferences. He was smart, funny, and kind. He made a difference. He will be missed.
We've tried putting style violations in the build and found there are enough edge cases that it isn't exactly the interaction we've wanted. Sometimes, we want the human to say "no, my pair and I broke the guideline on purpose and we're okay with it in this case." We don't want a broken build in those cases.
Totally agree with you about getting feedback earlier than opening a PR, though. Linters integrated into text editors are a great way to go.
I've been using Hound on about a dozen projects the last few months and haven't seen false positives. We built it atop Rubocop, which has been pretty well-vetted.
> Software development has too many unwritten rules and social interactions for a bot
We've limited our guidelines to a subset that should almost always be "no argument, my bad, fixed in [SHA hash]." However, it comments instead of failing the build or mechanically changing the code because that the human should make the final decision about whether to make the change.
I've been in a Campfire room with the new maintainers for a few days. We've been coordinating the transition for a couple of weeks. Looking forward to knocking out a few more features and bugs in the next few days while they get used to the codebase.
Everyone's busy so we'll see how much time is needed and able to be spent by the new maintainers but we're happy to have found almost a dozen developers to lead maintenance across the two companies (Crowdtap and Iora Health) and we took the time to express a process and way of doing things to help make the project more efficient: