mark4o

3 ms·

1.
by mark4o 5y ago
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, or will hog the cpu and work at about 1 frame per second). O
2.
by mark4o 5y ago
It won't even work on Windows, macOS, or iOS.
3.
by mark4o 9y ago
I suspect that the reason for switching from ### to XXX is that grep ### requires quoting in the shell.
4.
by mark4o 9y ago
In https://support.apple.com/en-us/HT207617 Apple admits that this may lead to arbitrary code execution.
5.
by mark4o 10y ago
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 in sixtieths of a second" ( https:&#x2F
6.
by mark4o 10y ago
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 OS, consider the case where the reading thread may have calle
7.
by mark4o 10y ago
The bug is architecture independent, although a particular exploit may work only on a specific architecture.
8.
by mark4o 11y ago
Existing image formats support color profiles, which allow use of colors beyond sRGB.
9.
by mark4o 11y ago
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 component the extra depth is more useful as an increase in th
10.
by mark4o 11y ago
Monty wrote up a detailed response to this in 2010: http://people.xiph.org/~xiphmont/lj-pseudocut/o-response-1.h...
11.
by mark4o 11y ago
An FFmpeg developer has already volunteered to continue the libav merges: http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2015-August/1...
12.
by mark4o 11y ago
The message on the FFmpeg site http://ffmpeg.org/index.html#message sounds hopeful for a reconciliation of the forks.