ralger
ralger stopped scraping only web pages and started scraping the files on them.
Comparison · DevOps
bskyr vs rtoot
A side-by-side editorial comparison of bskyr and rtoot — release velocity, themes, recent moves, and the top alternatives to consider.
bskyr vs rtoot: at a glance
What is bskyr?
bskyr grew from a Bluesky scraper into a full read-write client, DMs included.
bskyr is an R client for Bluesky's AT Protocol. It started as a data-collection package with deliberately limited posting, and has since added writing, embeds, list feeds and — in 0.4.0 — direct messages. The 0.4.0 release also fixed the profile endpoint's 25-actor ceiling and a result-widening bug, so the data-gathering half is still being maintained alongside the new surface.
What is rtoot?
rtoot reached 1.0 by rebuilding on httr2 rather than by adding anything new.
rtoot is the R client for Mastodon and the wider Fediverse, covering the REST endpoints, streaming, pagination and rate limits. The 1.0.0 release is infrastructure work — the HTTP layer moved to httr2, long-running queries are wrapped in tryCatch, and post_toot() gained basic error handling. The functional surface has been broadly stable since 0.2.0 added streaming and pagination.
bskyr vs rtoot: editorial side-by-side
bskyr
0.0DEVOPS
bskyr grew from a Bluesky scraper into a full read-write client, DMs included.
◆ Current state
bskyr is an R client for Bluesky's AT Protocol. It started as a data-collection package with deliberately limited posting, and has since added writing, embeds, list feeds and — in 0.4.0 — direct messages. The 0.4.0 release also fixed the profile endpoint's 25-actor ceiling and a result-widening bug, so the data-gathering half is still being maintained alongside the new surface.
◆ Where it's heading
Each release has extended what the package can do rather than how fast it does it: pagination and cursors removed the per-call result ceilings, 0.3.0 filled in the posting surface with link cards, custom timestamps and deletion, and 0.4.0 crosses into private conversations. Three vignettes shipping in the same release suggest the author now treats coverage of the protocol as broad enough to need documenting by task rather than by function.
◆ Prediction
The remaining AT Protocol surfaces the entries have not touched — moderation and labeling — are the plausible next target, since convos were the last major read-write area left. The entries do not indicate a timeline.
rtoot
0.0DEVOPS
rtoot reached 1.0 by rebuilding on httr2 rather than by adding anything new.
◆ Current state
rtoot is the R client for Mastodon and the wider Fediverse, covering the REST endpoints, streaming, pagination and rate limits. The 1.0.0 release is infrastructure work — the HTTP layer moved to httr2, long-running queries are wrapped in tryCatch, and post_toot() gained basic error handling. The functional surface has been broadly stable since 0.2.0 added streaming and pagination.
◆ Where it's heading
Development has slowed to roughly one release a year and shifted from endpoint coverage to durability: handling 429s, surviving editors that misreport as RStudio, accepting POSIXct where the API wants IDs. Most changes arrive as contributed pull requests against reported issues rather than from a roadmap.
◆ Prediction
With httr2 in place and a 1.0.0 label attached, further releases most likely track Mastodon API changes and contributed fixes; the entries show no new capability in progress.
Alternatives to bskyr and rtoot
Other DevOps 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 bskyr or rtoot.
ieugwasr
ieugwasr's release notes are a record of OpenGWAS tightening the tap.
Sanity
Sanity is widening the surface agents can act on while forcing its own packages onto modern Node.
Dapr
Dapr is shipping fixes across three release branches at once, most of them in workflows.
ipumsr
ipumsr is collapsing a dozen collection-specific APIs into one extract vocabulary.
collections
A stable R data-structure package whose releases are now mostly compiler and checker upkeep.
Recent activity from bskyr and rtoot
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agortootHTTP layer migrated to httr2 for the 1.0.0 release
- 9mo agobskyrbskyr 0.4.0 adds Bluesky direct messages ⚡
- 1y agobskyrbskyr 0.3.0: link cards, custom timestamps, post deletion
- 1y agortootPOSIXct accepted for ID arguments; VSCode detection fixed
- 2y agortootProgress bar and 429 rate-limit handling added
- 2y agobskyrbskyr 0.1.2 adds cursors and automatic paging
- 2y agobskyrbskyr 0.1.0 turns a data collector into a posting client ⚡
- 2y agobskyrbskyr 0.0.4: initial release, collection-focused
- 3y agortootget_fedi_instances() switched to a new API
- 3y agortootStreaming functions, pagination and rate-limit checking added
Frequently asked questions
What is the difference between bskyr and rtoot?
They serve adjacent needs but don't currently overlap on shipped themes. bskyr and rtoot are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is bskyr better than rtoot?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bskyr and rtoot are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to bskyr?
Top bskyr alternatives in DevOps are ranked by recent ship velocity. Browse the "bskyr alternatives" section above for the current picks, or visit /alternatives/bskyr-r for the full list with editorial commentary on each.
What are the best alternatives to rtoot?
Top rtoot alternatives in DevOps are ranked by recent ship velocity. Browse the "rtoot alternatives" section above for the current picks, or visit /alternatives/rtoot for the full list with editorial commentary on each.