mappu

29 ms·

361.
by mappu 4y ago
There are known patents on Opus held by Xiph.org, Broadcom and Microsoft, all made freely available. But as per https://opus-codec.org/license/ if you try patent litigation against anyone, your license to use any of th
362.
by mappu 4y ago
They're usually also in U-boot in ROM. The trees in the kernel override the platform's one because the kernel is newer and knows better. ACPI on x86 works the same way - it's in ROM but the OS doesn't necessarily use it
363.
by mappu 4y ago
Most ARM hardware is cellphones, raspberry pi and the Mac M1, which certainly aren't that type. But a lot of ARM hardware is that type. The keywords are SBSA / SBBR / SystemReady. If your hardware is SBBR compatible then Fedo
364.
by mappu 4y ago
It's possible that a single-purpose firmware is too few stages, and it's also possible that the current acpi->firmware->uefi->grub->initrd->linux is too many stages. UEFI does have many of the features of a full ope
365.
by mappu 4y ago
I left GAFYD just days prior to them relenting and let people stay on it. I regretted the decision for a while afterwards, but i've since realized i don't want this shutdown threat hanging over my head. Thanks for the 10+ years of
366.
by mappu 4y ago
Thanks for the long comment, there's a few insightful parts, and a few parts i wanted to reply to: > R2 is actually a CDN. So is S3. Yes, I'm aware, the vending companies also sell different products called CDNs. Nonetheless,
367.
by mappu 4y ago
A while back at $DAYJOB I tried to get a CI pipeline to bundle our docs as .chm, but the official tooling (hhc, with-or-without Sphinx as a frontend) is windows-only pre-unicode nonsense; the only Linux native chm compiler i found was Halib
368.
by mappu 4y ago
The "100+" number is too low for Genshin Impact - $100mn was the initial development cost for 1.0, but since then the game map has grown ~3x in size, the story ~3x longer, many live events etc. See https://www.pcgamesn.
369.
by mappu 4y ago
You see it a lot more often from the Microsoft world since MSVC only supported "C/C++" as a combined language, there was no separate C compiler.
370.
by mappu 4y ago
"ALSA" has two meanings - there is only one set of Linux kernel audio drivers, and they're all ALSA no matter what distro you use. I think you're talking about this meaning. The other meaning of "ALSA" is libas
371.
by mappu 4y ago
The `authbind` package can automate this by path, user, port and many other things. It comes from the Debian world (developed by Ian Jackson) so perhaps less well known for RPM users? https://en.wikipedia.org/wiki/Authb
372.
by mappu 4y ago
Sikuli works on Linux - http://sikulix.com/
373.
by mappu 4y ago
In Go you can assign this "method" to a func(v Vertex) float64 and it will run just fine: https://go.dev/play/p/NBS4Fc3r0w- It really is just syntax sugar,
374.
by mappu 4y ago
As well as Wine and DXVK there's also native Gallium Nine, which is `libd3dadapter9-mesa` in Debian.
375.
by mappu 4y ago
It's the modern-day version of United States v. Paramount Pictures, Inc. where movie studios were banned from vertically integrating with theatres. However I note on https://en.wikipedia.org/wiki/United_States_v.
376.
by mappu 4y ago
NQP is also a similar project from the Perl world, a subset of the language that's simpler to implement and has clearer edge-cases.
377.
by mappu 4y ago
Have you tried a Pop Socket? I can't say enough good things about them - for $2 they transform even the largest phones to being one-handable. It's miraculous. They make this conversation obsolete without the slightest exaggeration
378.
by mappu 4y ago
You may be interested in Laminar CI.
379.
by mappu 4y ago
I think it's about the route. For a `thumbnails/123/` endpoint, the parameters are specified in the route. You're encoding more information in the HTTP level, so encoding the error in the HTTP level as well is reasonable
380.
by mappu 4y ago
HTTP is just a transport for your RPC. It's an implementation detail. At the HTTP layer, the transport was successful, so a 200 is appropriate. A 404 would indicate 'not found' at the transport layer e.g. a bad proxy configur
381.
by mappu 4y ago
Haruhi is an anachronism here, that was well into the Windows XP era.
382.
by mappu 4y ago
Just a casual heads-up - https://time.com/12597/the-ukraine-or-ukraine/
383.
by mappu 4y ago
My reading of that statement is that there's no problem with mandatory cross-licensing. Instead it's about other companies - who did not help with AV1 development - being strong-armed into joining the cross-licensing agreement.
384.
by mappu 4y ago
The scale of the App Store, or iphone-vs-android in general, or even other markets such as semiconductor lithography - is just so mind-bogglingly massive in scale and cost, that the entire human race only has one or two entrants. It's
385.
by mappu 4y ago
> Effectively a private Zoom session. I just wanted to let you know that this comparison absolutely threw me. Of course you're right, they both let you "screen share" but the way you applied a 2022 metaphor to explain 90
386.
by mappu 4y ago
A possible middle ground here is to allow GitHub OAuth2 logins to your Gitea instance - then at least GitHub users can join in your project without too much friction.
387.
by mappu 4y ago
Git for Windows currently supports Vista and above - the AF_UNIX support was only added in Windows 10 1803. Named pipes are fine, the semantics are basically identical, and you can guarantee there is a separate namespace versus the filesyst
388.
by mappu 4y ago
There's a secure channel here (TLS) and then the blob encryption all happens clientside, so i don't think a PAKE-type solution is less mechanism, but i do recognize your expertise on that. Where do you think it would fit in? Backu
389.
by mappu 4y ago
I think this level of key management is relatively simple for a production application. There are not really too many pieces and certainly no unnecessary steps (the mitigation recommendation was to add more keys, not fewer). The interesting
390.
by mappu 4y ago
Restic had some professional cryptanalysis, and was very well received.

More ›