ownedthx

The numerical issues here are due to JavaScript, not JSON.

It’s writing colloquially… the writer has the difficult job of describing something that’s happening inside this cabinet over time and space and other dimensions Imposed by the game and players behavior.

Bear with us means, ‘I’m about to do a bunch of description… shore up your mental banks and prepare to reread the next bit a few times.

Man

Amish furniture is built extremely well. And the price is not cheap but not exhorbiant. And clearly American made :)

If you had lived through the last blackout and still lived in Texas, then absolutely yes it’s newsworthy. We want to grade our government accurately. Almost having a collapse again is a bad mark on the test score.

JamKazam founder here. Happy to come across a user!

We see that too: 25ms one-way latency is the max to stay in sync, and that includes both internet + audio device encode/decode, which gets eaten up quite fast!

We are looking at providing an optional premium networking service to offer a faster connection as an alternative to the open internet. Nothing too expensive, like $10/month is the goal. Hope that gets you and your friends under that magic threshold when it's available, if you try it out.

Get them out of the house. It's the same quitting unhealthy food. Take away easy access, and you'll do something else.

The frontend is all HTML inside of the webview.

We do have a tray icon too, though.

We have a website presence too, and the website UI (as visited in a normal browser) is 95% the same style and functionality as the desktop app.

So when you browse to our site via the desktop app, certain OS-only features turn on.

So it made a bunch of sense to use QtWebkit. I welcome the switch to QWebEngine though, if for nothing else in the hopes that the underlying browser code gets a update and the app will hopefully then feel more responsive.