geneva VS trio

I think cryptography is a decentralizing force in general, though its intersection with ML is small, Also, related things, steganography, differential privacy, federated learning, all things that tend to decentralize. Anonymizing text fingerprint with LLMs, ML-ish censor evading algo , possibility of a decentralized vector database

China just blocks ESNI entirely, possibly Iran too, and I'd assume once ECH becomes popular they'd do just that. The paper points out it's trivial to defeat the blocking, but there needs to be at least a client or server-side modification, which is kinda out of scope for your app & service. Would Cloudflare join the cat & mouse game? Probably not, considering in China they choose to cooperate with the local entity.

> The fact that Western countries aren't spending billions to comprehensively subvert the Great Firewall is a significant strategic failure.

I have strong opinions in this matter.

The GFW is only possible because of metadata leaks that Western countries are exploiting too, for security and surveillance, or whatever.

Suppose Western countries start investing billions in subverting the great firewall, our own infrastructure and economy would suffer too.

I'll give you an example, I tried to train https://github.com/Kkevsterrr/geneva against a CheckPoint and a Fortinet ... It's not been fun for those "next gen firewalls", and CheckPoint is a NASDAQ-100, Fortinet an S&P 500.

Incidentally, the alternative event loop implementation trio in python does not have "gather", you also need channels, and it's a deliberate design choice - there is some discussion about that in this ticket https://github.com/python-trio/trio/issues/2188

trio – a friendly Python library for async concurrency and I/O

trio. the best code, the best documentation, awesome community.

I'll +1 the Trio shoutout [1], but it's worth emphasizing that the core concept of Trio (nurseries) now exists in the stdlib in the form of task groups [2]. The article mentions this very briefly, but it's easy to miss, and I wouldn't describe it as a solution to this bug, anyways. Rather, it's more of a different way of writing multitasking code, which happens to make this class of bug impossible.

[1] https://github.com/python-trio/trio

[2] https://docs.python.org/3/library/asyncio-task.html#task-gro...

It's similar to manual memory management.

Structured concurrency is one approach to solving this problem. In a structured concurrency a promise would not go out of scope unhandled. Not sure how you would add APIs for it though.

See Python's trio nurseries idea which uses a python context manager.

https://github.com/python-trio/trio

I'm working on a syntax for state machines and it could be used as a DSL for promises. It looks similar to a bash pipeline but it matches predicates similar to prolog.

In theory you could wire up a tree of structured concurrency with this DSL.

https://github.com/samsquire/ideas4#558-assign-location-mult...

Not complete - doesn't include Task Groups [1]

In fairness they were only included in asyncio as of Python 3.11, which was released a couple of weeks ago.

These were an idea originally from Trio [2] where they're called "nurseries" instead of "task groups". My view is that you're better off using Trio, or at least anyio [3] which gives a Trio-like interface to asyncio. One particularly nice thing about Trio (and anyio) is that there's no way to spawn background tasks except to use task groups i.e. there's no analogue of asyncio's create_task() function. That is good because it guarantees that no task is ever left accidentally running in the background and no exception left silently uncaught.

[1] https://docs.python.org/3/library/asyncio-task.html#task-gro...

[2] https://github.com/python-trio/trio

[3] https://anyio.readthedocs.io/en/latest/