Live data from Hacker News

Viewing profile — georgemandis

georgemandis

HN member
Joined
Wed, Oct 15, 2008, 9:05 AM UTC
HN karma
429
Public activity
28 items

About georgemandis

https://george.mand.is

Recent public activity

  1. comment
    Comment #48162107

    I'm realizing `encodeURIComponent` is actually part of the ECMA spec! I thought it was something provided by the browser like `window` or `document`. I withdraw my "the language ha…

  2. comment
    Comment #48161900

    >I do not agree that slice() should operate on extended grapheme clusters. Don’t lump the grapheme cluster/scalar value split in with the sins of UTF-16 and its unreliable code poi…

  3. comment
    Comment #48161200

    You are reminding me we also circled an issue at one point where a backend system in Python needed to agree on the same character count length of a piece of content was the client …

  4. comment
    Comment #48161136

    The language handled it fine. It will generally just show replacement characters (�) for combos that don't map to anything. It was really `encodeURIComponent` that didn't handle it…

  5. comment
    Comment #48160976

    My recollection (that I didn't add to the story): I don't think Intl.Segmenter had great browser support then (2022). Even if it had it still wasn't a quick/obvious fix for our pro…

  6. comment
    Comment #48160794

    Just noticed this is getting some traffic! It's a little buried in the post, but I made an interactive tool for exploring surrogate pairs as part of this: - https://george.mand.is/…

  7. comment
    Comment #44388314

    Definitely in the same spirit! Clearly the next thing we need to test is removing all the vowels from words, or something like that :)

  8. comment
    Comment #44388301

    I had this same thought and won't pretend my fear was rational, haha. One thing that I thought was fairly clear in my write-up but feels a little lost in the comments: I didn't jus…

  9. comment
    Comment #44384158

    I kind of want to take a more proper poke at this but focus more one summarization accuracy over word-for-word accuracy, though I see the value in both. I'm actually curious, if I …

  10. comment
    Comment #44380436

    I watched your talk. There are so many more interesting ideas in there that resonated with me that the summary (unsurprisingly) skipped over. I'm glad I watched it! LLMs as the ope…

  11. comment
    Comment #44379806

    Hahaha. Okay, okay... I will watch it now ;) (Thanks for your good sense of humor)

  12. comment
    Comment #44379183

    Interesting! At $0.02 to $0.04 an hour I don't suspect you've been hunting for optimizations, but I wonder if this "speed up the audio" trick would save you even more. > We do this…

  13. comment
    Comment #44379143

    Yeah, I'd like to do a more formal analysis of the outputs if I can carve out the time. I don't think a simple diff is the way to go, at least for what I'm interested in. What I ca…

  14. comment
    Comment #44378604

    Should be fixed now. Thank you!

  15. comment
    Comment #44378560

    For what it's worth, I completely agree with you, for all the reasons you're saying. With talks in particular I think it's seldom about the raw content and ideas presented and more…

  16. comment
    Comment #44378492

    Oooh fun! I had a feeling there was more ffmpeg wizardry I could be leaning into here. I'll have to try this later—thanks for the idea!

  17. comment
    Comment #44376990

    I was trying to summarize a 40-minute talk with OpenAI’s transcription API, but it was too long. So I sped it up with ffmpeg to fit within the 25-minute cap. It worked quite well (…

  18. story
  19. story
  20. story
  21. comment
  22. story
  23. story
  24. story
  25. comment