Winter Rant

… now that Twitter is dead.

Across the Fediverse: Tags with Spaces (and dashes)

I have been wondering: how would WordPress tags federate when they have spaces?

In a couple of recent WordPress posts I absentmindedly end up using such tags (i.e., with spaces): “Year in Review” and “user feedback”.

Here are the screenshots of two such tags (two different blog posts):

When federating over to Mastodon it seems that the spaces in the tags are dropped, and the first letter (character) of each word in capitalized. Here is “Year in Review” rendered as “#YearInReview … notice that “in” is converted to “In” when the spaces are dropped.

Similarly, here is “user feedback” converted to “#userFeedback”.

  • One fun note: “u” in “user” is left unchanged, so it seems the case of the first letter in the hashtag will go unchanged.
  • Another fun note: “software-engineering” on WP became “#softwareEngineering” on Mastodon. So it seems that this translation does not just apply to tags with spaces, but also dashes, and perhaps other special characters(?). (Will test soon! Update: testing done, and special character handling is happening.)

– vijay, putting together some Ikea furniture 🪑

7 responses to “Across the Fediverse: Tags with Spaces (and dashes)”

    1. @eatyourglory @rant.vpalepu.com thank you! I thought so too! An interesting way to bridge tagging differences across platforms.

      Like

  1. @rant.vpalepu.com Cool. Wonder if this will be how Threads "topic tags" which also have spaces will do Federation of those tags.

    Like

    1. @tchambers @rant.vpalepu.com hey Tim, vijay here! Yes I think this very well ought be a viable solution for the topic tags over at Threads. So there, “Tech Threads” would simply become #TechThreads

      Like

      1. Streams and Hubzilla support multi-word tags (just wrap the words in quotes) and have for over a decade.  I brought this up a couple of weeks ago and was promptly shat on by  the Mastodon community – who I guess prefer reading machine-friendly tags than human-friendly tags. We also use display names for mentions because (doh) they’re ‘display  names’ and they’re being displayed. For this I had to translate all incoming and outgoing mentions so we could see human-friendly names like Jake Wallaby and Mastodon folks could use @jake1285@example.com. We’ve got nomadic identity, and you could have radically different webfinger addresses on your different identity clones – so this is important to us. We’ll probably have to do the same thing for hashtags eventually – translate everything for consumption by Mastodon and Threads and show it for humans over here.

        Like

        1. @mikedev @rant.vpalepu.com hey Mike! this is vijay, nice to meet you 👋
          Wow! terrific context and back story here! Did not know that Streams and Hubzilla supported multi-word tags. Good to know 🙂
          Good context about display names as well. I am certainly feel some friction there WP identifiers are too damn long 🤣

          thanks again for the context here 🙏 I am picking up a lot from this conversation!

          Like

  2. […] I was writing my previous post on how tags with spaces (and dashes and underscores) were federating, I wanted to test this more systematically. So, this is that post. It is merely a test balloon to […]

    Like

Leave a comment