Uncaught TypeError: The specifier “semfont/analyze” was a bare specifier, but was not remapped to anything. Relative module specifiers must start with “./”, “../” or “/”.
Seems to require Chrome? In Firefox it's just a text box, nothing happens. Was confused at first about what it was supposed to do, the rest of the page made it clear it was supposed to mess about with whatever text you write.
Trying it in Chrome and seeing the results I'm not sure that it is really that helpful. Has undertones of elementary school grammar lessons highlighting words in sentences.
The idea is amazing, and… how to say it?; The results are horrible to read in the same way as AI writing when AI writing is bad.†
And I mean this in the best possible way. It's really interesting.
There's this feeling of an intrusive forcing of something. A feeling that things don't… breathe? Feels like one already sifts out this sort of semantic weight when reading and to me the highlighting adds strange janky emotional-processing noise to the text; Uncomfortable and somewhat… dissonant?
It's really, really interesting. I hate how disparaging to the project this comes out!! my apologies for that! I LOVE the project and what it reveals about text comprehension and perception of saliency and rhythm in written text!
Cool, but I hope it doesn't catch on. Otherwise I can already hear managers complaining to people that they have too many red words and not enough green words in their emails/Slack messages/whatever...
This is brilliant and would likely be the most helpful for notes my agent takes for me or my own recorded transcripts. Especially being able to tweak it. I think where I would not want this is when it's done on my writing that's public facing in case it imbues unintentional meaning. But for my own notes, it's a small cost
This is a really neat idea. I'm not sure it's actually useful, but it's definitely neat.
And it made me think of the new kid in town: Jev. I wonder if Jev can do this well and quickly? Not that I'm willing to pay the tokens even to find out, but it's another neat thought.
Not using an LLM, but rather just a plain set of heuristics which can run formatting quickly enough to render while the text is being streamed or edited. The aim is to try to see if I can make text more readable as it's being streamed in.
Nifty idea, but the premise seems flawed. This won't help people read, it will help people avoid reading by focusing on which words to skim. It also seems like it would have a problem detecting sarcasm.
Trying it in Chrome and seeing the results I'm not sure that it is really that helpful. Has undertones of elementary school grammar lessons highlighting words in sentences.
like
https://github.com/RoelN/SansBullshitSans https://typographica.org/typeface-reviews/chartwell/ https://github.com/trishume/numderline
which can be taken rather far
https://www.coderelay.io/fontemon.html
And I mean this in the best possible way. It's really interesting.
There's this feeling of an intrusive forcing of something. A feeling that things don't… breathe? Feels like one already sifts out this sort of semantic weight when reading and to me the highlighting adds strange janky emotional-processing noise to the text; Uncomfortable and somewhat… dissonant?
It's really, really interesting. I hate how disparaging to the project this comes out!! my apologies for that! I LOVE the project and what it reveals about text comprehension and perception of saliency and rhythm in written text!
(† footnote: feels like this to me)
And it made me think of the new kid in town: Jev. I wonder if Jev can do this well and quickly? Not that I'm willing to pay the tokens even to find out, but it's another neat thought.