hhmx.de

· Föderation EN Fr 24.01.2025 20:43:17

@juliette from what I heard, is read correctly, but a is bad.

Föderation EN Fr 24.01.2025 20:47:39

@joachim @juliette Totally blind screen reader user here. You're correct: mixed case is better to separate words, where all lower case may result in something unintelligible without extra effort for the user. I think the benefits of this extend beyond screen reader users though; i.e. all lower case could be difficult even for some sighted users to interpret, though I can't cite evidence for that.

Föderation EN Fr 24.01.2025 20:52:45

@jcsteh @joachim thank you! I find capitalized hashtags easier to read but realized while posting something else that I sometimes get lazy typing when there are just two words. It made me wonder what the broader impact might be. I’ll be sure to capitalize from now on.

Föderation EN Fr 24.01.2025 20:53:03

@jcsteh @juliette as a sighted user I concur with your last sentence, I’ve seen lowercase hashtags that were quite confusing.

It makes me remember the domain name ExpertsExchange.com, which can very easily be read ExpertSexChange.com when written in lowercase

Föderation EN Fr 24.01.2025 20:56:18

@juliette @joachim Haha, yeah, I remember reading about a bunch of unfortunate domain names like that years ago and being very amused.

Föderation EN Fr 24.01.2025 21:15:46

@jcsteh @juliette @joachim

Video example (anchor link) showing how it announced on Twitter, which is the same here:
adrianroselli.com/2018/01/impr

Föderation EN Fr 24.01.2025 22:20:11

@jcsteh @juliette @joachim There's quite a few examples of all lowercase hashtags being misinterpreted. Eg. When Margaret Thatcher died and "Thatcher is dead" was trending, some people thought it meant that the singer Cher had died:

"Have you heard " versus "Have you heard "

(For those who can see it, I've used Pascal Case above for the benefit of screen readers but imagine it was the all lowercase instead).

Föderation EN Fr 24.01.2025 20:58:04

@jcsteh @joachim @juliette

Please DO capitalize the words within a hashtag.

camelCase and PascalCase are two very similar norms that allow words to be joined without hyphenation but distinguished by readers through capitalization of the first letters of words.

The difference is that Pascal Case requires the first letter of the first word to be capitalized but camel Case just insists on the following words. The two terms are often referred to without distinction here though.

Be aware that Mastodon autocomplete will offer up the first version created for a hashtag. So, it’s important to be careful to make sure a hashtag that you type isn’t autocompleted to a version without capitals.

Föderation EN Fr 24.01.2025 23:21:09

@AlsoPaisleyCat @jcsteh @joachim @juliette
The current is an obstacle to using . It's a tool for in that.

And in some situations it is a obstacle to typing in the desired text even.

Föderation EN Fr 24.01.2025 23:38:38

@skua

Yes, it’s an issue. We’ve asked for the menu of hashtags that pops up be updated to show the CamelCase alternatives in the listing.

This seems to be happening now. Once a CamelCase version of the hashtag is created, it will be listed. But the original version with no capitalization will still be listed first.

@FediTips
@jcsteh @joachim @juliette

Föderation EN Fr 24.01.2025 23:45:12

@AlsoPaisleyCat @skua @jcsteh @joachim @juliette

If you type a CamelCase version of a hashtag in full, it will preserve the CamelCase capitalisation, even if the suggestion isn't CamelCase.

It will only ignore the CamelCase if you don't type the hashtag in full, and pick a suggestion instead.

The auto-suggestions are based on what was first typed on that server. It's difficult to have suggestions automated as CamelCase because the same string can split many ways ( and ).