Telegram RegisterThe public register of Telegram
Telegram profile photo for FirebirdSQL

Channel

FirebirdSQL

@firebirdsql

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

683subscribers

-5 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-1001176622432
TypeChannel
Username@firebirdsql
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 November 2026
Measurements held12
Confirmed unchanged2 times, most recently 18 November 2026
On Telegramt.me/firebirdsql

Topic

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.

Growth

682689685.57 August 2026 — 688 subscribers8 August 2026 — 688 subscribers8 August 2026 — 689 subscribers16 August 2026 — 688 subscribers30 August 2026 — 687 subscribers9 September 2026 — 688 subscribers16 September 2026 — 685 subscribers30 September 2026 — 683 subscribers10 October 2026 — 682 subscribers24 October 2026 — 683 subscribers1 November 2026 — 684 subscribers9 November 2026 — 683 subscribers6837 August 20269 November 2026
12 measurements spanning 94 days, net -5. 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 681–690 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Nov 2026, 13:09683-1
1 Nov 2026, 10:16684+1
24 Oct 2026, 15:21683+1
10 Oct 2026, 16:17682-1
30 Sept 2026, 14:20683-2
16 Sept 2026, 08:16685-3
9 Sept 2026, 09:18688+1
30 Aug 2026, 15:57687-1
16 Aug 2026, 03:17688-1
8 Aug 2026, 14:21689+1
8 Aug 2026, 02:30688no change
7 Aug 2026, 21:08688first reading

Engagement

20 posts held, back to 12 March 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 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 20 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

146 reactions across 20 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍146100.0%

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 20 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 146 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 12 March 2026 to 1 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

1 Aug 2026, 17:39 UTC344 views6 reactionsread 8 August 2026

FBSimCity v0.6.0 — the replication district The explorable city of Firebird internals now has a replication quarter. Firebird has no write-ahead log to ship, so its replication is logical: as each transaction commits, the changes themselves are journalled into segments, sealed, and replayed on the replica in commit order. Three buildings: • Journal Yard — where commits are journalled. If the segments cannot be shi…

👍6

31 Jul 2026, 17:06 UTC378 views6 reactionsread 8 August 2026

cl-firebird v1.0.0 released — a pure Common Lisp driver for Firebird 3.0/4.0/5.0/6.0 with full 1:1 feature parity with node-firebird. No libfbclient, no FFI — it speaks the Firebird wire protocol directly over TCP (up to protocol 20) and runs on SBCL, CCL, and other ANSI CL implementations. Includes connection URIs, thread-safe connection pooling, named placeholders, custom type parsers (type-cast), streaming cursor…

👍6

31 Jul 2026, 17:03 UTC338 views13 reactionsread 8 August 2026

FBSimCity — an explorable city that shows how Firebird actually works https://mariuz.github.io/FBSimCity/ An interactive visualization of Firebird internals: an isometric city where every building is a subsystem from the classic "Conceptual Architecture for Firebird" paper (Chan & Yashkir), and queries commute through the pipeline as glowing particles — REMOTE harbor, Y-valve, DSQL, JRD, with the lock manager tower a…

👍13

31 Jul 2026, 16:51 UTC341 views6 reactionsread 8 August 2026

node-firebird v2.6.0 - v2.14.0: roadmap complete, issue tracker at zero Eight releases in under a week for the pure-JavaScript Node.js driver: Firebird 6.0 Protocol 20 support, the sporadic Srp auth failure fixed, single-byte codepage support (WIN125x, ISO8859_x, KOI8, DOS866), Firebird 4 batch API bulk inserts, multi-host pooling (poolCluster) for replica setups, and more. All 47 open issues closed. https://mapopa…

👍6

24 Jul 2026, 03:21 UTC627 views12 reactionsread 8 August 2026

FlameRobin Release 26.7.7 - Milestone Release https://github.com/mariuz/flamerobin/releases/tag/v26.7.7

👍12

8 Jul 2026, 14:19 UTC974 views15 reactionsread 8 August 2026

IBPhoenix is pleased to announce the release of a new free ebook: Practical Firebird Performance Diagnostics: A Structured Approach Unlike traditional performance tuning guides, this ebook focuses on the reasoning behind successful diagnostics. It introduces a structured framework that helps Firebird professionals move from observed symptoms to defensible explanations by classifying problems, selecting appropriate in…

👍15

1 Jun 2026, 09:04 UTC≈1,210 views7 reactionsread 8 August 2026

Release 2.7.10 of ibx4Lazarus https://github.com/MWASoftware/ibx4lazarus/releases/tag/R2-7-10

👍7

7 May 2026, 11:05 UTC≈1,550 views5 reactionsread 8 August 2026

https://firebirdsql.org/en/news/new-firebird-docker-images-and-update-for-1-step-firebird-linux-installation-scripts

👍5

7 May 2026, 05:59 UTC≈1,390 views6 reactionsread 8 August 2026

Release 2.7.9 of IBX for Lazarus https://github.com/MWASoftware/ibx4lazarus/releases/tag/R2-7-9

👍6

28 Apr 2026, 21:47 UTC≈1,350 views11 reactionsread 8 August 2026

New Firebird Docker Images : The Official firebirdsql/firebird Docker images have just shipped a major overhaul. https://groups.google.com/g/firebird-general/c/5gPXXp7m1aM

👍11

26 Apr 2026, 16:48 UTC≈1,200 views7 reactionsread 8 August 2026

Flamerobin 26.4.0 This update focuses heavily on UI responsiveness, workflow automation, and a significant expansion for macOS users. Key improvements include better handling of large datasets and several quality-of-life enhancements for database registration and management. Switched to Year.Month.Version releases https://github.com/mariuz/flamerobin/releases/tag/26.4.0

👍7

24 Apr 2026, 06:51 UTC≈1,110 views5 reactionsread 8 August 2026

Pre-release Firebird Docker Images -- Now with Firebird 6 Snapshot (For testing Not Production) https://groups.google.com/g/firebird-general/c/KefyO0KWKE4

👍5

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

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

“FirebirdSQL” (@firebirdsql), 683 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/firebirdsql.

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.