What's the use case?
Spellfucker
41–50 of 146 posts
Re: Spellfucker
#42Interesting idea though I don't agree with his statement: > The goal of the project is to make text hard to read for computers yet fairly easy to read for humans I found it impossibly difficult to read and I'm an native English speaker. I'd wager people who studied English as a second language might find it harder.
Re: Spellfucker
#43"The goal of the project is to make text hard to read for computers yet fairly easy to read for humans" At first look it doesn't pass the search engine test. https://duckduckgo.com/?q=I%27ve+bien+aloune+whyth+jou+eensi...
Good test! No this is one way: you know the obfuscated. What if you want to use it in the opposite direction? Let's call it the CIA/NSA direction, where you know what unobfuscated phrase you want to find, but not how someone may have obfuscated it. This is arguably much harder, especially if you do not store some sort of representation of the content "as sounds/phonemes".
Re: Spellfucker
#44Interesting idea though I don't agree with his statement: > The goal of the project is to make text hard to read for computers yet fairly easy to read for humans I found it impossibly difficult to read and I'm an native English speaker. I'd wager people who studied English as a second language might find it harder.
Lat kan nu'gruk da blah kos lat ar ash dafft pyn.
Re: Spellfucker
#45Ju kud tejk ej lengvich from ej diferent lengvich femili tu erajv et samfink similr. For furdr obfaskejshn ju kud juz diferent transliterejshn. Slavik pipl shud fajnd dis kvajt ridebl.
Re: Spellfucker
#46Ju kud tejk ej lengvich from ej diferent lengvich femili tu erajv et samfink similr. For furdr obfaskejshn ju kud juz diferent transliterejshn. Slavik pipl shud fajnd dis kvajt ridebl.
Æss a nårvidsjæn itt vassent tu hard tu riid jur vraiting laik dis. Aj vånder håo diffikult itt iss får a slav tu ønderstænd nårvinglisj.... Edit: and now I feel like Petter Solberg. [1] [1] https://youtu.be/Kaeh8FRPANs?t=4s
Re: Spellfucker
#47Ju kud tejk ej lengvich from ej diferent lengvich femili tu erajv et samfink similr. For furdr obfaskejshn ju kud juz diferent transliterejshn. Slavik pipl shud fajnd dis kvajt ridebl.
Akszualli dis is en obsfuskejszon juzing an akszual slawik lenguydz (uidaut juzing speszal slawik karakters but that // łud potenszalli bi iwen more obfuskejted). Ol klir?
Re: Spellfucker
#48Earlier quoted context omitted.
Seconded. Definitely unreadable. For anyone who didn't click through, a line from their self-chosen sample: >'kause jou gnaw jusd wuaed thoe sai
Italian here with a quasi-native command of the English language. It's very hard to read. My mind tends to parse the words as if they were to be read literally. E.g.: "I soumetymese scie jou pes outcyde mi dour" In my mind, "soumetymese" reads as "s-how-meh-teemesseh". "Scie" in Italian means trails. That automatically reads as "she-eh" (not "see"), as it's supposed to be pronounced in Italian. "Jou" reminds me of th…
Yes and "pes" surely doesn't remind me of "pass" but something entirely different and quite probably offending.
Re: Spellfucker
#49Re: Spellfucker
#50Earlier quoted context omitted.
Good test! No this is one way: you know the obfuscated. What if you want to use it in the opposite direction? Let's call it the CIA/NSA direction, where you know what unobfuscated phrase you want to find, but not how someone may have obfuscated it. This is arguably much harder, especially if you do not store some sort of representation of the content "as sounds/phonemes".
The point is that if you are the CIA, searching through a bunch of obfuscated text, just like you are already (hopefully) already compensating for basic spelling errors, it apparently would not be very difficult to expand the scope of that same mechanism (in the same way that Duck Duck Go has) to support searching through and understanding this obfuscated text.
Something I've had in the back of my mind for a while is the idea of swapping out a regular Lucene tokenisation & analysis for one that treats phonemes as tokens instead of (stemmed/analysed) words being the tokens... with a similar arrangement on the query side. I think it'd have interesting capabilities... this being one.