【誌調查|渠務署地盤致命工業意外 發展局:承辦商或致事故 已停止部分工程投標資格】 今年發生多宗工業意外,5月同日渠務署位於元朗及深水埗的地盤發生兩宗工業意外。在深水埗「欽州街污水系統改善工程」地盤,一名工人被吊重滑車及吊運車擊中頭部,重傷不治;元朗污水處理廠則有兩名工人受傷。 事發兩個月後,誌傳媒向勞工處、渠務署及發展局查詢調查進展。勞工處稱已向該地盤的承建商發出「暫時停工通知書」,事件仍在調查中,不便透露詳情;發展局則指出,承建商或導致事故,已於6月要求有關承建商及分判商進行獨立安全審核,並在期間即時暫停其工務工程道路及渠務類別的投標資格。 雖然政府相關部門一再強調會徹查事件,並停止承辦商部分類別的投標資格,工業傷亡權益會指出,政府一般不會公開調查報告,調查結果或不見天日。 翻查資料,欽州街致命工傷的承辦商金城營造,於2017年涉及一宗紅磡嚴重工業意外,時任特首林鄭月娥直接致電金城營造,並承諾徹查事件。最終法庭裁定…

Channel
HK.feature 誌
@HK_feature
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,550subscribers
-10 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001134938845 |
|---|---|
| Type | Channel |
| Username | @HK_feature |
| Created | 17 July 2019 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/HK_feature |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 12:03 | 1,550 | -1 |
| 20 Aug 2026, 16:03 | 1,551 | -1 |
| 18 Aug 2026, 02:42 | 1,552 | -1 |
| 14 Aug 2026, 22:35 | 1,553 | -3 |
| 12 Aug 2026, 00:16 | 1,556 | -2 |
| 9 Aug 2026, 06:11 | 1,558 | -2 |
| 6 Aug 2026, 07:34 | 1,560 | no change |
| 6 Aug 2026, 07:03 | 1,560 | first reading |
Engagement
21 posts held, back to 1 April 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 2 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 9.13%
- avg views ÷ 1,550 subscribers
- Avg views / post
- 142
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 6
- of 21 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 21 (1 April 2026 – 6 August 2026) |
| Views total | 849 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 18:06 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
【誌Podcast|深水埗關鍵字:中餅逆境奇葩、30蚊理髮、臨時布藝市場、長者的派飯時光】 散步途中,不時駐腳與街坊閒話家常,都可以成為一則社區新聞?雖說「新聞」的原則是以公眾利益為先,當我們落區做社區新聞,何謂「新聞」,往往由街坊決定。因為這個空間,街坊就是「公眾」的一份子,你們關心什麼,就是「新聞」。 左鄰右里,大家也想知道為何公公婆婆在酷熱天氣下風雨不改地輪候免費飯?為何深水埗理髮店不加價?又為何老店的「老餅」仍然叫街坊期待? 現在的新聞已少了一種「現場感」和真實聲音,那怕是街坊的一句話,收進錄音筆後報道出來,在今日網絡至上的年代,仍是十分珍貴。當新聞還原基本步,傳遞訊息是最基本的功能,也是做社區報道的本能。 Podcast:https://apple.co/457QX7c 採訪 / 社區公民報道班學員 旁白/ 主編關震海 【支持獨立報道 | 記錄香港 香港有誌】 $65(輕量電子會員) / $90(電子會員)…
【#散步學新聞|「臨時市場」億元變身展覽空間 每年加租三代布業存隱憂】 過去我們持續報道舊「棚仔」的布檔搬至通州街臨時市場,眼看布檔一個一個離開,剩下來的信昌疋頭仍然努力尋找去路。去年「信昌」赴東京 TOKYO BIG SIGHT 參展,今年與設計館DX合作,成功由布料供應商轉型至布藝品的生產及代工公司,第三代Yuki亦開拓健美內衣市場。 看似前路有曙光,Tammy表示搬到新的市場後,鋪位租金每年增幅高達8%至10%。今年每個檔位加租約167元,Tammy表示多個布檔合計約加租1,600元。 與此同時,通州街臨時街市即將展開工程,據立法會文件,第4號排檔及毗鄰空地將斥資億元改造為展覽、工作坊及社區聚會的空間。據悉,展覽區與布業無關。記者問Tammy會跟政府反映租金問題,Tammy感慨說:「我們像『十個救心的少年』,走了一個,之後又走一個,現在剩下來的聲音已不多,只能靠自己。」 全文:https://ly.hkfture.…
【性罪行法例改革|有關「權勢性侵」】 性別及兒童保護政策研究者梁欣怡(Chase)指出,「不同意列表」其中一項「濫用受信任或權威地位或受養關係而令受害人屈從參與性行為」,對於權勢性侵受害者及未成年人士的保護仍有不足。 她解釋,政府的建議有參考台灣「權勢性侵法」,為適用於所有年齡層人士而加上「屈從」一詞,但暫時未見政府有為這詞作出定義,「要在法庭上證明這是『屈從』,好像也有困難之處。」她舉台灣案例指,如上位者欺騙對方指是真心相愛,但在發生關係後拋棄對方,是不能被稱作權勢性侵。 從保護兒童的角度,Chase認為這條文的保障更是匱乏,「16至17歲之間的人,他們已到達性同意年齡,但他們未必能意識到他們處於一個權力關係的性剝削之中。」即使這些少年有意識,要離開處境也十分困難,「未滿18歲的人,不論是外出工作或租屋,對他們來說也不是那麼容易,沒有穩定收入,想脫離這些關係也有很多考量。」 全文:https://ly.hkfture.…
【#散步學新聞|深水埗仲有單剪$30 ?】 快剪連鎖店散落在車站和商場,包圍著這座城市。單剪$50,在百物騰貴的大環境下稱得上是基層恩物。記者沿著鴨寮街走到桂林街,發現鴨寮街新開的理髮店單髮$35,已平絕九龍,但仍有不少理髮店價格更低,多年來堅持$30不加價。 屹立於桂林街52號已有17年的映藝美容美髮,老闆王姑娘表示從開業至今,單剪價格一直是$30,洗剪也只是$40,每日最少有20位顧客光顧,才能勉強支付人工、租金及水電費」。十多年來,菜米油鹽和交通費用已不斷上漲,理髮店不加價有何因由?全文:https://ly.hkfture.com/vhDQb 採訪、攝影 / 社區公民報道班學員 @culturemediahk 文化及媒體教育基金 Culture & Media Education Foundation 【支持獨立報道 | 記錄香港 香港有誌】 $65(輕量電子會員) / $90(電子會員) / $135(紙本…
【#性罪行改革|倖存者言⋯⋯ 】 香港目前的性罪行法律條文是以1956年英國法例作為藍本,沿用至今已達70年。香港法律改革委員會於2006年4月獲委託全面檢討性罪行法例,並分別在20年間就各種性罪行發表過9份報各告書及諮詢文件。政府於7月7日宣布,就完善性罪行法例展開為期一個月公眾諮詢,諮詢期於本周三(8月5日)截止,目標在本屆政府任期完成立法。 關注組「We are X」成員Jessie認為,目前的性罪行法例雖有列明性行為必須受雙方同意,但「同意」的定義相對模糊,「沒有同意是否就代表同意?這留了一個讓辯方律師可以鑽入的漏洞。」而諮詢文件則有清晰定議「同意」一詞,「這樣能堵塞『沒有反應代表同意』這類型的漏洞。」 不過,單憑為「同意」作出定義及列出無法給予「同意」的情況,並不代表可以保護受害人。根據香港目前沿用的法律原則,如被告「真誠誤會對方同意」(誤信同意)發生性行為,則毋需合理辯解也可以成為抗辯理由,而這項法律原則未有在…
採訪 / 實習記者 謝沛桐、張曦晴【俄烏戰爭|國內看不見的盡頭 國外看不見的鬱悶困局 】 根據聯合國烏克蘭人權監測組織(UN HRMMU)指出,2026年6月戰爭至少釀成293名烏克蘭平民死亡,至少1990人受傷,這是自2022年4月以來平民傷亡人數最多的一次。 兩年前,本刊報道Thomas與烏克蘭女子Kateryna在港結婚的故事。其後,他們前往烏克蘭補辦結婚議式,順道與當地人舉辦藝術活動,期望在戰火中維持有限度的正常生活。 二人從戰場返回香港半年後,Thomas這位「烏克蘭女婿」分享了當地的所見所聞:「現在的氣氛所見的烏克蘭,已經不是剛開戰時的烏克蘭了。」4年戰爭不僅令烏克蘭失去多條寶貴生命,亦消磨國民意志,國內男性長年避兵疫躲在家,全國上下呈現疲態,內心鬱悶難以紓解。 全文:https://ly.hkfture.com/CdJmg 採訪 / 實習記者 謝沛桐、張曦晴 【支持獨立報道 | 記錄香港 香港有誌】 $…
【#香港職人|為鳥兒築家 兩代人對籠藝的堅持 】 雀鳥花園(又稱雀仔街)59號的「財記漆籠」是目前碩果僅存的的籠藝鋪。師傅陳樂財(財叔)正在在雀籠上仔細髹漆,先掃雕刻部分,再刷較平的部分。財叔凝神貫注先逆紋掃漆,再順紋掃漆,力度剛柔兼備,新徒弟Betty對師傅的髹漆功夫讚嘆不已。「財叔不但百毒不侵(生漆的漆酚會引起皮膚敏感),每一處也是均勻的。」 22歲的Betty是理工大學設計系的應屆畢業生,同時也是尚未拜師的徒弟。7月遇上極端天氣,財叔甚少在雨天動工。雨季陰晴不定,Betty特別留意師傅是否開工。一場滂沱大雨,無阻師徒繼續工作。在過去兩年間,Betty一邊向財叔學習籠藝,一邊撰寫Zine記錄這門工藝。作為籠藝徒弟,她更養了一隻灰燕,並為牠修理雀籠,她希望在25歲前親手製作一個廣籠,作為她學藝的里程碑。 全文:https://ly.hkfture.com/lpjAS 採訪 / 林碧欣 編輯 / 關震海 【支持獨立報道 …
【#視像火警系統|點解公屋得,居屋唔得?】 據立法會資料,房屋委員會自2020年3月起讓聽障居民經屋邨辦事處申請免費安裝該系統,截至2026年4月,已有84個公共屋邨及一個租置屋邨共150個單位完成安裝;房協亦在部分出租屋邨推行自願計劃,為有聽障住客的單位加裝室內視像警報並提供定期檢查及維修。公屋先行,是否代表私人屋苑跟隨安裝? 龍耳創辦人邵日贊表示,過去曾協助居於公屋、居屋及私樓的聽障人士評估和安裝視像火警系統,觀察到不同房屋類別的安排存在差異。邵日贊亦指出,公營房屋在流程及資助方面較為明確,申請人無需自行承擔工程費用,相關裝置的維修亦由機構負責。 全文:https://ly.hkfture.com/nIxnc 採訪 / 實習記者 謝沛桐、張曦晴
【又一宗 #奪命工業意外|意外現場相片 泥土頻色不一】 何文田自由道4號一個地盤於6月29日(周一)發生致命工業意外,當日早上9時,一名挖泥機操作員(機手)在操作挖掘機吊運一捆金屬喉管時,挖掘機突然翻側,在旁工作的40歲陳姓男工人被墮下喉管擊中,送院後證實不治。李小姐居於與自由道相鄰的太平道,她表示地盤每天施工時,都會將閘口打開,亦沒有放置任何警示。記者從讀者提供的相片可見,地盤內的砂石堆積成一個小斜坡,而泥土的顏色亦深淺不一。 工權會總幹事蕭倩文指,目前正等待勞工處調查意外原因,「估計有三個可能性,第一是斜坡;第二是意外前曾下雨,令泥土鬆散;第三是牽涉到是否因吊運造成力量不均而導致翻側。」全文:https://ly.hkfture.com/iRvTh 採訪 / 劉彥汶
https://hkfeature.com/hk-craftsman-statement 聲明全文
【Don’t Blur BRUCE LEE| 天橋美化工程?】 「哪裡是李小龍?」有街坊向本刊投訴塘尾道行人天橋被貼滿以武術動作和書法為主題的畫作,惟印刷質素參差,部分畫作甚至出現「起格」的情況 本刊調查發現,油尖旺民政處委託NGO「藝術有嘉」美化天橋。該機構以李小龍為題創作創作,邀請青年繪畫,並將部分作品張貼在橋柱以作美化之用。本刊向民政處查詢,民政處表示「藝術有嘉」以義務身分參與設計部分,並不涉印製工序;有關印刷的質素問題,處方稱:「留意到小部分畫作印製成海報貼紙後清晰度有改善空間」。全文:https://ly.hkfture.com/Ypymr 採訪 / 實習記者 謝沛桐、張曦晴
Showing the 12 most recent of 21 posts we hold for @HK_feature. 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 — 326,926 of 1,603,893entries 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@HK_feature named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“HK.feature 誌” (@HK_feature), 1,550 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/HK_feature.
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.