unmasked_poker

most probably you are right. But I could imagine crosshairs are not needed anymore with highly accurate eye tracking, you would just intuitively know where you are aiming anyways.

I solved this for me with a custom visual studio extension. It allows me to quickly specify a pattern that will create new code or change existing. The extension will show a so called Code Lens for each possibility to apply the pattern. This way for all the tasks I find my self doing over and over again I design the pattern as some kind of master and then apply it again and again on hundreds of locations in many projects. (some things I have solved this way: prisma schema, GraphQL resolvers, frontend code matching my backend API including full typings, ...). Saves me tons of work but I still have 100% controll over the code.

The PI is needed for bridging our PCM3060 based custom sound card(via hardware i2s) with a WebRTC client that connects to the customer. It also handles all the high end internet connectivity and allows us to easily flash the microcontrollers with new software. It could have been done with audiointerfaces instead, but this approach is truly modular and allows us to scale it easily.

Noise was a hard problem as well. In the end what helped us a lot was to keep the FX device in its own case and even solder the digi potis right in place where the real potis had been before. You can see that here: https://im.static-thomann.de/pics/images/stompenberg/backsta...

The relais modules are on the outside of the case, but on the left you will see a flatband cable (digital) run inside of the case, where the digipoti modules will sit. So all analog signals never leave the original case and the metal housing shields all kinds of external interference.

Our main concerns were a) the conversion process would be much more complicated b) hardware would be more expensive c) the motors would not live as long as the digi-potis

The digipotis were actually one of the hardest problems for this project. Additional to the many pot values and different tapers, you need to also cover a wide variety of voltages that can even be centered around zero (it is an audio signal after all), so you need to be able to handle negative voltage. DigiPots also have a capacitance, so when you have to replace high values like 1M-Ohm you will wind up with a low pass filter. We built a bunch of modules for common pot values and do the taper and uncommon values in software. If both sides of a poti are used, we will need to use two digipotis to simulate them.

Usually the amount of crypto that can be mined in a given time frame is limited. So you could buy more hardware, but it would not be profitable.

The bitcoin network will take exactly the same amount of energy mining an empty or full block. So a transaction does not use much energy (except for propagating it etc). By holding bitcoin, you reduce the supply, thus increasing the price of bitcoin. By increasing the price, you increase the value of the block reward, thus making it more attractive to mine bitcoin. So actually holding it, not transacting, will increase energy consumption.

There will be a lobby for public tables at some point in the future, but at the moment you would have to organize it your self (e.g. by posting a link to a table here)