Migration of Anki’s editor to Svetle.



Audio Recording in Spectacle!!!

Plasma 6.8
Plasma 6.6.6
Plasma 6.7.3
Plasma 6.8
Frameworks 6.29
Evaluation metrics for spaced-repetition schedulers in R: the sample-weighted binned RMSE (RMSE(bins)) used to rank algorithms in the open spaced repetition benchmark, together with log loss, the area under the ROC curve, and calibration curves. The metrics take plain vectors of predicted recall probabilities and observed outcomes, so they can benchmark any scheduler’s predictions.
Installation:
# install.packages("remotes")remotes::install_github("chrislongros/srsbench")
Use:
library(srsbench)p <- c(0.95, 0.86, 0.72, 0.60, 0.91)y <- c(1, 1, 0, 1, 1)elapsed_days <- c(1, 6, 20, 4, 15)i <- c(2, 3, 4, 2, 3)lapse <- c(0, 0, 1, 0, 0)rmse_bins(p, y, elapsed_days, i, lapse) # calibration, lower is betterlog_loss(p, y) # cross-entropy, lower is bettersrs_auc(p, y) # discrimination, higher is bettercalibration_bins(p, y) # predicted vs observed by bin
More info here: https://github.com/chrislongros/srsbench
Available as an AUR package too: https://aur.archlinux.org/packages/r-srsbench
SHA-256, SHA-512 and SHA-512/256 are secure hash algorithms specified in FIPS 180-4, NIST’s Secure Hash Standard. ZFS uses the above as block checksums (checksum=sha256, checksum=sha512) for data integrity and deduplication. There is currently no unit test coverage for this family of hash algorithms.
It adds a tests/unit/test_sha2.c with three types of tests that follow the FIPS 180-4 standard as defined in https://nvlpubs.nist.gov/nistpubs/fips/nist.fips.180-4.pdf :
tests/zfs-tests/cmd/checksum/sha2_test.czfs_impl_get_ops(): every supported implementation must reproduce the known answer and compute the same digest for a multi-block messageTesting perfomed:
$ make unit T=sha2 UNITTEST tests/unit/test_sha2Running test suite with seed 0xcf392006...sha2.sha256_known [ OK ] [ 0.00002286 / 0.00001675 CPU ]sha2.sha512_known [ OK ] [ 0.00002044 / 0.00001995 CPU ]sha2.sha512_256_known [ OK ] [ 0.00001542 / 0.00001524 CPU ]sha2.incremental [ OK ] [ 0.00019737 / 0.00019336 CPU ]sha2.impls [ OK ] [ 0.00026169 / 0.00026171 CPU ]5 of 5 (100%) tests successful, 0 (0%) test skipped.
This patch release addresses various bugs from v3 release and adds an additional filter to workflows

Strip fsrs_params_4/5/6 from each deck config when exporting withwith_scheduling=false and also add an clear_fsrs_parameters() helper function.
https://github.com/ankitects/anki/commit/8a99c47639491f38cb146ce7748b7b08ad77431f
Now, let’s get right into all the new features in this release:
Survival prediction for severe limb ischaemia in R, using the prognostic model from the BASIL trial (Bypass versus Angioplasty in Severe Ischaemia of the Leg).
The model is an accelerated failure time Weibull regression.

Main use:
digest(“abcde”, algo = “fletcher”, serialize = FALSE) # “f04fc729”


https://github.com/eddelbuettel/digest/commit/31d93bddd8ffa6f8e92dd687d0001a7dc86bf574
This deterministic test suite performs a scalar, incremental, native as well byteswap checksum verification of the fletcher2 and fletcher4 hash, non cryptographic algorithms. Additionally it verifies matching between different implementations supported by the host.

An interesting article by Klara Systems:
1. Different problems:
Ceph is built for distributed storage across many servers; ZFS optimizes performance, reliability, and simplicity on a single system.
2. Distributed = overhead:
Ceph scales horizontally and survives multiple node failures, but adds networking, coordination, and management complexity that raises latency.
3. Most don’t need it:
Modern ZFS delivers strong capacity, performance, and availability with far less operational complexity — a solid fit for virtualization, databases, backups, and enterprise storage.
https://klarasystems.com/articles/zfs-vs-ceph-do-you-actually-need-ceph/