#보안

Live, measured metrics for the hashtag #보안 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #보안

This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.

$11,525.77/ year · 2-character #name
Claim #보안 — $11,525.77/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
24
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 24
0.1
Avg reactions / post
Mastodon · last 24
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-08-08 07:02 UTC
0
08-02
0
08-03
0
08-04
0
08-05
0
08-06
0
08-07
0
08-08

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · fosstodon.org (Mastodon public search API) · fetched 2026-08-08 07:02 UTC
#보안뉴스
0 uses · 0 accounts / 7d
#연합우주_계정_보안_테스트
0 uses · 0 accounts / 7d
#보안실사
0 uses · 0 accounts / 7d
#보안컨설팅
0 uses · 0 accounts / 7d
#보안패치
0 uses · 0 accounts / 7d
#보안사고
0 uses · 0 accounts / 7d
#보안모델
0 uses · 0 accounts / 7d
#보안AI
0 uses · 0 accounts / 7d

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-08 07:02 UTC

Everything below is measured over the latest 24 public posts (spanning ~29951 hours).

Posting hours (UTC) — busiest: 03:00

00:0012:0023:00

Languages: Korean (24)

Avg boosts / post: 1

Top of the latest posts

  • #Hollo 쓰시는 분들은 可能(가능)한 限(한) 빨리 0.6.12 버전으로 올리시기 바랍니다. DM이 公開(공개) 揭示物(게시물) 페이지에서 露出(노출)되는 深刻(심각)한 保安(보안) 脆弱點(취약점)이 패치되었습니다. https://hollo.social/@hollo/0199aaaf-7979-7da3-9509-73c9e487de05 #보안 #취약점

    洪 民憙 (Hong Minhee) :nonbinary:@[email protected]♥ 1↻ 22025-10-03 15:32 UTCView post →

  • 이와 관련하여, #Hollo 역시 #보안 업데이트가 이뤄졌습니다. 0.3.6 또는 0.4.4 버전으로 바로 업데이트하시기 바랍니다! https://hollo.social/@fedify/0194848b-3b9e-7da1-b631-c011db2f4c43

    Hollo :hollo:@[email protected]♥ 1↻ 12025-01-20 17:01 UTCView post →

  • 6월 27일(土)에 #GitHub Security Advisory로 #CVE ID를 요청했는데, 거의 2주가 지나도록 감감 무소식이네요. 문서에서는 통상 업무일 기준 3일 정도 걸린다고 되어 있는데요. 요즘 GitHub CNA 쪽 처리가 원래 이렇게 느린가요? 아니면 저만 이런가요? #보안 #정보보안 #오픈소스 #FOSS #GHSA RE: https://hollo.social/@hongminhee/019f44fb-db84-7d

    洪 民憙 (Hong Minhee)@[email protected]♥ 0↻ 02026-07-09 03:50 UTCView post →

#보안 across platforms

every network with a public tag surface

Follow #보안 straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/보안