Web developer, lover of my wife, cats, music and CrossFit. Trying to be better than I was yesterday.

Getting Started with Twitter Spaces

This one will be members-only because it's a huge rant with toxic workplaces, and it's very personal. No company names or people's names will be mentioned, but I'd rather keep this one on the down-low, and I'm hopeful others can learn from this experience.

This post was originally posted on my newsletter โ€“ https://www.getrevue.co/profile/MichaelBrooks


CrossFit Open 2021 โ€“ I will not be competing this year

Hello March, Goodbye February 2021

Why You Should Have a Post-COVID Wishlist

WordPress has partnered with Anchor

Celebrating pancake day the only way I know how

Moving my email newsletter from Substack to Revue

Born to run (things) and How to Be Great

Hello, fellow Coil community. I usually post links straight from my blog posts. However, I created a blog post with emojis in the title which was also placed in the URL of said post.

Did you know emojis can be used in URLs?

I really love this fact. However, it does have it's issues. For instance, some websites can't properly decode emojis since they use UTF8MB4 encoding, and not every website has their database set up properly for this. It's mainly old websites that continue to have this issue and new websites less so.

However, Coil doesn't seem to like them when I'm linking a post. This is the error I am currently seeing...

Hopefully, you can see in that image that the link shows โ€œ%f0%9f%91%80โ€ and not ๐Ÿ‘€. This is because it's the decoded text of that emoji. This usually happens when you copy and paste an emoji from your desktop PC. If I visit that URL, then my blog is clever enough to redirect to the correct post. However, I think that the redirect is partially to blame. A redirect won't carry the โ€œmonetizationโ€ meta tag which is used to monetise blog posts.

My next thought was to delete said text and replace it with the proper encoded emoji.

Curious... As you can see from the above screenshot, when I change it to the correct emoji, I still get the same error. This is me fairly stumped since no redirect should happen, and it should pick up the tag. I have viewed the source on the said blog post, and it is definitely there.

Is there anyone in the Coil team who could look into this? If it's something that can't be fixed, then no worries. I can create a written post here and link to the original. ๐Ÿ˜Š

For anyone that's interested in the blog post I'm talking about then you can take a look here. Have a good weekend all.