101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

518
active users

#camelcase

0 posts0 participants0 posts today

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 ?

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

Replied in thread

@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)

Replied in thread

@_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.

Replied in thread

@mastodonmigration what a great tip! And welcome, new friends.

A note: you'll get more boosts on images with alt text. Some of us don't boost when alt text is missing - to make life richer for people using screenreaders. It's also fun, to do visual descriptions!

If you don't, you may get nudges like #altText4me #altText4u … and luckily you can edit and add #alttext to images later.

(PS: using #camelCase in your tags is recommended, it also helps screenreader users)

In response to the #hashtag casing issue, I've written a script for #MastoAdmin's to try to convert as many of them as possible to #PascalCase automatically:
codeberg.org/austinhuang/masto
Feedbacks & contributors welcome! (I'm still considering whether I should incorporate recent tagged posts to counter the computerized results.)

Codeberg.orgmastodon-tag-case-correctorA Python script for Mastodon instance admins to convert the display names of hashtags to PascalCase

@weirdwriter

#Inclusion and #Programming

#snake_case,
#kebap-case,
#camelCase, and
#PascalCase

(1/n)

" I wish all apps made all hashtags pascal case! "
Thanks for sharing this introspective, Robert.
Me, too. In fact, it makes long hashtags more easily readable for "sighted people" as well. ;) It is quite a bit more work, alas, in particular, as my apps try suggesting (and auto-replacing) previously used #Hashtags with all small letters, which I then have to...

@MoiraEve @elan @jamesbritt