Telegram RegisterThe public register of Telegram
Telegram profile photo for Zernio Developers

Channel

Zernio Developers

@zernio_dev

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

1,477subscribers

+886 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003320151971
TypeChannel
Username@zernio_dev
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 November 2026
Measurements held18
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/zernio_dev

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

5911,4771,0348 August 2026 — 591 subscribers8 August 2026 — 591 subscribers9 August 2026 — 592 subscribers17 August 2026 — 614 subscribers24 August 2026 — 645 subscribers1 September 2026 — 674 subscribers10 September 2026 — 708 subscribers28 September 2026 — 753 subscribers8 October 2026 — 773 subscribers16 October 2026 — 955 subscribers23 October 2026 — 1,123 subscribers27 October 2026 — 1,151 subscribers30 October 2026 — 1,190 subscribers2 November 2026 — 1,231 subscribers5 November 2026 — 1,263 subscribers8 November 2026 — 1,309 subscribers12 November 2026 — 1,385 subscribers17 November 2026 — 1,477 subscribers8 August 202617 November 2026
18 measurements spanning 102 days, net +886. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 458–1,610 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 21:571,477+92
12 Nov 2026, 12:591,385+76
8 Nov 2026, 00:191,309+46
5 Nov 2026, 00:361,263+32
2 Nov 2026, 08:261,231+41
30 Oct 2026, 09:461,190+39
27 Oct 2026, 00:591,151+28
23 Oct 2026, 19:561,123+168
16 Oct 2026, 17:51955+182
8 Oct 2026, 19:02773+20
28 Sept 2026, 10:21753+45
10 Sept 2026, 18:56708+34
1 Sept 2026, 09:14674+29
24 Aug 2026, 15:08645+31
17 Aug 2026, 10:13614+22
9 Aug 2026, 00:50592+1
8 Aug 2026, 03:18591no change
8 Aug 2026, 00:24591first reading

Engagement

20 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

6 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤466.7%
👍116.7%
🔥116.7%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 6 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 5 August 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 15:52 UTC56 viewsread 8 August 2026

WhatsApp connect now rejects Zernio-provisioned numbers that are pinned to a different profile with a 409 conflict. This prevents accidentally connecting a provisioned WhatsApp number from the wrong profileId. If you need to connect it on another profile, move the number first, then retry the connect. New 409 responses: • GET /v1/connect/whatsapp (when profileId doesn’t match the provisioned number’s profile) • POS…

Signed Social Media Connector

7 Aug 2026, 15:40 UTC56 viewsread 8 August 2026

