• 0 Posts
  • 49 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle
  • Since you’re still a Windows user at least for now, and assuming that you’re planning on continuing to be open-source, I can recommend Certum for this. https://shop.certum.eu/open-source-code-signing.html

    I gave up trying to initialize the USB thingy using Linux (I tried regular Arch [btw] and an Ubuntu distrobox IIRC), but once I got through the initial steps using Windows, I was able to sign ongoing builds with Linux just fine. It took a LOT of trial and error since there seem to be very few people who simultaneously

    • pathologically dislike using Windows regularly
    • still want to make it easier for people on Windows to minimize Windows Defender complaints when running software that they build
    • have the motivation and resolve to send a lot of PII to one of a handful of companies whose longtime business model is based around reputation and trust in order to get a usable certificate
    • are stubborn enough to go out of their way to still figure out how to do a subset of this stuff on Linux
    • are capable of actually succeeding at that, and
    • are willing to show how they did it in a way that should be reasonably easy enough to understand and adapt to your situation

    I didn’t renew after my first year - I switched from publishing an executable to publishing it on the web, so I no longer had a need for it - so I don’t know how things have changed (if at all). Most of my information came from eventually stumbling upon this wiki page for a Ruby-based tool where they figured out the last bits I needed to get it to work.

    • It also has instructions for initializing the USB thingy on Linux too, so if I were to renew, I’d give that a fair shot… but seeing “icedtea” and a link to a web application that no longer resolves, I’d still only recommend it if you can use a Windows machine once a year.




  • I got one in like 2009 or so as a student at university. It literally paid for itself, because it also let me get a discount on a new laptop that was bigger than the price I paid the Linux Foundation.

    I can confirm that my linux.com e-mail is still active, and I’ve changed where it forwards over the years.

    Just make sure that wherever you’re forwarding it, you can reply from that same address. GMail has been fine for this, but when I switched to a different provider that didn’t support this, conversations started getting awkward.









  • If shaders don’t get preprocessed, then a lot of the same work has to happen later, it just shows up as a seemingly random frame that takes particularly long to render.

    (edit to add:) or a section where some of the rendering doesn’t look quite right initially, if they do asynchronous rendering.

    In the limit, the sum of all these delays can add up to the same amount of time that the preprocessing WOULD have taken, but you also don’t necessarily use every shader every time you play every game, so YMMV.



  • JPEG also supports lossless compression.

    Technically, the spec does require it, but given that we’re in a thread about ecosystem support for a file format that’s approaching its 15th birthday, it’s worth considering how many image viewers will actually be able to work without the DCT step that is the essence of what typical JPEG does.

    I don’t have a Windows machine handy to test, but it’s entirely possible that maybe lossless JPEG won’t display in its default viewer.