Channel
@perlkohacon
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
60subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001561410575 |
|---|---|
| Type | Channel |
| Username | @perlkohacon |
| Description | YAPC::Europe with KohaCon together! We did it! Find talks here: https://www.youtube.com/playlist?list=PLa9kvrI3VLf7ZvLvJk9EtlnF2OVETvddm it was as planned, in Helsinki, August 2023: 14th-16th: talks days 17th-18th: workshops and extras perlkohacon.fi |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/perlkohacon |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 05:16 | 60 | no change |
| 7 Aug 2026, 22:57 | 60 | first reading |
19 posts held, back to 26 June 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 8 January 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
7 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 57.1% | |
| ❤ | 3 | 42.9% |
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 5 of the 19 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 26 June 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.
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…
this weekend, another very dense Perl community, yapcjapan: 14-15/11 YAPC::Fukuoka 2025 (ref by JF)
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!
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)
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…
And more Perl and Koha events, this year:
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
Koha minor release for latest version:v25.05.02 released Koha 25.05.02 is a bugfix/maintenance release. It includes 25 enhancements, 96 bugfixes. https://koha-community.org/koha-25-05-02-released/ and other releases for older versions: https://koha-community.org/news/
Worth to note in memoriam of mst ( https://t.me/PerlNews/46 ) sad news but worth to reveal respect for mst, especially, for DBIx::Class, for example, what Koha Community living with! Thank you, mst!
Signed Andrii Nugged
https://t.me/PerlNews/42
❤1
Dec 18, Happy Birthday Perl! ... it started in 1987, 37 years ago. === Happy Birthday, Perl! Today marks 37 years since Larry Wall first released this remarkable language. Over nearly four decades, Perl has grown into a powerful, versatile toolkit for everything from system administration to web development, thriving in a vibrant ecosystem that welcomes innovation. Far from resting on its laurels, Perl’s communit…
❤2
DAY 2 STREAM of 2024.kohacon.org: https://www.youtube.com/live/ByaJABOE5dU // #KohaCon #Koha #Perl #KohaCon24 #PerlKohaCon
Showing the 12 most recent of 19 posts we hold for @perlkohacon. 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Perl and Koha conference in HELSINKI, 2023” (@perlkohacon), 60 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/perlkohacon.
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.