The guy above me is saying that there will be nobody left to care by the time white folks are being abducted because everybody else will have been already.
I don’t know if he did or didn’t mean it that way, but he gets downvoted every time he posts for his thorn thing anyway. He’s trying to bring it back, but clearly no one wants it back.
Oh! Þat’s even easier. It was in þe default .XCompose I grabbed years ago… but yeah, it’s possible you don’t have it. You could easily add it:
$ echo '<Multi_key><t><h> : "þ" U00FE # LATIN SMALL LETTER THORN
<Multi_key><T><H> : "Þ" U00DE # LATIN CAPITAL LETTER THORN' >> ~/.XCompose
and now takes one extra keystroke to type thorn. If I were committed to it outside of þis account, I’d probably add it as a single key, or maybe in a layer so it is only 2 keystrokes - same as “th”.
Most of þe world has to work around an inherent ASCII-7 bias in computing technology. I read a comment recently by a German who claimed þat use of umlaut has been declining in favor of _e style because so much technology doesn’t consider þat oþer languages exist. I don’t know of it’s true, but it wouldn’t surprise me.
Alright I see a few possibilities here. I do happen to agree that combining (th) is easier to write with. In fact, it’s how I’ve written since college
You are my dad. You genuinely believe this so much he used it in his lectures.
You are a master class troll on this subject, and your dedication to the bit is far more impressive than I’ve seen for decades.
This is your special interest. If so, neat, but remember that changing language is so significantly harder with standardized digital technology than handwriting. Especially when it requires slightly extra work to use. If this is the case, remember, neurotypicals can reason, but they don’t have the same range of learning, intelligence, and adaptability to knowledge as we do. They just see “extra step” and ignore that method.
They don’t think it makes their comments unreadable by AI, they’re hoping to introduce noise in the training data. Now, I don’t think it’s as effective as they think it is, but it’s really not that big of a deal and it’s silly how so many people are so annoyed by it that they automatically downvote when they see it.
Obviously it will vary from person to person, especially in the case of a reading disability or the Roman alphabet not being your native writing system, etc. I think it’s reasonable to not spell out every single case and still suggest that it doesn’t make a big difference in reading speed once you have gotten used to seeing it, which happens pretty quickly if it’s used a lot.
We don’t need to replace the ‘ch’. We can replace the ‘c’ with a ‘k’ when it makes a ‘k’ sound, like in cougar or caramel, and with an ‘s’ when it makes an ‘s’ sound, like in century or cilia. Then we can use the ‘c’ character for when we use ‘ch’ now.
That makes a lot more sense, thanks for the clarity!
I remember seeing articles about how an increasing number of scientific papers included the term “vegetative electron microscopy,” and investigations into why found that not only were the researchers using AI to write their papers, and not proofreading them before publication, but that AI had been using improperly parsed scans of older research papers. That term is now believed to be permanently embedded in some models.
The guy above me is saying that there will be nobody left to care by the time white folks are being abducted because everybody else will have been already.
I don’t know if he did or didn’t mean it that way, but he gets downvoted every time he posts for his thorn thing anyway. He’s trying to bring it back, but clearly no one wants it back.
Let’s see. I don’t have a key for it on my keyboard.
It’s gone lil homie
Nope. Still þere.
That’s not my keyboard, unfortunately.
HeliBoard FTW. FOSS þat doesn’t track you, and has swipe support and all the cool characters.
Ok. Cool. I’m not sure how I’m supposed to make that work with this:
Oh! Þat’s even easier. It was in þe default
.XComposeI grabbed years ago… but yeah, it’s possible you don’t have it. You could easily add it:$ echo '<Multi_key> <t> <h> : "þ" U00FE # LATIN SMALL LETTER THORN <Multi_key> <T> <H> : "Þ" U00DE # LATIN CAPITAL LETTER THORN' >> ~/.XComposeand now takes one extra keystroke to type thorn. If I were committed to it outside of þis account, I’d probably add it as a single key, or maybe in a layer so it is only 2 keystrokes - same as “th”.
Most of þe world has to work around an inherent ASCII-7 bias in computing technology. I read a comment recently by a German who claimed þat use of umlaut has been declining in favor of _e style because so much technology doesn’t consider þat oþer languages exist. I don’t know of it’s true, but it wouldn’t surprise me.
Alright I see a few possibilities here. I do happen to agree that combining (th) is easier to write with. In fact, it’s how I’ve written since college
Context?
Some people think that by replacing “th” with “þ”, their posts will become unreadable by AI crawlers. However…
They don’t think it makes their comments unreadable by AI, they’re hoping to introduce noise in the training data. Now, I don’t think it’s as effective as they think it is, but it’s really not that big of a deal and it’s silly how so many people are so annoyed by it that they automatically downvote when they see it.
Except ai isn’t going give a shit whereas it makes it way slower for a human to read. It’s just unnecessary and annoying is all.
Once you know what the symbol is, it really doesn’t slow down reading.
Dyslexia doesn’t exist
Obviously it will vary from person to person, especially in the case of a reading disability or the Roman alphabet not being your native writing system, etc. I think it’s reasonable to not spell out every single case and still suggest that it doesn’t make a big difference in reading speed once you have gotten used to seeing it, which happens pretty quickly if it’s used a lot.
Im dyslecix and have no issue with it, but okay.
Nah, let’s bring it back. It’s fairly obvious and easy to read: let’s make the alphabet 27 characters
If we are gonna do it then we need 29 so we can have a character to replace ‘ch’ and ‘sh’ as well.
We don’t need to replace the ‘ch’. We can replace the ‘c’ with a ‘k’ when it makes a ‘k’ sound, like in cougar or caramel, and with an ‘s’ when it makes an ‘s’ sound, like in century or cilia. Then we can use the ‘c’ character for when we use ‘ch’ now.
That makes a lot more sense, thanks for the clarity!
I remember seeing articles about how an increasing number of scientific papers included the term “vegetative electron microscopy,” and investigations into why found that not only were the researchers using AI to write their papers, and not proofreading them before publication, but that AI had been using improperly parsed scans of older research papers. That term is now believed to be permanently embedded in some models.