Format: Aside

I’m having way too much fun with this. Did some plumbing today and this is the result 😀

I patched the http server of https://github.com/Alia5/X4-rest-server/ to send Access-Control-Allow-Origin so the browser wouldn’t refuse to load. Could set up a proxy but I wanted results fast xD

The flight instruments are from https://github.com/uw-ray/Skyhawk-Flight-Instruments and are not for obviously.

  • Speed is also mapped to ALT as Fast Travel speed
  • It reads just the camera position and not really the ship position (and since there is no up and down in space it settles fast on the new artificial horizon – may need some more tuning)
  • Plumbed the speed to the pressure so it starts creeping up from 27.1 inHg to 33 inHg (max on the instrument) when speed goes over 200. Just for fun.
  • Turn Coordinator is just Camera yaw + left or right based on mouse/pointer X.
  • Some target data as proof of concept

This worked out better than expected and the best thing is: Doesn’t need to run on the same computer – it just has to be on the net so a tiny Raspberry and some external display would be enough for some fun cockpit building 8)

Posted on
by

I found https://github.com/Alia5/X4-rest-server/ today and it makes me way to excited. Tricky to set up and “just” a proof of concept (that proofs very well) but look at this: with a REST server that lets you read (and partially set) additional gamedata more or less live. Awesome! Could plumb all sorts of stuff on that!

Misinformation about Permissions Policy and FLoC by Rohan KumarRohan Kumar (seirdy.one)
This post was written in a hurry in response to some misinformation about Google’s newest Web antifeature, Federated Learning of Cohorts (FLoC). Google’s FLoC is an attempt to track users even when their browsers (rightly) block third-party cookies. The initial blog posts about this issue were q...

Who would have guessed: That empty policy header against FLoC is probably worthless in the first place because people that are concerned about this are probably not affected by a prior opt-in at all: https://seirdy.one/2021/04/16/permissions-policy-floc-misinfo.html

Really curious what else will show up on this topic over the next weeks.

Whatever happened to IoT smoke alarms? by @edent@edent (shkspr.mobi)
I’ve had a Nest smoke alarm for about 7 years. It connects to my WiFi network and occasionally pings a message to my phone that I’ve burnt my toast. Nifty! But, due to planned obsolescence regulatory requirements, it needs to be replaced. In app warning that my Nest smoke alarm needs replacing. ...

I love reading about your IoT journeys @Edent whilst completely ignoring my own. Like that washing machine I have, that in theory is able to connect over the wifi to… yes to what? I guess to some vendor API and I assume it does so over WEP only too. Or our central heater, that used to have it’s own gateway but since the company never got it running they patched it out so now it sits on my regular subnet and sends an occasional mail unsecured to some SMTP gateway. Don’t think it even uses hardcoded credentials for this. Oh the possibilities (and dangers)…

I know. And weep. And I ignore it. I’m too busy with other things than “fixing” or getting this zoo under control. It’s a mess. It’s the Internet of Shit.

Yikes, looks like some Webmentions didn’t make it to the blog. Very confused about this but it seems like some buffer was too tight. I may have to revise my setup.