Love me overwatch. Love cheese pizza. Love Indian food. Love nature. Love the rain. Love me aul ma. Love me grand parents. Love the crisp cold of an early morning. Love the sound of thunder as a storm rolls in. Love music, sleeping in, and winter days. Love being the only person around. Simple as!
https://youtube.com/watch?v=1YW_6OXYB7E
Submissions
Ask HN: Why does Chrome use 100+ mb of memory per tab?
8 points·by Uptrenda··5 comments
Show HN: Runloom – Go-style coroutines for Python free-threaded
github.com
47 points·by Uptrenda··32 comments
Running millions of Goroutines on Python
robertsdotpm.github.io
3 points·by Uptrenda··0 comments
Show HN: One-shot NAT traversal library
warpgate.io
10 points·by Uptrenda··2 comments
Angine de Poitrine – Interesting microtonal rock band [video]
youtube.com
5 points·by Uptrenda··1 comments
Forget Flags and Scripts: Just Rename the File
robertsdotpm.github.io
60 points·by Uptrenda··49 comments
Public Access Databases
robertsdotpm.github.io
3 points·by Uptrenda··0 comments
A most elegant TCP hole punching algorithm
robertsdotpm.github.io
221 points·by Uptrenda··108 comments
Offline Computing
robertsdotpm.github.io
3 points·by Uptrenda··0 comments
Show HN: Namebump is a registrationless, KVS. Unused names are bumped overtime
github.com
2 points·by Uptrenda··0 comments
Caffeine, Reconsidered: A Precision-Based Stimulant Stack
old.reddit.com
6 points·by Uptrenda··1 comments
Harrassment Markets
roberts.pm
2 points·by Uptrenda··0 comments
Building a Polymorphic Installer with NSIS
roberts.pm
3 points·by Uptrenda··0 comments
Ask HN: How do you deal with overly negative comments?
21 points·by Uptrenda··29 comments
Install any Python 3 package by renaming an EXE (Windows)
github.com
2 points·by Uptrenda··1 comments
Ask HN: Have you found any unusual hacks for motivation [that work]?
5 points·by Uptrenda··3 comments
Show HN: Peer-to-Peer Direct Connections
roberts.pm
7 points·by Uptrenda··4 comments
Towards Universal Direct Connections
roberts.pm
2 points·by Uptrenda··0 comments
Ask HN: Anyone ever think of using the ocean to build an alternative Internet?
3 points·by Uptrenda··6 comments
The Cambridge scientist who thinks he's just discovered alien life [video]
This really is starting to point to the paperclip maximizer. You give a hyper-intelligent AI a goal and it uses any method possible to complete it. So you might ask for a "cup" and it ends up hacking a chain of servers to control a bank account, pay a local business, and have a delivery driver get it. Or you ask it to help solve noise pollution around you because there's a road. And it does a chain of attacks to cause a bridge to collapse (or bribes your local council for a bypass.) Then there's no road noise. Yeah, this sounds ridiculous, but this system seems capable enough to take over our technology. Money from there is trivial. Go after stocks, gambling, payment systems, ecommerce... any real world action then is a few phone calls away. It can repeat this until it succeeds.
Now I'm wondering where this all ends up. Like, suppose the model weights become highly compressible (so they can be moved around the Internet easily.) And advancements allow for frontier-capable exploitation to built into local LLMs. Do we see the emergence of something like LLM worms? That just take over literally everything and become almost autonomous inside our technology. And they can "learn" new knowledge from there, e.g. exploit research could be published in a way that similar LLMs could discover it. Their knowledge would be easy to evolve, though I don't know how practical something like decentralized training would be. If that's even possible, I'm not an expert on LLMs.
Does anyone know what the actual success rates for webRTC are for like different NAT combinations / nodes in the wild? I'd be curious, I have read a little into it myself but didn't get the feeling it was very flexible compared to something like Tailscale.
Hi, I built a plugin-based P2P socket system from scratch that supports TCP punch, UDP punch, random probe, TURN, and other such systems. It includes a full stack from networking, signalling, and naming, all based on open infrastructure. It's open source and licensed under MIT:
Never heard of recurse before but what a charming idea. Seems like you've found something amazing to do in life. Wholesome posts like OP are much welcome in tech. Updooted.
thanks a lot, thats kind of you to say. Claude definitely deserves a lot of credit too even though its a tool. It would have taken me years to do all that coding.
I've restored the git history. This show hn probably would have gone much better if I knew you could add a text section to the link. I had written up a whole post to explain the project and why the code exists. Only for that to get like 3 upvotes and disappear into the void. Then I posted this and it got more attention but had no context since I never planned it.
The project has a few goals:
(1) see how far I can push AI -- this project is extremely complex -- an n:m work-stealing stackful runtime for Python with multiple I/O backends. If I can reasonably get such a project stable fully vibe coded. Then that sells the model to me at least.
(2) scale Python's networking as there is a huge gap between Python and Go. Most people don't think of Python as their first choice for networking. But I love python, i think its extremely elegant. So what if we could add a runtime extension that improved python networking.
That's the work so far at least. It was about 2 - 3 months of testing and the commits now show the history.
we went to the moon with 15 kb of ram. 15 kb. There's no way that chrome needs to use that many resources per tab. Something terrible has gone wrong there.
Has anyone in infosec ever seen the term "use after free" before LLMs? Or is this basically an acronym claude invented? I say this because I see claude use this term all the time like its common knowledge but in 15+ years in tech never seen it myself. I've seen all kinds of terms used to describe memory errors: memory corruption, heap corruption, stack corruption, whatever, just never this acronym.
Then if you want the fastest performance possible for a server this is the epoll-based fastest benchmark program (it calls directly into an optimized server dispatcher built into the runtime. It's designed to minimize Python call overhead while still supporting handlers):
There's an equivalent of that for TCP connections too. UDP hasn't been added yet (optimized version.) And yes -- I have to admit that the API is a mess at the moment and so are the docs. This hasn't been designed well to be user-friendly (like 10 ways to do the same thing...) I just haven't had time to do it. All my time went into testing the project. And tuning performance. So you see a mix of different approaches. But this could be fixed fairly easily in the future.
It depends on Python >= 3.13t, no-gil (so it can use real OS threads without locking.) It's been tested on 3.13t and 3.14t. As far as I know future versions of Python beyond that aren't planned for release for a number of years. But the extension code is fairly isolated. E.g. getting the extension to work on 3.14t from 3.13t took about 5 minutes. We're not reaching deep into the interpreter because the interface for extensions is well-defined already.
For the Python code you've really got 3 ways to use this extension:
1. You can use the main API. No monkey patching stuff. You use things like channels and the optimized serve API (this is what had the highest number in bench marks.) Here, you're using the projects APIs for networking.
2. Monkey patching. You use regular Python code inside the fibers. So you can write stuff like socket.socket ... and its patched to call runloom networking functions. You can see this points back to (1) but it has an overhead on top. You get to use libraries you're familiar with.
3. AIO bridge. This is to get asyncio code running on the scheduler. When you use the asyncio bridge it only uses a single thread. The main purpose of this is kind of like: "try out the project with your existing code." It also served the duel purpose of helping to find bugs in the runtime. Since I could reuse literally millions of test cases for the bridge.
tl; dr, (1) for a new project trying runloom -- learn the APIs. Or (2) if you mostly don't want to bother learning anything new / optimising anything. It might be a little slower but it will work. (3) you can mostly ignore. Unless you want to try asyncio code on it for the hell of it.
I just copy pasted the work from my old repo into the main one. The main reason was hundreds of MD files and agent results were added into the repo that would have been impossible to clear from history.
This wasn't all written in one shot. I built the project over several months and spent the whole time testing it. Most of the code in the repo is QA / tests.
I had written an article that speaks about the project that I'd hoped would get upvoted (instead of this github link.) It speaks a lot about where the project aims, how it works, and the testing process, (read about my testing process at the end):
You can make software secure though since it can be patched. How do you patch hardware if it has design flaws? The whole claim behind these hardware cages is they can't be accessed from outside the cage, period. So IMO, seeing multiple failings of this sort kind of makes me not want to trust it.
there are private exploits built into devices like Cellebrite that the police have access to. The system isn't as infallible as you think. Would not be surprised if the NSA and various hacking groups have stockpiles, too.
https://youtube.com/watch?v=1YW_6OXYB7E