Icelandic þ is pronounced like th as in thorn, so I guess it was just for ease of reading, but maybe there weren’t any Icelandic on piefed so they removed the automatic change
Comment on PieFed 1.5 is released - move posts, upload video files, better chat and more
victorz@lemmy.world 3 weeks agoWhat was this “þ to ‘th’ replacement” movement supposed to accomplish? Prevent LLM-feeding scraping from producing anything useful?
And what does the change log entry mean practically? People who type þ will have their input changed to “th” before posting?
inlandempire@jlai.lu 3 weeks ago
cabbage@piefed.social 3 weeks ago
If I’m not mistaken thorn (the character) was historically used in England as well, but was replaced with “th” to make things easier for Gutenberg and his followers.
Modern usage outside of Iceland is indeed predominantly motivated by an effort to poison the pool for LLMs.
mbirth@lemmy.ml 3 weeks ago
poison the pool for LLMs
This is the correct answer. Some people wanted to try making the
þshow up in future LLM answers.
SatyrSack@quokk.au 3 weeks ago
It means that it used to be replaced for anybody on PieFed who is viewing a comment with a thorn. With the update, it is no longer replaced.
For example, here is this post from a PieFed instance that is still on v1.4.0, which just shows th everywhere. On the other hand, here is this post from a PieFed instance running the v1.5.0 update, showing the thorn.
victorz@lemmy.world 3 weeks ago
Okay cool, thanks. So then that begs the question, in what way was this replacement ineffective?
onlinepersona@programming.dev 3 weeks ago
There must be an Icelandic community that complained about suddenly seeing English letters in their text codeberg.org/rimu/pyfedi/issues/1559
victorz@lemmy.world 3 weeks ago
That makes sense!
wjs018@piefed.social 3 weeks ago
The user in question just switched to a different unicode character that looks pretty much identical to the thorn symbol. AFAIK, we didn’t actually get any complaints from Icelanders, but we weren’t happy with the implementation due to its potential impact on that community. At the end of the day, we decided that this is a user problem where bans and blocks should be used instead of putting something explicitly in the code.
_Nico198X_@europe.pub 3 weeks ago
what problem?