Yesterday I noticed that the blog posts I write in Hugo via Vim are uglified on Mastodon and Calckey. By uglified I mean that the neat and tidy key words that I use as tags are converted into hashtags on Mastodon and Calckey and this makes me both sad and angry. It makes me sad because hashtags are a way of spamming conversations, and of allowing people who are not invested to participate in conversations.
The second reason is that hashtags are ugly. It’s like wearing socks with sandals, it’s like wearing cycling clothes at the cinema. It’s a bad habit that needs to stop.
The History of the Hashtag
Originally Twitter was a web based, and SMS based platform. With SMS you can’t use HTML tags, so you need a symbol to differentiate between words and normal content.
For a long time Twitter was just text. With time people started to interact and so we said we need to use @ replies to clarify who we are speaking to. This was fantastic because it made answering much easier. We had to remember the username, type at username and then the message. Eventually this was made more efficient. We simply pressed the reply icon and that was that. Quick, efficient, and great for conversation.
The preceding paragraph is to show that I am not resistant to all change.
The Hashtag was different. The hashtag made it possible to spam conversations, and to pretend you were deeply engaged within a community when the opposite was true. People create content, but rather than engage with the community, and invest their time in creating human connections, they spammed hashtags in the hope of hitting something. Imagine a child throwing stones in a lake. At first one at a time, and then handfuls. That’s how hashtags are used.
The Metadata Discussion
Metadata for Web Resources
A Brief History of Metadata
Back in the 90s, I remember reading articles about SEO and about metadata in pages, and web etiquette. I can’t find the articles now but the idea was that if you create content, you add metadata in the appropriate metadata field in the head of the document. You do not add several lines of white text on a white background to game search engines. To some degree that’s what metadata is. It’s white text on a white background. Hashtags are spam.
But Hashtags are Visible
Yesterday someone argued that we need to use hashtags because they’re visible, and this argument is crap. I know, I could say flawed, but I prefer to use the word I chose.
One of the reasons that I love Hugo as a Static Website Generator is that I think of the keywords I want to add as tags within the Frontmatter of the documents I create, and they will automatically populate the article, as well as pages with lists of every article with that keyword. It’s clean, it’s efficient, and it’s effective. Scroll to the bottom of this page and you will see the visually appealing use of tags, rather than the scruffy use of hashtags.
Hyperlinked Words To Replace Hashtags
What differentiated the Hypertext Markup Language, from other languages is the hyperlink. The hyperlink allows us to say “This word, in that context links to these documents”. The very idea of hypertext is that you can give behaviour to a key word or phrase, and link it to something else.
The way hashtags are used today, they are being used as hyperlinks, or threads, to connect content together. Hashtags are used as metadata and since 1976 or so conventions have existed to describe how to most effectively use that metadata. By using hashtags we are ignoring the beauty of hypertext but we’re also forgetting rules that were common sense until 2007 when the hashtag was suggested for Twitter, and then recycled on other social media websites.
The Trigger for this Post
What triggered me to write this blog post is looking at the articles I am sharing from Hugo to WordPress, and from WordPress to the Fediverse. The neat and tidy posts that I write with tags in the write place, are uglified by Mastodon and Calckey. It makes me appear sloppy and amateurish, but it also makes Mastodon and calckey look bad.
What I want
What I want to see, and what I expect, is for tags, that are created as tags, for example from Wordpress, Hugo and other sources, to be kept as metadata rather than spam data. I want tags and categories to be shown as tags and categories, rather than the mess of hashtags.
I was so horrified when I saw the hashtag mess at the bottom of my WordPress to Fediverse posts, that I considered dumping the fediverse entirely.
Visible, By Being Active
Someone on techhub social asked “but how will you be visible?” if you don’t use hashtags. The answer is simple. By tooting on Mastodon, by posting notes on Calckey, by answering toots by others, by devoting more than 30 seconds to the social network. We’re not fighting against an algorithm here, we’re conversing with a community. Hashtags don’t build community, the dilute it, by making people with no dedication more visible than people who see social media as a lifestyle.
The Bard Answer
Yesterday I gained access to Google bard so I asked bard
What regex would I use to convert hashtags to keywords in ruby on rails?. I could create my own calckey or mastodon instance, where, instead of seeing hashtags, we see hyperlinked words that guide us towards other posts with the same keyword. If I can’t influence the culture, away from a bad habit, then I can create an instance where that bad habit is invisible to me.
And Finally
I am not arguing against the use of metadata. I am not arguing against keywording. I am not arguing against threading. I am arguing against having metadata that should be in a dedicated field, to be displayed clearly. I use keywords for every blog post I write. I like keywording and I like cataloguing content. I am a media asset manager after all. I am a video after all. I have a passion for documentary.
My argument is not with organising information. My argument is with the sloppy, amateurish use of hashtags, when we have better tools available. 33 percent of the web uses WordPress, and WordPress uses tags and categories succinctly.
Like this:
Like Loading...
@admin-richard That is true if you build your site yourself. You could use services like Netlify, Github Pages or one of the many others to simplify the process. You need to have everything in a repository that can be accessed by those services. But once something is pushed to the repository, like your new blog, the service only pulls the difference, your new blog page, and builds it with Hugo automatically.It saves a lot of time and can be free as well.