Skip to content

telegramR

0.0.2Package record

Interact with the 'Telegram' 'MTProto' API

0packages depend
1.6Kdownloads / year
–test coverage
13/13flavors OK

Overview

About

Provides a full-featured client for the 'Telegram' 'MTProto' protocol (https://core.telegram.org/api), enabling programmatic access to 'Telegram' chats, channels, messages, media, and stories. Implements binary encoding and decoding of the 'Telegram' 'TL' (Type Language) schema, authentication (including two-factor), encrypted transport, and high-level helpers for downloading channel history and reactions at scale. Intended for social-science research and data collection tasks that require direct API access rather than the 'Bot API'.

Changes in 0.0.2
  • Removed unused sample video files from inst/extdata, shrinking the source tarball to ~3.4Mb (under CRAN's 5Mb guideline).
  • Exported TelegramClient, the high-level client class, so TelegramClient$new() works after library(telegramR) (its @export had been in a comment that roxygen ignored, leaving it inaccessible).
  • Synced the bundled 'Telegram' TL schema to layer 229 and regenerated all TL type and request classes, fixing dialog and message parsing against current 'Telegram' servers.
  • Reworked the schema code-generation tooling in data-raw/ entirely in R (generate_tl.R, overwrite_stale.R, dedupe_types.R, emit_missing.R, and the regenerate.R pipeline), replacing the previous scripts. The pipeline is idempotent and documents every generated class with roxygen.
Show all changes in 0.0.2Hide the rest of the changes in 0.0.2
  • Fixed serialisation of 64-bit integers and byte fields, and the send-media chain.
  • Fixed the asynchronous test helpers to resolve promises objects, and a latent unqualified openssl::rand_bytes() call in the obfuscated transport.

From NEWS.md in the release

Install

Health

CRAN checks
13OK
Slowest check: 47.5 min · r-oldrel-windows-x86_64
Status changes
  • OK13 OKNow
  • OK12 OK, 1 FAILURE2026-10-01
  • NOTE11 OK, 2 NOTE2026-06-30
  • ERROR11 OK, 1 NOTE, 1 ERROR2026-06-23
  • NOTE11 OK, 2 NOTE2026-06-07
  • ERROR5 OK, 1 NOTE, 1 ERROR2026-06-03
Advisories

none known

Documentation

In release 0.0.2
READMEYes · 324 wordsVignettesYes · 4 · dynamicNEWSYes · 100% structured · mentions 0.0.2Citation fileYes · computed when R runs itWebsiteYes · pkgdown
Help pages
32
Examples that run
0%1 never run
Exported functions with examples
3%
Documented parameters
95%
Return-value docs
100%
Help pages citing references
0%

Downloads

1.6K
CRAN downloads in the past year
Rank #12,027 · ~4/day · ~129/mo
Daily download trend is not available in this view yet.
40630 days
89990 days
1.6K1 year
Compare downloads with other packages →
Also on96 r2u3 autocran

Repository

0Stars
0Forks
0Open issues
0Open PRs
0Releases
apitelegram
Last activity 2026-10-09
Responsiveness
How these are sampled
PRs merged (all time)
100%
Median days to close, 50 most recently updated closed issues
not measured
Median days to close, 50 most recently updated closed PRs
not measured

PRs over time

2026-07-07 · 02026-10-09 · 0
PracticesBeta

11 development-tooling and community-health practices detected across 7 families in the upstream repository

Checks run against github.com/romankyrychenko/telegramr on 2026-10-11.

Continuous integration (2)
GitHub ActionsR CMD check workflow

The R CMD check workflow runs on Linux, macOS and Windows, and on R-devel

Docs source (3)
pkgdown

GitHub Pages site last deployed 2026-10-09 · The repository has a site deploy workflow

pkgdown site last built 2026-10-09

Coverage (1)
Coverage reporting
Reproducibility and dev environment (1)
data-raw/
Show all practicesHide 3 practices
CRAN release process (1)
cran-comments.md
Research and citation (1)
CITATION.cff
Lint, format, editor (2)
lintrLint workflow
How this is detected·Detection ruleset v3 (2026-09-26)
AI coding toolsBeta

This repository shows signs of AI coding tools.

  • Claude Codefirst seen on or before 2026-05-01
    Named in .Rbuildignore: .claude
    Pull request it wrote: opened by a project member
    Commits: 19 by its own account · at least 43 crediting it in the message
  • GitHub Copilotfirst seen on or before 2026-05-05
    Commits: at least 22 crediting it in the message
Models named in its commits
  • Claude Opus 5.519 commits · Oct 2026
  • Claude Opus 4.815 commits · Sep 2026
  • Claude Opus 4.79 commits · May 2026
Counts are commits, not lines of code. Commits by a tool's accounts count once across all of its accounts. Commits crediting it are the largest count among its credit lines, a minimum.How this is detected·Detection ruleset v4 (updated 2026-09-27)

Dependencies

Declared dependencies
39 external dependencies (excludes base and recommended)

Installing telegramR adds 40 packages (26 with compiled code, 16 MB of source tarballs). Heaviest: promises 3.1 MB, Rcpp 1.8 MB, logger 1.1 MB.

Depends (1)
R >= 3.5.0
LinkingTo (1)
Enhances (0)
none
Reverse dependencies
0direct
0indirect

Nothing depends on this yet.

Datasets

People & History

People (1)
Author, Maintainer since 0.0.1 (2026), Copyright holder
Releases (2)

Pick two releases to compare their code metrics.

  • 0.0.2Latest
    record
    2026-09-30 · current release · diff ↗ ·
    added 1 export
    TelegramClient
  • 0.0.1
    record
    2026-06-02
  • R
    R 4.6.0 released · 2026-04-24

Package metadata

First published
2026-06-02
Total releases
2 / 1 yrs
License
MIT + file LICENSE OSI
Minimum R
≥ 3.5.0
Download size
3.3 MB

Cite

Cite this package

Run in R for the authors' preferred citation:

citation("telegramR")

The package provides a citation file that builds its entry when R runs it. Run citation() to see it.

The repository also keeps a CITATION.cff.

Cite the R Observatory

For a number measured here: a download total, a coverage figure, an archival date.

APA

Balamuta, J. J. (2026). R Observatory: Metrics for telegramR version 0.0.2 [Data set]. HJJB, LLC. Data release v2026-10-18. https://doi.org/10.5281/zenodo.21843040

From data release v2026-10-18, which the citation names so these numbers can be found later. More on citing and the projects behind them.

Report a problem with this page →

Privacy choices

These apply to this browser and are stored on this device only. Nothing about your choice is sent to us.

Read the privacy policy