Mandatory client-side scanning of encrypted messages has been removed from the proposal following opposition from the European Parliament and several member states, preserving E2EE integrity
And you believe they won't try again and again until they push it through? All of these have already been rejected multiple times, and yet some parts of it are already enacted, some will be soon, and the rest will come after a few more tries.
Amazing! Might be a real game changer as Supabase's uptime is not the best to be honest. I hope they can also improve on that otherwise this might be the way to go.
Making Wasmer Edge open source would convince me to use Wasmer instead of the other options! I can see that this is on the roadmap. Any ETA you can already share?
Also I would be interested in restricting specific requests to certain regions.
Good point! I believe none of the other Edge platforms are fully open source yet (I don't mean their runtime being OSS, but the Edge Platform itself). Clouflare Workers is the only one that gets there half way with Workerd (they are missing KV, other APIs and the glue-code).
Right now the Wasmer Edge product usage is not in a stable enough point to make it open-source. I'd love to share the timelines, but anything that I say now will likely be wrong (as we are still iterating hard on the product).
> I would be interested in restricting specific requests to certain regions
I can see this being an issue if you plug the workload with data that is located in a specific region (for example, via a DB connection or doing API calls to an API in a specific region). Is that your use case?
