#textverarbeitung
Live, measured metrics for the hashtag #textverarbeitung from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #textverarbeitung
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.social (Mastodon public tags API) · fetched 2026-10-10 00:51 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-10 00:51 UTCNo related tags with measured usage found for #textverarbeitung.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-10 00:51 UTCEverything below is measured over the latest 40 public posts (spanning ~25645 hours).
Posting hours (UTC) — busiest: 08:00
Languages: German (32) · English (2)
Avg boosts / post: 3.1
Top of the latest posts
LibreOffice 25 - durchdachte Schwärzungsfunktion mit Extras Um sensible Daten in Dokumenten zu schützen, greift man oft zu den bekannten "schwarzen Balken". Aber, wie in diesen Tagen die Epstein-Files zeigen, kann der Text trotzdem lesbar b
Collabora Office für den Desktop Jetzt gibt es die Office-Suite für den Desktop. Kann diese Anwendung die Lücke im Mittelfeld der Office-Anwendungen schliessen? Dieser Kurztest verrät es. #Office #Collabora #Desktop #Textverarbeitung #Tabel
Trolle, Kobolde und Gnome: Hammer - Textverarbeitung für phantasievolle Geschichten Hammer ist eine (Markdown-)Textverarbeitung für umfangreiche Texte. Die Besonderheit: Es kann ein eigenes Nachschlagewerk gestaltet werden, sodass man den Ü
#textverarbeitung across platforms
every network with a public tag surfaceFollow #textverarbeitung 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/textverarbeitung