Channel
@zernio_dev
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
645subscribers
+54 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003320151971 |
|---|---|
| Type | Channel |
| Username | @zernio_dev |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/zernio_dev |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 15:08 | 645 | +31 |
| 17 Aug 2026, 10:13 | 614 | +22 |
| 9 Aug 2026, 00:50 | 592 | +1 |
| 8 Aug 2026, 03:18 | 591 | no change |
| 8 Aug 2026, 00:24 | 591 | first reading |
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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 6 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (5 August 2026 – 7 August 2026) |
| Views total | 1,665 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 03:18 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
6 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 66.7% | |
| 👍 | 1 | 16.7% | |
| 🔥 | 1 | 16.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 6reactions 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.
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
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
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
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
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
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
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
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
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
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
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
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“Zernio | Developer News” (@zernio_dev), 645 subscribers as measured 24 August 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.