Post AlifGUVu0zsctdYIe8 by nicd@social.ahlcode.fi
 (DIR) More posts by nicd@social.ahlcode.fi
 (DIR) Post #AliVqvDpByIoc9pTmq by susie@blob.cat
       2024-09-06T05:35:40.842384Z
       
       0 likes, 0 repeats
       
       @nicd @aliceif Akkoma and Pleroma "support" the MastoAPI language selector when writing posts. There is a dropdown box for languages. However no one tells me if it actually works in their end lol It is not supported in any way when browsing fedi on PleromaFE, so I cannot be sure if it even does anything. I just know the code is there and apparently the field gets send during federation.I keep forgetting to use it though since again it doesn't change anything on my end.
       
 (DIR) Post #AliWqJ1LK7mE5bGFjk by nicd@social.ahlcode.fi
       2024-09-06T05:43:07.921Z
       
       1 likes, 0 repeats
       
       @susie@blob.cat @aliceif@mkultra.x27.one Firefish actually has a pretty nifty feature, where it tries to detect the language you wrote in and suggests if you've chosen the wrong option. Sometimes it suggests something silly but it's saved me a couple of times.Okay, Sharkey does not have per post language setting yet. :( https://activitypub.software/TransFem-org/Sharkey/-/issues/253So Sharkey is out of the running.
       
 (DIR) Post #AliePZ1IWut1Wb01vU by susie@blob.cat
       2024-09-06T07:11:38.086577Z
       
       0 likes, 0 repeats
       
       @nicd @aliceif One choice of course is to forgo the feature and do the same thing with hashtags. So for example hashtag nicdsuomeksi and hashtag nicdenglish. Can then tell followers to filter one hashtag they don't want to show up.Personally I don't get why "features" like that can't just be silly things like a hashtag/other special command character like !english. Easy. No complicated coding issues with federation, since it is part of the message and can be parsed however the target software wants.Users can then choose which country codes/commands to show (whitelist) in their client/front-end.
       
 (DIR) Post #AlifGUVu0zsctdYIe8 by nicd@social.ahlcode.fi
       2024-09-06T07:13:44.338Z
       
       0 likes, 0 repeats
       
       @susie@blob.cat @aliceif@mkultra.x27.one This would have been a working idea if it had been adopted, but it's too late for that. Other software like Mastodon expect to find the language information and it affects things such as translations and the language that a screen reader uses to read a message. That's why I don't want to just hashtag it.I used to use separate accounts for Finnish and English before Firefish supported the language setting, but I don't want to go back to that, it was cumbersome.
       
 (DIR) Post #AlifGUrAjutTxbVHnc by susie@blob.cat
       2024-09-06T07:21:10.796319Z
       
       0 likes, 0 repeats
       
       @nicd @aliceif Yeah. At times like these I wish everything was just text files flying over the internet. Adding features to protocols and APIs forces all the client software to "do as told" instead of "free to do as they wish" by parsing the same text file differently. So for example those who use screen-readers can just use a "fully featured" client which supports parsing that tag/command/whatever. However the writer/sender can just use simple FTP to upload the text file or whatever without worrying about end users not able to get the features they need.I'm probably the only one who wishes technology would have went this way instead of fully featured server software and "simple" front-ends lol
       
 (DIR) Post #AljxRuO69HJyf6SJFo by tirifto@jam.xwx.moe
       2024-09-06T16:56:42.887369Z
       
       1 likes, 0 repeats
       
       @susie @aliceif @nicd That’s what I’ve been doing since before proper tags got support in Mastodon. #lang_en for English, #lang_eo for Esperanto, etc. I still recommend people do that, since not all Fedi software supports proper tagging yet, so for some people this is the only way to filter by language.(Admittedly multilingual support in Fedi is lacking in general and should have been less of an afterthought.)