dobremeno

I haven't heard of this behavior before. Could you elaborate or link to some evidence of it?

I have my AC connected using Matter (over WiFi, not Thread) using esphome-matter, a relatively new extension to ESPHome + a small open PR [1]

Since it's running ESPHome you can easily verify everything it's doing.

Thread would be even better but this is good enough for me. 100x better than the original cloud app it came with. Still no proprietary app required, works on every platform.

[1] https://github.com/DavidvtWout/esphome-matter/pull/53

SPy [1] is a new attempt at something like this.

TL;DR: SPy is a variant of Python specifically designed to be statically compilable while retaining a lot of the "useful" dynamic parts of Python.

The effort is led by Antonio Cuni, Principal Software Engineer at Anaconda. Still very early days but it seems promising to me.

[1] https://github.com/spylang/spy

I agree with you that creating a tool is different from providing a service. However, I disagree on the rest of what you said, here's why:

> Nonsense, they didn't give away (or even sell) a tool, they were actively operating the tool themselves, taking requests to control and aim it in different ways.

They did give away a tool - they published (open-source, GPL3) a set of smart contracts. They then deployed those immutable (!) smart contracts as a one-time thing. From that point forward, anyone could interact with those smart contracts permissionlessly, that's just how Ethereum works. They didn't afterwards control or aim it in different ways - how could they? The smart contracts are immutable.

All they actually did afterwards is host a user interface (also open-source btw) that made it easy for users to interact with those smart contracts. After some outside pressure they added geo-blocking to the user interface they hosted, which —unsurprisingly— didn't actually stop bad actors from using Tornado Cash. After all, even if they were unable to get around the geo-blocking, bad actors could self-host the user interface or interact with the smart contracts directly.

Think of their user interface as an email client. Would somehow blocking an email client actually stop people from sending emails? No, they could still just use SMTP and directly interact with a server. In the same way, taking down their user interface or implementing any sort of check would not have prevented bad actors from interacting with the smart contracts directly.

It's just a neutral tool, open for everyone to use. There's plenty of people that used the tool for completely legitimate reasons, simply wanting to protect their privacy just like GrapheneOS users.

Why is the creator of this tool being held responsible for how others use it? That's like dragging Henry Ford to court the moment a car driver runs someone over.

That's like saying Adi Shamir helps drug cartels, Tim Berners-Lee helps facilitate online fraud or that Henry Ford helped kill millions of people on the road.

All these people created tools that could be used by anyone. Encryption, the Internet, cars. All have legitimate uses cases just like Tornado Cash does.

To me, not wanting to have all of your public blockchain transactions linked to you is actually quite similar to wanting a phone detached from the hivemind - all you want is a bit of privacy.

Not just in Europe, in the US too - Roman Storm is on trial as of last week for building a privacy tool that ended up getting used by criminals.

Not much good coverage on it out there apart from the great work by The Rage journalists.

I assume OP meant something like this, building the image on the remote host directly using a docker context (which is different from a build context)

  docker context create my-awesome-remote-context --docker "host=ssh://user@remote-host"

  docker --context my-awesome-remote-context build . -t my-image:latest

This way you end up with `my-image:latest` on the remote host too. It has the advantage of not transferring the entire image but only transferring the build context. It builds the actual image on the remote host.