#sitberlin
Live, measured metrics for the hashtag #sitberlin from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sitberlin
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.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 08:48 UTC0 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-07-27 08:48 UTCNo related tags with measured usage found for #sitberlin.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:48 UTCEverything below is measured over the latest 3 public posts (spanning ~0.2 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.7
Used together with
Top of the latest posts
#sitberlin currently streaming on YouTube: https://www.youtube.com/watch?v=tewV0iir7eE Off to a good start with a talk on #infosec, bug bounties and responsible disclosure.
For a responsible disclosure program, #infosec researchers need: - A point of contact, - No legal consequences, - Financial reward Openness is important too, sharing discoveries after they've been fixed has value. Tim Philippp Schäfers @ #s
Legal restrictions against reverse engineering devices make security researchers afraid of disclosing vulnerabilities. Everyone ends up worse off. Sebastian Neef @ #sitberlin #infosec
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/sitberlin