I'm writing this in English.
Do you, though? Your writing style was different in the past, so I am pretty sure that you now machine-translate, or perhaps use an LLM writing assistant.
To be honest, the non-slop version of you was much better.
Timeline
Post
Remote status
Replies
6
@hongminhee @silverpill Maybe consider writing posts in both languages, Korean and English. Multi-language posting on the protocol side is in its early infancy and basically does not exist, but you at least don't seem to have the arbitrary character limit on posts that a certain blue elephant has. It might not be a bad idea to take advantage of that. Even if the english part is slightly broken, there is still the possibility of defaulting to a translation.
Not sure how that would hold up in reality, but it seems like a reasonable option to me, even though translators in $current_year are getting worse instead of better in general. Google Translate is barely usable now.
Not sure how that would hold up in reality, but it seems like a reasonable option to me, even though translators in $current_year are getting worse instead of better in general. Google Translate is barely usable now.
@hongminhee @phnt @hollo The implementation of multi-language posting once proposed to Pleroma, I think by tusooa, rendered all language variants merged into single string in the "content" field
@mkljczk @hollo @hongminhee Ideally I think it should render based on the user's language and if it doesn't match, display the "main" language the post was written in, which of course is not possible because AS2 did not define the order, like usual. Another standardization like a FEP would need to be created.
On the same note, I have a hard time thinking how to make that look nice in Pleroma-FE, similar to translations which aren't implemented either I think. The status view isn't forgiving to new elements and both a button, or a language drop down look completely out of place when I tried.
On the same note, I have a hard time thinking how to make that look nice in Pleroma-FE, similar to translations which aren't implemented either I think. The status view isn't forgiving to new elements and both a button, or a language drop down look completely out of place when I tried.
@phnt @hollo @hongminhee My front-end implementation is as simple as this (it's compatible with tusooa's work. But yeah, that would be another icon (that won't be displayed for most posts though)
I also think it's beter for posts to have a main language.
I don’t interject this as an attack, but please realize that when you say “AI slop” you say “sloppy person who uses AI”.
@hongminhee very clearly is not such a person, so please don’t imply they are, even if they chose an assistant you disapprove of to help them communicate.
I am irritated by the term “AI slop” because it shifts the responsibility from the user to their tool, from the way they use the tool to something that’s inevitable.
@silverpill @hongminhee DeepL or some LLM translation assisants often use hyphens to replace commas or semicolons, so I usually use this feature to confirm if a text is machine-translate.