I’m very interested in this approach. I’ve hosted friends’ websites for decades but I’ve been the single-point of failure, so “cooperative” is very enticing.
I’m currently working on a cooperative “lights-on” solution which might be complementary.
I don't know much about the SSH this app uses (Citadel) which uses NIOSSH under the hood. I prefer using Mosh (https://github.com/mobile-shell/mosh) for mobile apps where connectivity is often spotty. Does NIOSSH use a model that accounts for that?
NIOSSH itself doesn't include Mosh support, so adding it would require a mosh client. i didn't include it in the initial beta, because mosh isn't direct fit for tmux control mode, which requires an ordered raw byte stream. i'm planning to add mosh for standalone terminal sessions tho.
This is such a garbage take. Yes, if you're running a cloud-backed service, a subscription makes sense. But the overwhelming number of complaints have been when previous download-only apps (e.g. Photoshop) become part of a subscription service (Creative Cloud). And people complain when the option of a thing that didn't need the cloud (like a garage door opener) now is only available in a subscription model (see "Unauthorized Bread" by Cory Doctorow). It's called "enshitification".
yes but again, who has $2M to bet, even at 1/500 odds? You have to be a billionaire to make 500 bets hoping one hits, then you’re back to just being a billionaire again.
I would short xAI but the market can remain irrational longer than I can remain solvent. Plus all the foolishness to prop it up with other businesses just seems like bad accounting.
Bullets don’t kill you, it’s the bleeding that gets you. Wait, no, it’s not the bleeding since you could just put an IV in, it’s the loss of blood pressure. No wait, it’s not the loss of blood pressure since we can reattach severed limbs that have been at 0/0 for hours. It’s the lack of oxygen to the brain and other vital organs. Bullets definitely don’t kill you /s
16 bytes equals immediate “black magic” and “it’s a witch”. I get it in the abstract - generative art and CAs and fractals have infinite depth. But this is madness. I love it so much
> For 7 months I'd been prompting and shipping without ever sitting down and actually reading the code Claude wrote. I'd look at the diff, verify it compiled, test the happy path, move on. But now something was fundamentally broken and I couldn't just prompt my way out of it.
I stopped reading after this, because this is the dumbest way to vibe code anything larger than a single-use tool.
Claude is a collaborator, and honestly a decent voice of dissent, but it will never offer that unprompted. "Make this thing" - "OK".
You need to review the code. You need to say "I want this, AND HERE IS THE LONG-TERM VISION. Now offer critique and the trade-offs for various implementations."
Or just realize that in every hand-written project you learn the contours of the problem space as you go along and if the tool is big enough you'll feel the urge to do a green-field rewrite of hand-rolled code after a few years. You get there quicker with the robot's help. This is not a new lesson.
“I was using, at times, pretty lackluster equipment, simply because I had no money to buy anything better,” he said. Later, he moved on to digital audio tape, or DAT, and, as technology progressed, to solid-state digital recorders."
Hashcash was a proof-of-work system that would have put a computational tax on email. I don't know what kept it from getting more traction other than simple chicken-and-egg network effects, but it's a good idea, and worth resurrecting.
TLDR: Mail storage is the sender's responsibility. The message isn't copied to the receiver. All the receiver needs is a brief notification that a message is available.
Sounds like a horrible system where you retain many of the problems of email (you still need to deliver notifications) and new surveillance and persistence and mutability problems layered on top..
I’m currently working on a cooperative “lights-on” solution which might be complementary.