Telegram RegisterThe public register of Telegram
Telegram profile photo for RubyOfSec 2.0 (0x177)

Channel

RubyOfSec 2.0 (0x177)

@MoreRubyOfSec

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

73subscribers

-2 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-1001907149077
TypeChannel
Username@MoreRubyOfSec
CreatedBetween 1 March 2023 and 28 December 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live19 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 19 August 2026
On Telegramt.me/MoreRubyOfSec

Growth

7375746 August 2026 — 75 subscribers9 August 2026 — 75 subscribers12 August 2026 — 73 subscribers6 August 202612 August 2026
3 measurements spanning 6 days, net -2. 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 73–75 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:1873-2
9 Aug 2026, 21:1775no change
6 Aug 2026, 12:3775first reading

Engagement

20 posts held, back to 28 December 2023 — 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 20 posts for this entry, the most recent from 28 December 2023. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.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 1 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 1reactions 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 28 December 2023 to 28 December 2023, 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

28 Dec 2023, 22:47 UTC525 viewsread 9 August 2026

e bem, assim vamos obter a sequencia de bits que ao converter em ascii, vai nos dar a nossa flag

28 Dec 2023, 22:45 UTC506 viewsread 9 August 2026

dps de usar nosso script, descobrimos que os argumentos (*var_c*) que precisamos passar pra funçao fcn.000013e9 sao (18,5,17,2,30,51,13,46,16,55,9,57,28,5,16,49,12,4,57,31,21,51,5,52,18,5,61,2,12,21,17,51,8,18,5,61) para atingir as posiçoes no vetor E como fazemos isso?? Sabendo que cada numero que retorna do loop for com *var_10* na funçao anterior sera somado a *var_c* dependendo dos valores 0 ou 1, vamos testar i…

28 Dec 2023, 22:39 UTC303 viewsread 9 August 2026

e BOOM (agr de vdd), vemos agr o algoritmo de permutação, onde basicamente temos um vetor (começando pelo rbp-0x190 ateh rbp-0x158) e como vemos no endereço 0x000014a1 o argumento eh usado como valor pra procurar no índice do vetor e colocar no terminal com puts Entao, basicamente o que precisamos pra gerar a string criptografa eh passar no argumento o valor equivalente a posiçao no vetor da letra na string *lag.enc…

28 Dec 2023, 22:37 UTC223 views1 reactionsread 9 August 2026

e ao voltar a funçao fcn.000014ba cada resultado eh armazenado na variavel *var_20*, dps passa *var_8* (basicamente aqui ele pegando a posiçao atual do arquivo e ta substraindo as iteraçoes) e tira o bit relativo a posiçao pra ser multiplicado pelo retorno da funçao anterior (*var_20*) e ser armazenado na *var_c*. E como no arquivo soh existem 0 e 1, logo cada retorno ou vai adicionar 0 (nada) ou vai adicionar algum…

👍1

28 Dec 2023, 22:33 UTC202 viewsread 9 August 2026

dentro do loop, usa o valor de *var_10* como argumento a uma chamada a fcn.000013ab Aqui temos mais uma funçao que eh basicamente um loop com o argumento inserido, neste loop o argumento eh uma potencia de 2, ou seja, podemos representar com um pequeno script em python var_8h = 2 #nao confundir com rbp-0x8 da funçao anterior, as duas estao em frames diferentes da stack for i in range(6): var_4 = var_8 ** 2 print(…

28 Dec 2023, 22:20 UTC179 viewsread 9 August 2026

e como podemos ver, o resultado gerado pela suposta flag eh diferente da flag cifrada que precisamos gerar, ainda assim os primeiros caracteres sao iguais, ou seja, podemos deduzir que a flag real possui HTB{ como primeiros 5 caracteres, o que nao eh nenhuma surpresa sabendo que esse eh o formato das flags usadas pelo HTB. Porem vamos seguir usando esta entrada em nossos testes a fim de analisar o comportamento e enc…

Showing the 12 most recent of 20 posts we hold for @MoreRubyOfSec. 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 — 1,209,991 of 1,602,868entries 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.

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.

Ruby Of Security
@rubyofsec · 1,0621 post

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

“RubyOfSec 2.0 (0x177)” (@MoreRubyOfSec), 73 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/MoreRubyOfSec.

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.