@acdha@webology Ivory isn't autocompleting anything. It is just getting back what Mastodon is returning as the most popular result. If you type in the hashtag yourself with your preferred casing, we intentionally show you your hashtag history before Mastodon's results so your proper hashtag casing shows up first.
@ivory@webology is there a server setting which could affect that? It sometimes works but doesn’t enough to be noticeable and something like a size limit or time window might explain that.
@ivory a little testing narrowed it down to two things:
the list of previously-used values is per account so when I started to enter a hashtag I normally use on a different account it didn’t get the capitalized form unless I switched accounts first.
The iOS sharing extension doesn’t appear to use it even if I switch accounts first.
@acdha Ah yea this is account specific, unfortunately. Also, if you use specific hashtags all the time, we recommend adding them to your “Featured Hashtags" list. That will give them priority as well as make it easier for users to find those posts in your profile.
The iOS sharing extension is getting a big redesign in the next update, but there's no autocomplete in the share extension so not sure what's not working right there?
@webology I pretty much always do this when there's multiple words because I also find a multiwordalllowercasehashtag hard to read. I'm not sure whether I do this consistently for single word hashtags though. 🤔 I'll keep this in mind.
@treyhunner@webology There's no need to capitalise single-word hashtags. Screen readers will just read the single word, regardless of casing. The exception would be things you'd already capitalise anyway, like acronyms or the first word of a sentence.
Add comment