#retnet
Live, measured metrics for the hashtag #retnet from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #retnet
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-29 13:12 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-29 13:12 UTCNo related tags with measured usage found for #retnet.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 13:12 UTCEverything below is measured over the latest 3 public posts (spanning ~82 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Used together with
Top of the latest posts
Unexpected Discovery: Training a #RetNet model on the CPU isn't *nearly* as slow as I'd expected. Yes, it's slower than the GPU but probably by less than a factor of 10 - not 100's of times slower. Which means I can periodically move my mod
So it occurs to me that #RWKV or #RetNet can both offer an alternative RAG implementation with saved memory states having just read priming information to start with reading new prompts. With RWKV - there's no time oscillations. Wondering i
#GPT first clues me in to the existence of #RWKV and #RetNet and then when I ask for details on how each works proceeds to spit out perfectly viable #Pytorch implementations of each... Which *did* answer my questions beautifully... But it a
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/retnet