Toot by eshtoneshton (indieweb.social)

@theynege @Pawpower In the case of hashtags, camelcase does the work of indicating spaces between words, at least as far as text-to-speech is concerned. It still takes up extra cells on braille displays though. What happens with alternate letter capitalization is that in text-to-speech situations, capitalization of letters can effect the way they're spoken. The text-to-speech assumes that capital letters should be emphasized differently than lower-case letters, because the assumption is in acronyms letters should spoken out instead of pronounced. So this context gets ported to everywhere else, since text-to-speech dictionaries don't do specific contexts.

Toot by eshtoneshton (indieweb.social)

@theynege @Pawpower Speaking for myself, spelling out words using spaces is annoying , mostly because if I need to know the spelling of a word, in a document or on a webpage for instance, I can move by character. In social media contexts, it's mildly annoying and I'll skip past posts doing this rather than waste time asking people to please not do this.

Mixed case makes me want to throw things, mostly because there is zero way to make sense of it, and in social media contexts, if someone does it all the time, I'm liable to unfollow them or mute them for extended lengths of time just to avoid the noise. Because it's quite literally noise as far as text to speech is concerned, and doing either of these things, spelling with spaces, or spelling with mixed case, unnecessarily takes up cells on a braille display. And cells on a braille display are valuable real estate.

Hope this helps.