I dabble in coding, linux, gaming, HEMA, LARP, e-mobility, carhacking, simpits and… parenting?

  • 61 Posts
  • 104 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle





  • Feel free to share your sources.

    The source is the technical spec. Read this yourself more closely!

    Interoperability: The solution ensures seamless integration across diverse device operating systems, wallet applications, and online services.

    And let’s not ignore the demo part:

    The white label solution will be implemented based on the open source EUDI Wallet Reference implementation libraries.

    And yes it is good that people watch this carefully (and voice their concerns in a civil matter, which does not seem to be the case with most heated comments from your examples). But!

    This is the very same with e.g. Let’s Encrypt. Or a VPN ‘service’. Or CloudFlare, that so many people love to hide behind.

    What ifs. The spec does explicitly not allow exactly this and it’s our job to investigate such providers closely and in doubt start and run trustworthy providers ourselves. And Let’s Encrypt is again a prime example for something like this.

    Oh and no nothing in the spec nails this down to Google or Apple alone. These are examples for smartphones for existing eco systems. I do not need a smartphone for e.g. AusweisApp and I will ask the same for E-Wallet because this is also in the specs (Interoperability) and explicitly not tied to some vendor specific eco system but to protocols and cyphers.

    And this is where the next FUD may come in: TPM[1]. This does [also] exactly this: Device attestation and is a perfect candidate for regular PCs. That’s probably just the next can of worms for you though and with this I’ll end this discussion because even with plenty of What Ifs I do not see this solved from anyone in any better way - and again especially not from some company like Dis-fuckin-cord. This is exactly what a GOV exists for and they’d be sleeping on their job not providing digital ways for this very use-case.

    [1] And just so that you may understand my POV on this: I demonstrated against TCPA back in the days. I can accept TPM tho. It’s a rather useful compromise and something similar exists for most smartphone ALSO. That is a good thing because this is responsible for keeping e.g. password wallets private. Something the “oh noes, Windows requires TPM now” crowd never understood - and this is from a die hard Linux user for decades.


  • This is not how remote attestation works. It’s the whole point of the age verification of the wallet that such meta data doesn’t have to be stored. The data submitted is transparent and can be viewed before accepting the verification. It’s in the core concept that this process is unlinkable and the goal is to implement this with ZKP (Zero-Knowledge Proof) mechanisms.

    That is in the technical spec for this proposal. It is designed for exactly this kind of requested online anonymity.

    Does this have to be watched? Absolutely Yes. What you’re doing here is spreading FUD though without any proof whatsoever just because “iTs fRoM tHe gOv”. Now I don’t know your frame of reference and it’s probably a good idea to keep a healthy level of mistrust in place but(!) the EU does a lot of things correct and I take this over any system designed by a private company that is definitely always only interested in our best: money.









  • Not sure I can follow. There are various IMU systems, of course. The ones I have expose it’s data as Quaternions and I used Euler’s formula to translate this to rotation (orientation). Been a while but that’s what the Breezy xr-driver does now for me under the hood too. With this I have roll, pitch and yaw - the more important ones for games.

    Now in combination with a webcam and OpenTrack I also get x, y, z as position (location). Yes. that also has roll, pitch and yaw, but that is not as precise and will lag a tiny bit by design resulting in motion sickness - so that is not used and simply discarded. This can work fine on it’s own, of course. It really depends on the fine tuning of the settings and mapping and I did use only this before I accessed the data provided by the IMU.

    Does this make a 9DoF device? I don’t think so. There’s nothing like a magnetometer involved. And what would the use-case be? I’m not a plane xD











  • So often connected devices have to be “overriden” again within Wine too.

    There are now still 2 entries for the same Model and Vendor id in the Wine reg. One for xinput. And this is e.g. prioritized by some games like Elite so they will only start to listen on xinput here, where nothing ever arrives. In that case references to xinput have to be removed again from the registry. Only to be auto repopulated by the next Proton upgrade in some cases or when the device enumeration changes for some reason. Pain.


  • I do this but that’s not all. There are some options that remap especially additional joysticks to SDL XInput Mapping devices automatically. Probably(!) back from the days where games could not deal with more than one joystick anyway. Layers in layers and sometimes it’s detective work to figure out why and where the device stopped working. Again. And this is before the terribly broken input system of some games is even reached.

    Random trivia: Touch panels count too.