#hateoas
Live, measured metrics for the hashtag #hateoas from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hateoas
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 18:44 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 18:44 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 18:44 UTCEverything below is measured over the latest 40 public posts (spanning ~23831 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (35) · Russian (1) · Chinese (Taiwan) (1) · Swedish (1) · German (1)
Avg boosts / post: 1
Top of the latest posts
HTMX [1.9.7 has been released 🎉 htmx gives you access to AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML, using attributes, so you can build modern user interfaces with the simplicity and power of hypertext :pickl
Have been playing around with #HATEOAS Thinking it as document synchronization (i.e alpine-ajax) make it easier to maintain than html swapping (i.e htmx). And, I ended up having less endpoints. It's kinda inconvenience because it based on h
"The only reason that Google works is because the web is built on the hypermedia principle.” – Kris Brandow #rest #api #openweb #hypermedia #hateoas #podcast 🎥 https://youtu.be/2WMcZ7KYa34
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/hateoas