#WindowsPowerShell
Live, measured metrics for the hashtag #WindowsPowerShell from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #windowspowershell
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 · mastodon.online (Mastodon public tags API) · fetched 2026-10-29 15:00 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-29 15:00 UTCNo related tags with measured usage found for #windowspowershell.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-29 15:00 UTCEverything below is measured over the latest 23 public posts (spanning ~42012 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (16) · German (6) · Japanese (1)
Avg boosts / post: 0.5
Top of the latest posts
I've been using #Tabby (formerly #Terminus) as my main #Terminal app for a while, and I've customized it quite a bit, so I thought I'd share some of my favorite #TabbyTweaks. 1. A #PowerShell script that launches Tabby, waits for its #MainW
PowerShellの配列への+=は「大量追加には遅い」と一括りにせず、バージョンも確認したいところです。 同一PCで3万件を追加した実測では、Windows PowerShell 5.1の約13.4秒に対し、PowerShell 7.6.5は約280msでした。ただし同じ7.6.5でもListのAdd()は約2.59ms。 配列の作成・追加・削除・検索、foreachとの使い分けや、0件・1件でも配列として受け取る@()の使い方まで整理しています。 #PowerShell
UNC6671 calls your phone, fakes a passkey setup, then steals your M365 session while you watch. 9 detections, 30 IOCs. Full analysis + IOCs: https://intel.threadlinqs.com/threat/TL-2026-1962 #ThreatIntel #Pink #pythonrequests #WindowsPowerS
#windowspowershell across platforms
every network with a public tag surfaceFollow #windowspowershell 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.
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/windowspowershell