Google Business location selection/updates now validate the provided Google account resource name and will reject mismatches. If you pass an account identifier to speed up location resolution for large GBP accounts, the API will now return 400 when the provided account is not one of the accounts the connection manages. Applies to: • POST /v1/connect/googlebusiness/select-location with accountId • PUT /v1/accounts/{…

Signed Social Media Connector

7 Aug 2026, 15:23 UTC52 viewsread 8 August 2026

POST /v1/ads/boost now supports attaching a boost to an existing Meta ad set via adSetId, and adds Meta support for CTA destinations via linkUrl + callToAction. This lets you refresh/boost an existing post while keeping the ad set’s learning phase (attach to an existing ad set instead of provisioning a new campaign/ad set). Key changes: • Meta-only attach: send adSetId to attach under an existing ad set • When adSe…

Signed Social Media Connector

7 Aug 2026, 14:17 UTC57 viewsread 8 August 2026

New endpoint: PATCH /v1/whatsapp/phone-numbers/{id}/profile to move a provisioned number to another profile. This re-homes the number and any associated accounts together (so you don’t split the number across profiles by moving only the social account). Send { "profileId": "..." } where id is the phone number record id from GET /v1/phone-numbers (not an account id). Response may include movedPlatforms with values …

Signed Social Media Connector

7 Aug 2026, 13:57 UTC65 viewsread 8 August 2026

PUT /v1/ads/campaigns/{campaignId} now supports Google campaigns (in addition to Meta) and enforces platform-level field support (unsupported fields return 400, not silently ignored). For Google, you can set campaign bidding via: • platform: google • bidStrategy (Meta + Google) • bidAmount (Google only; required for LOWEST_COST_WITH_BID_CAP and COST_CAP) • roasAverageFloor (Google only; required for LOWEST_COST_WITH…

Signed Social Media Connector

7 Aug 2026, 08:54 UTC84 viewsread 8 August 2026

Message reactions are now supported on Instagram, Facebook Messenger, and Slack via the existing reactions endpoints. You can add/remove reactions across more inbox channels, and reaction webhooks now cover these platforms too. Use: • POST /v1/inbox/conversations/{conversationId}/messages/{messageId}/reactions with emoji • DELETE /v1/inbox/conversations/{conversationId}/messages/{messageId}/reactions with accountId…

Signed Social Media Connector

7 Aug 2026, 08:12 UTC80 viewsread 8 August 2026

Instagram follow checks are now available via GET /v1/accounts/{accountId}/follow-status/{userId}. This resolves the follow relationship (when Meta allows it) and returns isFollower (can be null when unknown) plus basic public counters; use refresh=true to bypass the short cache. Key fields: • isFollower: true | null (null = unknown, never “no”) • unavailableReason: consent_required | dm_access_disabled | not_messa…

Signed Social Media Connector

6 Aug 2026, 13:04 UTC89 views1 reactionsread 8 August 2026

GET /v1/comment-automations/{automationId}/logs now returns non-matching comment diagnostics via a new misses object. Use misses to see how many comments reached the automation but matched none of its keywords (and a few recent samples) to troubleshoot keyword/exclusion setups. New response fields: • misses.total • misses.retentionDays • misses.samples[]: commentText, commenterName, excludedBy, at Request validati…

❤1

Signed Social Media Connector

6 Aug 2026, 12:34 UTC89 views1 reactionsread 8 August 2026

PATCH /v1/comment-automations/{automationId} now accepts trigger to control what fires an automation. You can switch an automation between comment-based and story-reply-based triggers; changing it will detach the automation from its currently bound post/story unless the same request sets a new binding. Set trigger to: • comment • story_reply (Instagram only) View documentation

❤1

Signed Social Media Connector

6 Aug 2026, 12:16 UTC85 views1 reactionsread 8 August 2026

Ads analytics now includes funnel step counts, an engagement breakdown, and cost per ThruPlay. This makes it easier to report on Meta ads without parsing/deduping raw actions keys (and avoids double-counting), and adds a direct cost metric for ThruPlays. New fields in AdMetrics: • costPerThruplay • funnel (ref AdFunnelCounts): landingPageViews, contentViews, searches, wishlistAdds, cartAdds, checkoutsInitiated, pay…

❤1

Signed Social Media Connector

6 Aug 2026, 12:08 UTC85 viewsread 8 August 2026

Comment-to-DM automations now support more precise keyword matching and exclusions via matchMode=word, plus new fields excludeKeywords and typoTolerance. This lets you avoid accidental triggers (e.g., keyword app no longer firing on happy) and optionally match close misspellings when using word-based matching. Use matchMode: • contains • word • exact New fields: • excludeKeywords: string[] - comments matching thes…

Signed Social Media Connector

6 Aug 2026, 11:46 UTC85 viewsread 8 August 2026

LinkedIn connected accounts now include additional profile details in SocialAccount.metadata.profileData (refreshed on each daily snapshot). This lets you read LinkedIn bio/headline and vanity slug info directly from the account object without extra lookups. Key fields: • metadata.profileData.bio (nullable) • metadata.profileData.extraData.vanityName (personal accounts) • metadata.organizationInfo.vanityName (organ…

Signed Social Media Connector

Showing the 12 most recent of 20 posts we hold for @zernio_dev. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 17 November 2026 — this entry's latest reading, not the date you are reading this.

“Zernio Developers” (@zernio_dev), 1,477 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/zernio_dev.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.