Telegram RegisterThe public register of Telegram
Telegram profile photo for Perl News (+ some Koha and AI)

Channel

Perl News (+ some Koha and AI)

@PerlNews

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

35subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001998865343
TypeChannel
Username@PerlNews
CreatedBetween 1 November 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live29 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/PerlNews

Growth

343534.57 August 2026 — 34 subscribers11 August 2026 — 34 subscribers29 August 2026 — 35 subscribers7 August 202629 August 2026
3 measurements spanning 22 days, net +1. 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 34–35 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 10:5435+1
11 Aug 2026, 00:1534no change
7 Aug 2026, 13:5334first reading

Engagement

15 posts held, back to 25 October 2024the 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.

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

Reaction mix

13 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 30.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥430.8%
323.1%
👍215.4%
😢215.4%
🙏215.4%

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

Measured over the 15 most recent posts we hold, published 25 October 2024 to 8 January 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

8 Jan 2026, 12:22 UTC283 viewsread 11 August 2026
Photo

https://www.tiobe.com/tiobe-index/ https://www.tiobe.com/tiobe-index/perl/ What TIOBE’s creator says about the “Perl comeback”: - A big technical driver may be the huge number of Perl books on Amazon (and Amazon has serious weight in TIOBE’s search-hit methodology). - A possible real reason (more speculative): the naming/positioning finally settled — Perl 5 is “Perl”, and Perl 6 became Raku. So: treat TIOBE as an a

18 Nov 2025, 23:53 UTC82 viewsread 11 August 2026

Well now it is! from HTTPs://www.londonperlworkshop.com === Now For 2025 Let's do it again. We can now confirm event details... WHEN • 29th November 2025, WHERE: • The Gulbenkian and The Club Room, ISH Venues, 229 Great Portland Street, London, W1W 5PN, United Kingdom. Address on Google Maps: [HTTPs://maps.app.goo.gl/oQqV1PgYQMnKHEDs9] More Venue Details here: [HTTPs://act.yapc.eu/lpw2025/venue.h

17 Nov 2025, 22:49 UTC65 viewsread 11 August 2026

The Act website is now up and accepting talk submissions. We still have some slots open! https://act.yapc.eu/lpw2025

11 Nov 2025, 06:02 UTC230 viewsread 11 August 2026

nowadays it's easy to track those which possible remotely, so, Perl (and Koha/Dev people), if you can't be there by person — track channels, talks, give some shout and participate in dicsussions online around!

11 Nov 2025, 05:59 UTC212 viewsread 11 August 2026

and we glad to remark reviving and now returning to be regular, LPW, "yet another big Perl mongers area": London Perl & Raku Workshop 2025 29th November 2025, The Trampery, Old Street, London http://londonperlworkshop.com/ https://act.yapc.eu/lpw2025/ (ref by JF)

11 Nov 2025, 05:57 UTC269 viewsread 11 August 2026

Uprising and actively developed Perl product, really related and meaningful for Perl nowadays: KohaCon 2025 in New Zealand: https://2025.kohacon.org Te Hokinga Mai | Coming Home – Celebrating 25 Years of Koha 17-23 November 2025, Te Whanganui-a-Tara | Wellington, Aotearoa New Zealand. Join us in celebrating 25 years of open source innovation and community collaboration. Together, we weave the past and future of K

11 Nov 2025, 05:54 UTC111 viewsread 11 August 2026

this weekend, another very dense Perl community, yapcjapan: 14-15/11 YAPC::Fukuoka 2025 (ref by JF)

11 Nov 2025, 04:32 UTC174 viewsread 11 August 2026

German Perl Workshop 2026 Berlin. 16-18 March 2026 https://act.yapc.eu/gpw2026/news —————————————— One of the most active and rather big Perl community gathering nowadays. Koha people worth to pay attention. - - src by Corion (https://t.me/perlcon/8510): German Perl Workshop 2026 - in Berlin from 16.-18. March 2026: https://act.yapc.eu/gpw2026/news

9 Jul 2025, 17:41 UTC134 views2 reactionsread 11 August 2026

... mst passed away :*( https://www.shadowcat.co.uk/2025/07/09/ripples-they-cause-in-the-world It is worth to denote his remarkable contribution for Perl, and personal acquaintance. mst! Your name echoes across CPAN and every Perl place. I met you at my first conference, and since then your voice was always loudly distinguishable, heard from far away at every venue. Your talks were different, special, razor-sharp,

😢2

3 Jul 2025, 22:13 UTC98 views2 reactionsread 11 August 2026
Photo

press "Y". GREET THE 5.42.0 ! Perl v5.42.0 released. https://perldoc.perl.org/5.42.0/perldelta

🔥2

Showing the 12 most recent of 15 posts we hold for @PerlNews. 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.

Citation-graph rank

Citation-graph rank — 693,116 of 1,628,524entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Perl News (+ some Koha and AI)” (@PerlNews), 35 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/PerlNews.

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.