More complex stuff you can build on the “outside”. So keeping it local seems ok, because it’s just the LLM facing part.
9,625 karma · joined May 18, 2013
morten(at)punnerud.net
Some hobby projects: https://claude-checkpoints.com https://blank-black-screen.com https://politihelikopter.com http://punnerud.github.io/CamDelete https://punnerud.github.io/Auto-Mouse-Jiggler-Mover
More complex stuff you can build on the “outside”. So keeping it local seems ok, because it’s just the LLM facing part.
Instead of using a global lock ("red-cap"), Python objects have introduced a specialized reference counting system that distinguishes between "local" references (owned by a single thread) and "shared" references (accessed by multiple threads).
In that way enabling to remove GIL in the long run, now starting with making it optional.
Synchronous code is like a single-lane road where cars (tasks) must travel one after another in perfect sequence. If one car stops for gas (waiting for I/O), every car behind it must stop too. While orderly and predictable, this creates massive traffic jams as tasks wait unnecessarily for others to complete before they can proceed.
Pure asynchronous code (with callbacks) is like dispatching multiple cars onto independent routes with no coordination. Cars move freely without waiting for each other, but they arrive at unpredictable times and following their progress becomes chaotic. It's efficient but creates a complex tangle of paths that becomes hard to maintain.
Async/await combines the best of both approaches with a multi-lane highway system. Cars follow clear, synchronous-looking routes (making code readable), but only wait at strategic "await" exit ramps when truly necessary. When a car needs data, it signals with "await", pulls off the highway temporarily, and other cars continue flowing past. Once its operation completes, it merges back into traffic and continues. This gives you the logical simplicity of synchronous code with the performance benefits of asynchronous execution - cars only wait at crossroads when they must, maximizing throughput while maintaining order.
The genius of async/await is that it lets developers write code that looks sequential while the runtime handles all the complex traffic management under the hood.
Title:”0-click deanonymization attack targeting Signal, Discord, other platforms”
Maybe not 0-click anymore, but still applies if the user browsing the internet.
Uses OpenStreetmap file, Python and SQLite3.
First it finds all addresses using +/- like a square from lat/lon, then calculate distance based on the smaller list (Pythagoras), and pick the closest. It expands until a set maximum if no address is found in the first search.
Mapping from one JSON with a lot of plain text, into a new structure and it fails every time.
Ask it to generate SVG, and it’s very simple and almost too dumb.
Nice that it doesn’t need that huge amount of RAM, and perform ok on smaller languages from my initial tests.
When I see the stats on paying Android users compared to iPhone, I feel I always will start on iOS and only maybe make to Android if it’s successful somewhere else first.
I guess the fixes have to start there first.
I guess OpenAI and Google use that to be able to build search and training ML-models. Almost all countries in the world is bounded by that.
Some of them have Facebook, but turned off all notifications and never check for updates. So they can be counted as not having it.
Had a good laugh from this.
Should maybe have been a separate AppStore category for apps dedicated to this mode. I would probably try to make an app or two for it, if it existed.
Example you used the normal Signal app without patch and sending me a message, and I have the patched version.
Just to remove certificate pinning, to be able to see the API traffic because of encryption.
Could we have PyTorch / ML training with CUDA through the browser performing ok?