Reminder to use #CamelCase on your multi-word hash tags, for #legibility and #accessibility.

Like the “eats shoots and leaves” lesson about the importance of comma placement, but for the digital age. https://mas.to/@markarayner/114591353734555100

@jcsteh Using #LowercaseOnly instead if #CamelCase on #Hashtags impedes #TextToSpeech systems!

@A11yAwareness Ot is called Camel Case and please everyone, do it, it makes a huge difference to readers

#CamelCase

@Sunnysouth ja, #CamelCase ist zu bevorzugen wenns zusammengesetzte Wörter sind damit Screenreader die separieren.

Acronyme natürlich groß aißer die sind kompositär.

Bspw.:

• ITsec, InfoSec, OpSec, ComSec
• LEV0518
• #ScreenreaderFriendlyHashtags

@IsabelB
@Natasha_Jay

Nice photos. :-)

I got a little choked up seeing the Irish passport. Hopefully some day there will be a united Ireland.

Also, #CamelCase is nice:
#TransAtSixty #TransVisibility

@tripplehelix @joel @MekahimeAkari

Not that Meta, but meta in the sense of the thing itself, or folded on itself.

In this sense, meta-evil (it was capitalized because my brain was in hashtag #CamelCase mode, apparently), because it's evil the way he uses evil. XD

Question aux personnes concernées et/ou expertes en accessibilité numérique :

Je me rappelle, il y a longtemps, que le camelCase (mettre une capitale à chaque nouveau mot) était bien mieux pour les hashtags. Cela facilitait la lecture, notamment avec les lecteurs d'écran.

Est-ce toujours le cas ?
Edit: Oui

(Je découvre d'ailleurs sur Wikipedia que j'utilise surtout le "PascalCase" puisque je mets aussi une capitale au 1er mot.)

#CamelCase #PascalCase #AccessibilitéNumérique #LecteurDÉcran

@angelastella

It's fine for code but also (a) harder to explain/teach, (b) harder to automate, (c) badly supported on Mastodon (incremental search usually smashes case).

I think Mastodon has gotten better at preserving #CamelCase in hashtags. #GoToSocial is working on it, it's still really bad right now (always flattening/tolower()-ing).

I can see being a bit harder to explain/teach, although I'm not sure what cases of automation you're referring to.

I guess my main thing (and perhaps it's a silly one) is that _ is harder to reach than just capitalizing (and not spacing out) the next word. XD

I have no issues with Pascal (Borland's implementations and docs were excellent), but I had to learn C immediately afterwards like everyone else.

I used Borland on the PC and Symantec/THINK on the Mac. Both absolutely lovely.
Symantec Pascal on the (emulated) mac was actually a stepping stone towards @neaoire@merveilles.town's development of #uxn, IIRC. They even developed a 3d game in Pascal on the Mac (heavily accelerated, of course)

Looking at my hashtag list, I noticed that #CincoDeMayo was trending when I made the list, except it was in lame, all lower case, like #cincodemayo

So, I initially read "code mayo," then "cin code mayo."

So, I'm imagining a brand of mayonnaise made for C++ coders.

See what happens when you don't #CamelCase? Nerfherders.

#cpp

@angelastella

Hey now, #CamelCaseIsLovely

I cut my teeth on Pascal, I'll never stop using #CamelCase. XD

@bdm Kannst du für die Hashtags bitte #CamelCase verwenden?
Ist besser lesbar, insbesondere für Menschen die auf Screenreader angewiesen sind. Dankeschön 😀

@h3mmy @rootsandcalluses is this the way to pedantry corner? Shall we head there together?

Camel case is the first letter of every word after the first capitalized. #camelCase. The first letter of every word, including the first is Pascal case: #PascalCase.

These are both terms of art in programming. Pascal case, in particular, comes from the Pascal programming language.

Title case is different in that minor words aren’t capitalized, and is used in literature (sort of, certainly not programming) for titles and headlines:

Netizens Discuss Capitalization in Pedantry Corner: Homo sapiens Mid-conversation Share

The above title confioms to the Chicago Manual of Style (whose title also conforms) by not capitalizing 4 of 11 words.

Now to make this useful: both camal case and Pascal case address the issue at hand; title case doesn’t, but the expression may be useful to communicate the idea of Pascal case to a general audience.

References:

https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/capitalization-conventions

https://en.wikipedia.org/wiki/Title_case

@rootsandcalluses My only problem with #camelCase is what to do with something like #BestCSSPractices; that’s where #kebab-case or #snake_case works better.

Mein innerer #CaptainObvious will was sagen:

Versucht's bei #Hashtags am Ende mal mit Space statt mit Tab.

Dann wird euer liebevoll in #CamelCase eingetippter Hashtag (vielleicht) nicht autokorrigiert.

(Fänd ich am Ende sogar logisch:

Tab = Gib mir Autokorrekt,
Space = Ich schreibe hier.)

Getestet freilich nur auf Trötdeck/Firefox/Windows und Tusky/Android und auch nur auf dieser Instanz, seufz.

@Andreas_Sturm @OskarImKeller @wurzelmann
Alles klar, also #camelCase wäre die optimale Schreibweise? :)

@Hippie Das klingt jetzt vielleicht zunächst etwas kleinlich, aber wenn auch der erste Buchstabe immer ein Großbuchstabe wäre, nennt man es #PascalCase (oder UpperCamelCase) bei #camelCase (eigentlich LowerCamelCase) hingegen ist der erste Buchstabe immer klein. Finde ich wichtig, wenn man einen "Styleguide" verabschieden würde, schon bei der Definition präzise zu sein. Sonst ist das Ergebnis nachher uneinheitlich.
@OskarImKeller @wurzelmann

@OskarImKeller @wurzelmann
Das wäre ein riesiger Hebel um #CamelCase durchzusetzen! Einfach die Vorschläge (fast) immer CamelCased haben. Bei mir scheiterts halt echt meistens daran leider...
Opt out statt opt in :)

@rootsandcalluses@norden.social

Das mit Screenreadern war mir nicht bewusst, ist aber logisch. Woher soll der sonst wissen, wo das nächste Wort anfängt 🤷

Da ich aber auch sonst die Lesbarkeit ohne #CamelCase mehr als schwierig finde, habe ich das schon immer so gemacht.

@_elena @dmoonfire

I want to say Mastodon has gotten better at this, but if you're writing a hashtag in #CamelCase and the prevalent usage of that hashtag isn't camelcased, then it will probably get overwritten by your client's "suggestion."

You just have to be extra vigilant about avoiding the bad autocorrect. :(

It's very annoying, especially when the camelcase could happen kind of automatically using a simple dictionary.