#serialcommunications
Live, measured metrics for the hashtag #serialcommunications from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #serialcommunications
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 12:18 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 12:18 UTCNo related tags with measured usage found for #serialcommunications.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:18 UTCEverything below is measured over the latest 6 public posts (spanning ~49768 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 0
Top of the latest posts
Hi #hivemind, has anyone got the #Wyse WY-120 #serial #terminal to work correctly on #Linux with any #terminfo entries? Specifically, it has trouble with backspace/delete, arrow keys and general #curses page layout. #Halp? PS: I've seen @ve
@rl_dane It basically redraws entire lines at a time, and a single character change invalidates the entire line that it is on. #urwid #TUIs #SerialCommunications #Unix #ncurses
@rl_dane Youth of today, with your emulators! (-: I simply have an actual serial port that I can set to 1200 BPS, and log in on. From a quick perusal of its 'raw' driver's code, you probably do not want to know #urwid's drawing behaviour. #
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/serialcommunications