Telegram channel bridge as a new vacancy source — no API, no scraping

[DENISmer]

Hi Santiago and team — thanks for career-ops.

A huge share of dev vacancies today are posted in public Telegram channels before (or instead of) hitting Ashby/Greenhouse/Lever. For me and the community I'm part of, this is the primary channel for finding remote and product jobs, and career-ops currently has no way to ingest them. I'd like to contribute a Telegram bridge to fix that.

I know CONTRIBUTING.md rejects scraping PRs, so up front: this proposal does not use the Telegram API and does not scrape anything restricted. It only reads what Telegram itself publishes openly.

A few examples of channels this would unlock

• @devops_jobs
• @forallhr
• @jobs_in_tech
• @python_jobs
• @golang_jobs
• @react_jobs
• @remoteok_io

…and dozens more that any user can add to their own config.

How data is obtained — within Telegram's allowed surface

Every public Telegram channel is published by Telegram itself at https://t.me/s/{channel_username} as plain HTML — viewable by anyone with no login, intended to be linkable and indexable by search engines. This is Telegram's official public surface, the same one Google crawls.

The bridge does exactly one thing: a normal HTTPS GET against that URL, the same request a logged-out browser makes. No API, no auth, no rate-limit games, no private content.

For private channels the user is already a member of, there's no automation at all — the user pastes/forwards a message into /career-ops tg, identical UX to the existing /career-ops {paste a JD} flow.

What gets added

templates/telegram.example.yml     # user copies → telegram.yml, lists channels
modes/scan-telegram.md             # mode/skill: normalize TG posts → offers
scan/telegram.mjs                  # public-preview fetcher
docs/TELEGRAM.md                   # short setup doc

No .env changes. No new credentials.

What this is NOT

• ❌ Telegram Bot API
• ❌ Telegram Client API / MTProto
• ❌ Reading private channels without membership
• ❌ Auto-applying or messaging anyone
• ❌ Collecting personal data of channel posters

Questions before I start

1. Does fetching the public t.me/s/ web preview clear your "no scraping" bar, or would you prefer I ship only the manual-paste mode in v1?
2. New top-level /career-ops scan-telegram, or fold into the existing /career-ops scan?

Happy to open a draft PR once direction is clear. Thanks!