Telegram RegisterThe public register of Telegram
Telegram profile photo for SLpct

Channel

SLpct

@SLpct

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

1,192subscribers

-1 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001008813722
TypeChannel
Username@SLpct
CreatedBetween 1 September 2015 and 31 December 2015— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live24 August 2026
Measurements held6
Confirmed unchanged2 times, most recently 24 August 2026
On Telegramt.me/SLpct

Growth

1,1911,1941,192.55 August 2026 — 1,193 subscribers6 August 2026 — 1,193 subscribers9 August 2026 — 1,194 subscribers12 August 2026 — 1,192 subscribers18 August 2026 — 1,191 subscribers21 August 2026 — 1,192 subscribers1,1925 August 202621 August 2026
6 measurements spanning 15 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 1,191–1,194 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 08:541,192+1
18 Aug 2026, 10:131,191-1
12 Aug 2026, 13:141,192-2
9 Aug 2026, 12:381,194+1
6 Aug 2026, 08:491,193no change
5 Aug 2026, 22:321,193first reading

Engagement

20 posts held, back to 4 June 2026the 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 25 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

25 Jul 2026, 08:30 UTC≈440 viewsread 6 August 2026

Se state utilizzando versioni di SLpct precedenti alla 1.36.2 riceverete immancabilmente la terza PEC dei controlli automatici con Errore imprevisto nel deposito, sono necessarie verifiche da parte dell'ufficio ricevente. In tal caso dovete non solo aggiornare ma anche ricreare la busta. Si può utilizzare il deposito già fatto ma andrà ricreato l'Atto.enc https://youtu.be/LPEokli2BK4

21 Jul 2026, 06:39 UTC≈640 viewsread 6 August 2026

Configurazione Firefox con CNS https://youtu.be/tPrDwt-4n98?si=mpPjz0wV9JaFdR9O

18 Jul 2026, 08:26 UTC≈695 viewsread 6 August 2026

Interruzione dei servizi informatici del settore civile, del Portale dei Servizi Telematici e del Portale dei Depositi Penali dalle ore 17:00 alle ore 18:30 del 21.07.2026 https://pst.giustizia.it/PST/page/it/interruzione_dei_servizi_informatici_del_settore_civile_del_portale_dei_servizi_telematici_e_del_portale_dei_depositi_penali_dalle_ore_1700_alle_ore_1830_del_21072026?contentId=NWS5068&modelId=4

12 Jul 2026, 08:46 UTC≈867 viewsread 6 August 2026

AGGIORNAMENTO: FINE MANUTENZIONE ll sito www.slpct.it è momentaneamente irraggiungibile per manutenzione programmata. Sono assicurate tutte le funzionalità tranne il download. Verrà ripristinato in giornata. buona domenica

9 Jul 2026, 08:55 UTC≈929 viewsread 6 August 2026

RIEPILOGO DEGLI EVENTUALI PROBLEMI DI FIRMA 1) Infocert nuove (ellittiche) necessario SLpct aggiornato e i driver bit4 che trovate in fondo al post 2) Aruba in scadenza il 30 giugno rinnovate gratis: sarà possibile creare la busta solo utilizzando firma esterna o differita, nessun problema con SLpw 3) Certificato rinnovato che risulta scaduto: anche qui va installato il bit4 aggiornato ATTENZIONE: i depositi effettu

1 Jul 2026, 10:11 UTC≈956 viewsread 6 August 2026

Repetita iuvant: Firme decedute il 30 giugno. Su questa tipologia la firma non è più utilizzabile da ieri 30 giugno. Per chi aveva firme rilasciate da Visura e Namirial il problema non si pone, perché Vi hanno semplicemente costretti a prenderne una nuova. Aruba invece ha cercato di mettere una pezza, come si dice a Roma, quindi ha dato la possibilità di "trasformare" il certificato non più a norma con una sorta di f

30 Jun 2026, 06:11 UTC≈730 viewsread 6 August 2026

SLpct FR Embedded Temurin E' stata rilasciata la versione 64 bit di SLpct che ingloba Java Temurin e che non necessita di un'installazione separata di Java. Disponibile per Windows e macOS https://youtu.be/4xKHOLjAhuo

26 Jun 2026, 07:09 UTC≈920 viewsread 6 August 2026

Il supporto esteso di windows 10 terminerà ad ottobre 2027 e non 2026 come inizialmente affermato. E' necessario accedere con account Microsoft ed attivare gli aggiornamenti estesi. Se lo avete fatto in precedenza non serve fare altro. https://www.facebook.com/slpct/posts/pfbid02AmHDWRSVodA7HMekfSZtj5fGzceuhhgBeMHyeBFYPjewX3jUyp4QD4DyMiboMEVdl https://www.microsoft.com/it-it/windows/extended-security-updates

22 Jun 2026, 05:38 UTC≈934 viewsread 6 August 2026

Errore imprevisto nel deposito https://youtu.be/DiE5JF7bkKY

17 Jun 2026, 11:54 UTC≈983 viewsread 6 August 2026
Photo

Come detto chi ha versione di SLpct precedenti alla 1.36.2 deve necessariamente aggiornare. E' ora disponibile la versione SLpct FR Embedded Temurin che non necessita di installazione Java a parte e dovrebbe semplificare il compito. Disponibile per Windows e Mac. Non serve disinstallare la precedente né fare altre operazioni

17 Jun 2026, 09:18 UTC≈790 viewsread 6 August 2026

AGGIORNATE AGGIORNATE AGGIORNATE! La mia non è una certezza, ma solo una ragionevole ipotesi. In seguito al fermo di lunedì il Ministero ha deprecato i vecchi certificati con algoritmo non AES256. Dunque chi ha una versione di SLpct precedente alla 1.36.2 riceverà errore imprevisto o simile. Dunque chi ha versioni obsolete aggiorni al più presto! https://www.slpct.it/slpct-redattore-atti/download

Showing the 12 most recent of 20 posts we hold for @SLpct. 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 — 412,232 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.

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

“SLpct” (@SLpct), 1,192 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/SLpct.

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.