Telegram RegisterThe public register of Telegram
Telegram profile photo for спасибо за кривой айос клиент

Channel

спасибо за кривой айос клиент

@funny_ios_bugs

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

100subscribers

+46 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004300854191
TypeChannel
Username@funny_ios_bugs
Created5 August 2026measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live4 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/funny_ios_bugs

Growth

5410177.56 August 2026 — 54 subscribers7 August 2026 — 75 subscribers9 August 2026 — 75 subscribers13 August 2026 — 96 subscribers19 August 2026 — 101 subscribers27 August 2026 — 98 subscribers4 September 2026 — 100 subscribers1006 August 20264 September 2026
7 measurements spanning 30 days, net +46. 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 47–108 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 21:17100+2
27 Aug 2026, 17:3498-3
19 Aug 2026, 20:53101+5
13 Aug 2026, 02:1596+21
9 Aug 2026, 21:1575no change
7 Aug 2026, 00:2275+21
6 Aug 2026, 02:0254first reading

Engagement

11 posts held, back to 5 August 2026the 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 11 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

54 reactions across 9 posts, in 10 distinct kinds. The most used accounts for 29.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁1629.6%
🤣1222.2%
814.8%
🍓59.26%
👏35.56%
😘35.56%
🆒23.70%
🤯23.70%
🥰23.70%
👎11.85%

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 9 of the 11 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 54 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 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, 06:34 UTC317 views3 reactionsread 9 August 2026

а ещё зачем-то этого бота забанили и автору бота выдали бан в ботфазере ¯\_(ツ)_/¯ неплохой такой айос баг вышел

😘3

6 Aug 2026, 14:39 UTC497 views14 reactionsread 9 August 2026
Photo

кстати кто ворму это сообщение ^ переслал перешлите также что он тупоголовый еблан который вообще не понимает как телеграм работает изнутри и не понимает что он вообще пишет

🤣12😁2

6 Aug 2026, 11:07 UTC558 views1 reactionsread 9 August 2026

Timestamp issues are fixed and will be released shortly

1

6 Aug 2026, 11:07 UTC529 views3 reactionsread 9 August 2026

в новой версии iOS-клиента баг исправлен правда когда она релизнется — да хуй его знает, так что страдать осталось недолго

3

5 Aug 2026, 19:40 UTC≈1,260 views4 reactionsread 9 August 2026

я сильно не изучал и не тестировал но кажется этот краш работает только если сообщение находится в канале, и пост из канала пересылают — если просто так скопировать он не у всех крашит почему то. странная хуйня короче

🆒2👎1😁1

5 Aug 2026, 19:09 UTC≈1,540 views10 reactionsread 9 August 2026

конкретно этот пост с шансом 100% крашит у меня на стабильной версии айоса; пост ниже с шансом 50/50 ¯\_(ツ)_/¯

😁5👏3🥰2

5 Aug 2026, 19:09 UTCviews —

спасибо за кривой айос клиент pinned «Upgrade price timeline 21:32 MSK → 1M⭐️ 22:32 MSK → 575.3k⭐️ 23:32 MSK → 337.1k⭐️ 00:32 MSK → 201.2k⭐️ 01:32 MSK → 122.5k⭐️ 02:32 MSK → 76.1k⭐️ 03:32 MSK → 48.3k⭐️ 04:32 MSK → 31.3k⭐️ 05:32 MSK → 20.8k⭐️ 06:32 MSK → 14.2k⭐️ 07:32 MSK → 9897⭐️ 08:32 MSK →…»

5 Aug 2026, 19:02 UTC≈1,870 views7 reactionsread 9 August 2026

NFT upgrades available 🎁 30000⭐️— upgrade for 1M⭐️→ 2500⭐️ @ 13:32 MSK Monitor upgrade price changes at @GiftChangesUpdates 🐈‍⬛ @GiftChanges • Portals ❤️ • Tonnel 🌪

😁4🍓3

5 Aug 2026, 19:02 UTC≈2,580 views8 reactionsread 9 August 2026

Upgrade price timeline 21:32 MSK → 1M⭐️ 22:32 MSK → 575.3k⭐️ 23:32 MSK → 337.1k⭐️ 00:32 MSK → 201.2k⭐️ 01:32 MSK → 122.5k⭐️ 02:32 MSK → 76.1k⭐️ 03:32 MSK → 48.3k⭐️ 04:32 MSK → 31.3k⭐️ 05:32 MSK → 20.8k⭐️ 06:32 MSK → 14.2k⭐️ 07:32 MSK → 9897⭐️ 08:32 MSK → 7121⭐️ 09:32 MSK → 5287⭐️ 10:32 MSK → 4067⭐️ 11:32 MSK → 3258⭐️ 12:32 MSK → 2746⭐️ 13:32 MSK → 2500⭐️🎁 🐈‍⬛ @GiftChanges • Portals ❤️ • Tonnel 🌪

😁4🍓2🤯2

Showing the 11 most recent of 11 posts we hold for @funny_ios_bugs. 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.

Mentions

Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 4 September 2026 — this entry's latest reading, not the date you are reading this.

“спасибо за кривой айос клиент” (@funny_ios_bugs), 100 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/funny_ios_bugs.

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.