ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
A side-by-side editorial comparison of Jackett and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
Daily tags chasing tracker domain moves, login changes and freeleech detection
Jackett continues to ship a tag most mornings, each one a short auto-generated commit list of indexer definition edits. The newest adds a cookie login variant for HD-Space and captcha-aware login for funfile; the day before was a sweep of domain bumps and download-volume-factor detection corrections across torrenttip, magnetcat, 52bt, torrenteros, tocashare and seedcore. No release in this window touches the application itself.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
Jackett continues to ship a tag most mornings, each one a short auto-generated commit list of indexer definition edits. The newest adds a cookie login variant for HD-Space and captcha-aware login for funfile; the day before was a sweep of domain bumps and download-volume-factor detection corrections across torrenttip, magnetcat, 52bt, torrenteros, tocashare and seedcore. No release in this window touches the application itself.
This is maintenance as a product, and the cadence is the feature. Trackers rotate domains, add captchas, switch to cookie auth or vary their freeleech percentages, and Jackett absorbs each change within a day — Scenetime was added and dropped within days, 720pier removed and then restored by revert. The recurring shift from form login to cookie and captcha handling across sites is the one visible pattern: the definitions are steadily taking on more anti-bot handling.
Expect the same daily cadence of definition edits, with more cookie and captcha login variants as trackers tighten access. The entries show no application-level work planned or in progress.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.
Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Jackett or surveytidy.
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveycore declared its API stable with every survey design type covered.
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
A German electricity load-profile package added gas and doubled the market it serves.
See all Jackett alternatives → · See all surveytidy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Jackett is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Jackett is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Jackett alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Jackett alternatives" section above for the current picks, or visit /alternatives/jackett for the full list with editorial commentary on each.
Top surveytidy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveytidy alternatives" section above for the current picks, or visit /alternatives/surveytidy for the full list with editorial commentary on each.