desllre

ru telegram news detection

Classify & tag

This receipt records checks for this exact file; it does not prove safety or that it will run on your device. Read the receipt

Model details
text classificationLicense: mitSHA-256 recorded for 7 of 10 filessafetensors · BIN
Quick answer: compatibility and sources

Can I run ru_telegram_news_detection on my computer?

It depends on your memory, processor, file format and runtime. A download is not confirmed by the current file evidence; inspect the file record before trying it. A file-size fit is an estimate, not a successful run or speed promise. Read the license before use.

ru_telegram_news_detection is an open-weights language model for text classification. Model weights are learned parameters; a runtime loads them. A hosted file is an individual file Hugging Bay can serve. SHA-256 identifies exact file bytes. The availability date above applies to this file record, not the upstream metadata update date.

As of the recorded file availability check on .

Recorded SHA-256 for model.safetensors: 75478cf129bd09a56a0b518ef68673ff66af4eccb7baa2c98e31d7fd63af8f84. Exact file evidence · Machine-readable source facts · Run evidence and any recorded receipts. A checksum fingerprints only the named file bytes; it does not prove safety, quality, a complete multi-file selection or a successful run.

Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/lib/model-page-template.mjs, apps/web/lib/model-page-v3.mjs, apps/web/lib/aeo-page.mjs · Full revision record

Model metadata: As of at the model source. Popularity counters are source-reported, not measured by Hugging Bay. Availability checked .

Key facts

Catalog record
Summarizes upstream metadata; it is not itself a download or run receipt.
File evidence
Lists exact filenames, availability and any recorded SHA-256 for individual files.
Run evidence
Reports measured results only when a receipt exists for named file bytes and a setup; otherwise unmeasured.
Checksum scope
SHA-256 fingerprints one file’s bytes; it does not prove safety, quality or a multi-file bundle.

Evidence you can inspect (plain text)

  • This page’s quick answer names the file record for hf-model-desllre-ru-telegram-news-detection.
  • Open /artifact/hf-model-desllre-ru-telegram-news-detection/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-desllre-ru-telegram-news-detection for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-desllre-ru-telegram-news-detection/card.md for machine-readable source facts (not a runtime test).
  • A matching checksum on this page fingerprints only the named bytes shown in file evidence.

Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.

Which date applies to which fact

  • File availability check:
  • Committed page-copy sources:
  • Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
  • Run receipts: Only on /evidence pages when recorded; otherwise unmeasured

Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.

Requirements and source record
desllre/ru_telegram_news_detection

Content controls: not assessed.

The catalog lists this model for sorting text into categories. Catalog sources: license, cardMetadata.license, baseModel, task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileSizeSHA-256SourceDownload
Weights
model.safetensors116.8 MB
75478cf1…63af8f8475478cf129bd09a56a0b518ef68673ff66af4eccb7baa2c98e31d7fd63af8f84
Download availability is being checked.File metadata
training_args.bin5.71 KB
d801fe3a…e80aa853d801fe3a3eefcd38db929de8349be3e03c54a4ce6742a3313de98f95e80aa853
Download availability is being checked.File metadata
Tokenizer & config
config.json705 bytes
d317d6cd…47a93d69d317d6cd239c779c15365688ef226b7bfedbe8ce4e01adbe4138296147a93d69
Download availability is being checked.File metadata
encoder.pkl260 bytes
184ef68d…ee584ea1184ef68d6d5ae2d3efc9e4459b82ad50cc3e147b6cc2b75c545422cbee584ea1
Download availability is being checked.File metadata
special_tokens_map.json695 bytes
5d5b662e…a350503a5d5b662e421ea9fac075174bb0688ee0d9431699900b90662acd44b2a350503a
Download availability is being checked.File metadata
tokenizer.json2.41 MB
577bab11…8e288d4e577bab111ebe028ed7476fa89af3af3a385670311816938253038fc48e288d4e
Download availability is being checked.File metadata
tokenizer_config.json1.46 KB
71b22b16…825c713571b22b163773e6d2a3bc53236a6dca9245f2e0422b09e2d9597dbf02825c7135
Download availability is being checked.File metadata
vocab.txt1.08 MB—Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB—Download availability is being checked.File metadata
README.md2.61 KB—Download availability is being checked.File metadata

Check a download

In the folder where you saved config.json, run:

macOS
shasum -a 256 -- 'config.json'
Linux
sha256sum -- 'config.json'
Windows
Get-FileHash -LiteralPath 'config.json' -Algorithm SHA256

Compare the result with the recorded SHA-256.