Channel
@EinatMeyronCyberResilience
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,532subscribers
-7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001188949285 |
|---|---|
| Type | Channel |
| Username | @EinatMeyronCyberResilience |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/EinatMeyronCyberResilience |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 09:40 | 2,532 | -5 |
| 10 Sept 2026, 00:39 | 2,537 | +8 |
| 4 Sept 2026, 16:02 | 2,529 | -4 |
| 31 Aug 2026, 23:27 | 2,533 | +1 |
| 28 Aug 2026, 16:48 | 2,532 | +1 |
| 25 Aug 2026, 10:38 | 2,531 | -2 |
| 22 Aug 2026, 20:34 | 2,533 | -3 |
| 19 Aug 2026, 10:58 | 2,536 | +1 |
| 13 Aug 2026, 06:57 | 2,535 | -2 |
| 9 Aug 2026, 20:31 | 2,537 | -2 |
| 7 Aug 2026, 01:00 | 2,539 | no change |
| 6 Aug 2026, 13:21 | 2,539 | first reading |
20 posts held, back to 13 July 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 2 pages 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
30 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 36.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 11 | 36.7% | |
| ❤ | 6 | 20.0% | |
| 👏 | 6 | 20.0% | |
| 🔥 | 4 | 13.3% | |
| 🤯 | 2 | 6.67% | |
| 👎 | 1 | 3.33% |
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 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 30 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 13 July 2026 to 6 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.
https://www.linkedin.com/posts/einatmeyron_%D7%90%D7%A4%D7%A8%D7%95%D7%A4%D7%95-%D7%94%D7%AA%D7%A7%D7%9C%D7%94-%D7%94%D7%A9%D7%91%D7%95%D7%A2-%D7%91%D7%91%D7%A0%D7%A7-one-zero-%D7%94%D7%99%D7%A4%D7%95%D7%AA%D7%98%D7%99%D7%AA-share-7491098565763719168-oSTp/?utm_source=share&utm_medium=member_android&rcm=ACoAAABHQioBvhxJhprGDZIt0bI_zfRJrMrlxQ4 בואו נדבר קצת מספרי RTO.
עוד בשולי האירוע אתמול - מבינה שיש פער בהבנת הסיכון והמהות. אז בואו רגע נהדק את המשמעות של תפיסת סיכוני סייבר עסקיים. לא מדובר בעוד מנגנוני הגנה. כאלה, כולנו יודעים, יש למכביר מדובר בהבנת וזיהוי התהליך שחייבים להגן עליו. כשזה מבוצע, מתאימים לתהליך המסויים, בארגון המסויים שלא דומה לאחר, גם אם הוא סקטוריאלי - את ההגנות התהליכיות המתאימות. למשל ניטור יעודי, בקרות יעודיות. על זה - אם לא מגדירים RTO אפקטיבי לתהליך המס…
👍1
*לא. לא מכירה מישו בבנק. *כן, אם מישו רלוונטי בבנק רוצה להעביר עדכון, מידע, לקיים שיחה - בשמחה. חברו ביננו.
היתה לי שיחה עם מישו שפנה בפרטי וביקש להבין למה מפריע לי שיש תקלה ושזה בסדר וזו הזדמנות מצוינת לחזור ולהסביר - סיכוני סייבר מתבססים על פוטנציאל נזק. העובדה שברגע נתון, בעיתוי מאוד בעייתי, אני ועוד כמה אלפי לקוחות הבנק, לא הצלחנו לגשת לשירות שמחוייב בזמינות מלאה, כדי למנוע מאיתנו ומהבנק סיכון משפטי-כספי מיותר, זו תקלה. העובדה שמדובר בתקלה ממושכת - דמיינו שאין דרך לפנות למוקד 100 או לחדר מיון במשך שעה וחצי - היא התקל…
👏4❤2
שעה.
לא תקין. לא. ממש לא תקין ולא מקובל. כמה נזק עיכוב כזה עלול לייצר.. רבע שעה אחרי פתיחת מסחר. לא מקובל כשזה תפעולי ומפחיד אם זה תוקף.
https://www.linkedin.com/posts/einatmeyron_%D7%91%D7%9E%D7%A2%D7%A8%D7%99%D7%91-%D7%94%D7%9B%D7%99%D7%A0%D7%95-%D7%9B%D7%9E%D7%94-%D7%A8%D7%99%D7%9C%D7%A1%D7%99%D7%9D-%D7%A4%D7%95%D7%9C%D7%99%D7%98%D7%99%D7%99%D7%9D-%D7%9E%D7%A9%D7%A4%D7%98%D7%99%D7%99%D7%9D-ugcPost-7490291337293082625-dGn8/?utm_source=share&utm_medium=member_android&rcm=ACoAAABHQioBvhxJhprGDZIt0bI_zfRJrMrlxQ4
❤1
https://www.linkedin.com/posts/einatmeyron_%D7%A7%D7%A8%D7%99%D7%A1%D7%AA-%D7%A7%D7%A8%D7%9F-%D7%94%D7%92%D7%99%D7%93%D7%95%D7%A8-situational-awareness-%D7%A9%D7%9C-ugcPost-7488923763099504640-ZcUr/?utm_source=share&utm_medium=member_android&rcm=ACoAAABHQioBvhxJhprGDZIt0bI_zfRJrMrlxQ4
מעניין אם זה בידיעת ואישור משרד הבריאות שכזכור אסר לפני מס' שבועות על בתי החולים לעבוד עם AI. כרגיל, כוחות השוק עושים את שלהם, יותר מכל התערבות רגולטורית.
❤1👍1
לא האירוע הראשון שלהם. תזכורת כאן. מאפריל 2018.
תקלה ביורוקונטרול: שיבושים בטיסות ברחבי אירופה רשות שדות התעופה עדכנה כי בעקבות תקלה במערכת Eurocontrol בבריסל, צפויים שיבושים בלוח הטיסות במרחב האווירי האירופי. כתוצאה מהתקלה, ייתכנו עיכובים ממושכים בטיסות היוצאות והנכנסות בשעות הקרובות. הנוסעים מתבקשים להתעדכן מול חברות התעופה לגבי מועדי ההמראה וכל שינוי בלוחות הזמנים. https://t.me/yediotnews25
כתבת יחסי הציבור של הרשות להגנת הפרטיות שעושה סיבוב על קופח מאוחדת הזכירה לי את ההמתנה עם הדיווח על הפרת התקנות בחברת איתוראן ב2018. ממש במאי. אתם זוכרים מה קרה במאי 2018, נכון? אז כתבתי את זה כבר לפני כמה ימים. תדביקו אצל כל עו"ד שמנסה להתפרנס על חשבון הפחדות טיפשיות. https://www.linkedin.com/posts/einatmeyron_cyberresilience-privacy-dpo-activity-7485370848628072448-vJm-?utm_source=share&utm_medium=member_android&…
Showing the 12 most recent of 20 posts we hold for @EinatMeyronCyberResilience. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Cyber Resilience - Einat Meyron” (@EinatMeyronCyberResilience), 2,532 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/EinatMeyronCyberResilience.
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.