#amaranthhdl
Live, measured metrics for the hashtag #amaranthhdl from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #amaranthhdl
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-30 01:59 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-30 01:59 UTCNo related tags with measured usage found for #amaranthhdl.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 01:59 UTCEverything below is measured over the latest 4 public posts (spanning ~12885 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 5.5
Top of the latest posts
Testing my first #amaranthHDL design with #TinyTapeout 02 from @matthewvenn #ASIC, this design is a Gray code counter, it seems to work although i have some rare glitches maybe "noise" in the output pins, (maybe I also missed to read someth
me & @mwk just shipped a new Intermediate Representation for #AmaranthHDL! Amaranth's new IR is designed around an industry-leading netlist format taking into account everything we know about RTL, enabling both analyses and interoperability
Got inspired yesterday and wrote a double data rate transmitter and receiver in #amaranthHDL Most interesting was to learn about clock domains to get a negative edge clock for the receiver part.
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/amaranthhdl