anki

We define our API into the Rust via protobufs[0] and some codegen. The wrapper around these is very lean, FFI-based[1], it's abstracted to a library so Android devs never need to know there's rust/codegen involved. We then define a light Kotlin-based wrapper around the protobuf-generated API[2]. This is a candidate to move to Kotlin multiplatform in the near future (mostly for test speed improvements). [0] https://github.com/ankitects/anki/tree/main/proto [1] https://github.com/ankidroid/Anki-Android-Backend/blob/a0428... [2] https://github.com/ankidroid/Anki-Android/blob/68192585a7ae4...

When a popular, free and open source passion project led by a single dev moves into the hands of a company that needs to sustain its 30-people team [0], you know what happens next. AnkiHub's modus operandi has been to take over communities or projects where free exchange happens and monetize/paywall them. If you've been a part of the /r/medicalschoolanki subreddit, you know exactly what I mean. It's been hollowed out completely. In the post, AnkiHub mentions how Anki is "sacred" to them. Yet, they have had no qualms entrenching themselves into Anki's settings menu as the only third-party ever to do so. [1] I am sure more is to come. And the language used in their post almost never helps their case, especially in the pricing and OSS sections. I understand why Damien felt he was being a bottleneck in Anki's development. This is similar to w

The community has been in a deadlock over making FSRS the default (https://github.com/ankitects/anki/issues/3616), and I wonder if this will lead to some resolution. It seems like the core things that Anki needs are new user experience improvements, and algorithm updates. SM2 really shows its age as compared to other algorithms.

Try docker: https://github.com/ankitects/anki/tree/main/docs/syncserver#...