Live data from Hacker News

Viewing profile — mark4o

mark4o

HN member
Joined
Fri, Jul 31, 2015, 5:57 AM UTC
HN karma
39
Public activity
12 items

About mark4o

No profile information was provided.

Recent public activity

  1. comment
    Comment #26754155

    On macOS my experience with Zoom in the browser is that the gallery mode works in Chrome, however in Chrome it has problems with the camera (it reports that the camera is in use, o…

  2. comment
    Comment #26719722

    It won't even work on Windows, macOS, or iOS.

  3. comment
    Comment #14133457

    I suspect that the reason for switching from ### to XXX is that grep ### requires quoting in the shell.

  4. comment
    Comment #14068033

    In https://support.apple.com/en-us/HT207617 Apple admits that this may lead to arbitrary code execution.

  5. comment
    Comment #13924492

    In Unix v1 (1971) it actually did not even track the year. The time system call was documented as "get time of year", and returned "the time since 00:00:00, Jan. 1, 1971, measured …

  6. comment
    Comment #13919921

    POSIX does not require EOF to be returned from a blocking read() if the same file descriptor is passed to close() in another thread. Even if it appears to work on some particular O…

  7. comment
    Comment #12641592

    The bug is architecture independent, although a particular exploit may work only on a specific architecture.

  8. comment
    Comment #10907713

    Existing image formats support color profiles, which allow use of colors beyond sRGB.

  9. comment
    Comment #10907036

    If you're going to go with 16 bits per component, please at least increase the color gamut. sRGB is fine if you can only dedicate 8 bits per component, but with 16 bits per compone…

  10. comment
    Comment #10605598

    Monty wrote up a detailed response to this in 2010: http://people.xiph.org/~xiphmont/lj-pseudocut/o-response-1.h...

  11. comment
    Comment #9989654

    An FFmpeg developer has already volunteered to continue the libav merges: http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2015-August/1...

  12. comment
    Comment #9989395

    The message on the FFmpeg site http://ffmpeg.org/index.html#message sounds hopeful for a reconciliation of the forks.