Mastodon will never be superior to other social media platforms if it doesn't adopt #PascalCase when suggesting hashtags. Defaulting to all lower case does nothing to help me understand the difference between #therapists and #therapists.
I have superior vision to many my age, but if using #PascalCase was the default, even I wouldn't have unnecessary misunderstandings. It must be quite challenging for people who rely on screen readers.
You know what would be great on Fediverse? If we could get an app that automatically makes known hashtags formatted in #SentenceCase or #PascalCase for easier viewing.
Now, I would develop that if I had a shred of knowledge beyond Hello World.
Pour rendre plus lisibles les hashtags de tes pouets, tu peux mettre des capitales à la première lettre des mots. C'est même nécessaire pour être intelligible par les lecteurs d'écrans.
Pour te la péter avec tes copaines qui sont dans la tech, sache que ça s'appelle #PascalCase ou #camelCase selon que le premier mot a une majuscule ou pas.
Capitalization affects how people read hashtags or how people hear them on screen readers. Use #camelCase or #PascalCase in hashtags instead of lowercase. You could have #DoctorWhoRewatch ("Doctor Who Rewatch") or #doctorwhorewatch ("doctor whore watch.")
If you have a hashtag with multiple words, write the hashtag in #PascalCase or #camelCase to help users of screen readers. That helps the screen reader to read out the words out individually, rather than trying to read them in one long word.
If you're using hashtags with more than one word, use #PascalCase to make them more easily readable for people and assistive technologies. It could be the difference between #analbumcover and #AnAlbumCover 😏
Here we got a class, in our regular #odata controller functions it produces #camelCase like we tell it to in our settings. However, in our non-base controller function it produces #PascalCase ... because, duck us?
Only on the expanded parts which are handled a little bit differently for efficiency, hense the need for the non-base controller function with odata.
@jab in both Newtonsoft.json and System.Text.Json, there is a way to control this behavior via "options" or custom converters. If it's part of your framework it might be obscured, but I would look for ways to adjust json serialization settings.
@TimPurdum but we did. I’m not sure if it’s because we are also using asp.versioning on top of it all. Which we probably shouldn’t have done to be completely honest, because so far we only have one version and it’s looking like we might never expose this outside our own frontend.
We’ve handled it by parsing the JSON on the consumption side. Not in our client in-house package for OData in Typescript but directly where it is consumed. That’ll have to do for now.
@SamiMaatta Mastodon's very own web interface makes this terrible to do especially on mobile devices.
On my desktop, sure, and I try; but sometimes, on mobile, I give up. It'll autowrong it to lowercase, add another space after it, there's not always a good way to abort that "help". 😕
One of the finer points of making your hashtags accessible for people who use screen readers, beyond using #camelCase or #PascalCase:
If you're using an acronym as a hashtag, don't lowercase any of the letters the way you might if it was title case.
Why? A lowercase letter following an uppercase letter is treated as a word, so title casing your acronym will muddle your meaning for those reliant on screen readers.