Home Creators Posts Import Register Favorites Logout

Content

Hello everyone!

8.14 update is now available for download.

As always, thank you very much for continued support!

Josef

Fixed:

  • Humble import fails in some cases

  • Amazon integration doesn't import all games

As with 8.13, this version is only available as an update after you  install 8.11. I can't make full installers available on the website (or  GitHub) because browsers and AV software will complain that Playnite is  a virus, because these builds are not signed...

Anyways, here are full packages if you really need them:

https://playnite.link/update/stable/8.14/Playnite814.exe

https://playnite.link/update/stable/8.14/Playnite814.zip

Comments

Tyler Szabo

I really like that you tag it on GitHub right away so that us that build from source get it, too.

Josef Nemec

Can I ask why are you building it from source instead of using official builds? I don't mind, I'm just interested knowing why would you do that.

joshg253

Josef, (sorry if this is answered elsewhere) What is the plan going forward re the Unsigned Builds?

Josef Nemec

The plan is to start signing builds as soon as I get need certificate. I'm getting it from different authority this time. But even then I will be able to only sign Playnite 9 builds because of some restrictions this new authority has for open source projects.

Tyler Szabo

I wrote this whole thing a few days ago I think I deleted the wrong post when trying to reply. I'll try my best to reconstruct it: 1) I like that I can fix issues or make improvements and contribute those fixes back if others also like the changes or run a locally patched copy. 2) The features that involve authentication make Playnite a very privileged application and thus make your build system a valuable target for someone with malicious intent. I don't think that you would have malicious intent (you'd have too much to lose) but I've seen bigger operations become compromised for a supply chain attack and running a local build gives me a little bit more safety. 3) If you were to move on from Playnite (perhaps other interests, a non-compete from a new job, selling it) then I would not have to worry about how a new steward would handle the project; I could continue to use it tomorrow the way I used it yesterday - especially with locally hosted Playnite Services. I could continue to patch it if there were any issues (OS updates breaking things, new requirements, etc.) 4) If the project were to make a pivot and drop core features that I was using then, I still would have a working project and I could potentially backport the new bits that were handy without giving up the features that I had relied on. Also FOSS projects are cool and running something you built from source is fun. I feel like before I create an issue that I should debug locally, first, and make a more meaningful bug report (or ideally come ready with a potential fix). I truly believe the nature of this being a FOSS project is what will allow it to endure in a space where there's plenty of flashy, opaque options that drop features on a whim and are always trying to do some kind of vendor lock-in.