Okay, so this makes me love the open source itch.io client even more! The client has been updated to 23.3.0 which include some pretty smart updates.
If you're on a 64bit install, it will now prefer the 64bit builds of games to the 32bit version.
On top of that, it will specifically tell you what dependency is missing:
That's extremely useful!
Other Linux-specific fixes:
- When registering the itchio:// protocol, the wrong .desktop name was used. The correct one is now set.
- The .desktop file had some validation errors.
- Trying to configure a game with a fifo in the folder would get stuck forever. fifos are now ignored when looking for executables.
See the full release notes on the github here.
I do enjoy watching the itch app progress, as it's really slick looking and actually works really damn well too.
Have you guys been using itch for much? Let me know some good finds to check out in the comments.
If you're on a 64bit install, it will now prefer the 64bit builds of games to the 32bit version.
On top of that, it will specifically tell you what dependency is missing:
That's extremely useful!
Other Linux-specific fixes:
- When registering the itchio:// protocol, the wrong .desktop name was used. The correct one is now set.
- The .desktop file had some validation errors.
- Trying to configure a game with a fifo in the folder would get stuck forever. fifos are now ignored when looking for executables.
See the full release notes on the github here.
I do enjoy watching the itch app progress, as it's really slick looking and actually works really damn well too.
Have you guys been using itch for much? Let me know some good finds to check out in the comments.
Some you may have missed, popular articles from the last month:
6 comments
I just spend a few minutes searching around for the cause of some libxcursor errors and later updated to 23.3.0. If only I had waited a few minutes. Eh, you learn something new with every breakage.
0 Likes
itch.io team needs to get rid of their callback hell and creepy .. i don't know how to call that what they do. unnamed functions to a variable being later parameter to a function reassigning to a callback...
brrrr. I have no damn clue how they can maintain their software except if the guy or girl who wrote it is still there.
And ye, I plan to get an ugly code example for itch client on each release :D.
Last edited by STiAT on 14 March 2017 at 11:28 pm UTC
const code = `(function () { document.body.scrollTop = ${oldScrollTop}; return document.body.scrollTop })()`;
this.webview.executeJavaScript(code, false, (scrollTop) => {...
brrrr. I have no damn clue how they can maintain their software except if the guy or girl who wrote it is still there.
And ye, I plan to get an ugly code example for itch client on each release :D.
Last edited by STiAT on 14 March 2017 at 11:28 pm UTC
2 Likes, Who?
You can thank/hate me for the critical bug.. I was hoping they'd fix it immediately but maybe I missed the cutoff for this release. I didn't dig into their release cycle.
TLDR For now, definitely disable the sandboxing. It's using an outdated library that has several critical CVE fixes since then. I don't even want to think about someone putting payment info into the client (hopefully that's done in the browser, but I haven't bought a game on there and wouldn't know).
I definitely appreciate the overall fast response time and feedback. I assume it'll be updated in the next release.
EDIT: Long term, on my TODO list is dig into the : / eek .. TypeScript and implement a native library method so that if you're on a rolling release and have a later version of the library it is used instead of downgrading.
Last edited by saildata on 15 March 2017 at 2:45 am UTC
TLDR For now, definitely disable the sandboxing. It's using an outdated library that has several critical CVE fixes since then. I don't even want to think about someone putting payment info into the client (hopefully that's done in the browser, but I haven't bought a game on there and wouldn't know).
I definitely appreciate the overall fast response time and feedback. I assume it'll be updated in the next release.
EDIT: Long term, on my TODO list is dig into the : / eek .. TypeScript and implement a native library method so that if you're on a rolling release and have a later version of the library it is used instead of downgrading.
Last edited by saildata on 15 March 2017 at 2:45 am UTC
2 Likes, Who?
Quoting: STiATitch.io team needs to get rid of their callback hell and creepy .. i don't know how to call that what they do. unnamed functions to a variable being later parameter to a function reassigning to a callback...
const code = `(function () { document.body.scrollTop = ${oldScrollTop}; return document.body.scrollTop })()`;
this.webview.executeJavaScript(code, false, (scrollTop) => {...
brrrr. I have no damn clue how they can maintain their software except if the guy or girl who wrote it is still there.
And ye, I plan to get an ugly code example for itch client on each release :D.
Agreed. That's gross. Did you lose formatting in copy/paste? Many people forget that the code you write is only for human eyes.. that's what the compiler is for :)
0 Likes
Love itch.io So many odd gems that I discover it reminds me of the early days of indie gaming as they came out of flash site and starting make computer games.
0 Likes
Quoting: MegazellLove itch.io So many odd gems that I discover it reminds me of the early days of indie gaming as they came out of flash site and starting make computer games.
Ahh Flash... I keep Chrome around for anything that must have Flash support (that list is growing smaller by the day...) for anyone on Firefox, you can completely disable Flash support in about:config,
plugin.state.flash
set to 0. (1 = ask to activate, (should be the default setting in FF 53), 2 = always activate (current default in FF 52)).
Definitely recommend also setting the Chrome config to 'ask to activate'. Having it on by default is just silly in 2017.
The number of exploits that involve Flash has a long and nasty history. I'm guessing that browsers have kept it around because developers have been so slow in migrating to HTML5. Maybe because browsers have continued to support it... circle of life : )
0 Likes
See more from me