158 karma · joined September 29, 2026
- Saving, as before.
- Sharing, works, but due to a glitch the recipient got a blank blank image/video. He'll sure reply to let you know, but unfortunately incriminate himself in the process.
- Deleting, as before, no sorry, bugger, I/O error, can't delete this file. But support team has your address and is on their way.I agree that he could do a lot better with controlling his emotions. Me and him are on the opposite ends of the tmux debate for example. But I understand his point, he's trying to solve the same problems that tmux solves, with a very different way.
The problem is that Kitty isn't there yet (I wish it was) and his outburst on the topic are quite damaging to his goals.
When you've met and worked with people in real live that are like that, you can just visualize them and have a laugh at their outbursts.
I'm still team Calibre and Kitty any day and tremendously thankful for what he's doing.
Yes, the system is old and warty, but we know it. It's old Jim the warthog.
JonnieCache: Hold my beer.
(brilliant work btw)
Correct move on handling the financial aspect yourself. I asked my mine to do everything but forgot to give it some dough. It sorted it all out but ended up with $6.3B on its account and I think it might have done something dodgy.
Since most people do click-and-run most of the time (based on decades long research, n=1), I'll just add paste the link for more examples: https://ivankovic.github.io/omnidiff/showcase/content.html
There are over 10,000 taxing jurisdictions in the US, so good luck with even trying to figure how many different taxes.
I've done that to myself quite some times when writing a very detailed report on an issue. Back in the day of stackoverflow (godbless and godspeed, glad Joel made it out and sorry for the investors) you had to be detailed to maximize on your initial viewers.
I think the idea is the same with the rubber duck debugging method although I've never tried it myself.
One of my methods for my pet projects is just to wait for someone else to do it, worked this time :)
I might chuck this into Claude when I have tokens to spare and see how it'll do with my feature request. Are there any specific apple silicone limitations you can remember? I'll send you a PR if you're interested?
<cmd> force-off # pull the plug
No faffing around.> It is not true that some independent AI agent went in and deleted the material
Notice the wording. It's a half-truth response. She's probably correct, but the accusation wasn't that a "some independent AI agent went in and deleted the material". Just a AI deleted the material.
Then backup failed as the reason. That's not THE reason. You don't need backups unless you lose your data. How did the data get lost?
Personally I wouldn't store this info as refs in git.
But If i had to, I'd store them under subdirectories, try "git checkout -b "host/person/version/diet/cookies/bug-fix-for-joe".
It gets created as directory structure under .git/refs.
HarmonyOS 5.x+ both discards the common Unix-like Linux kernel and replaces the previous multiple-kernel, kernel agnostic system from OpenHarmony with its own bespoke HarmonyOS microkernel as a single framework.
https://en.wikipedia.org/wiki/HarmonyOS#:~:text=HarmonyOS%20...
It'd be amazing to hook is up with the engine sound simulator: https://github.com/ange-yaghi/engine-sim
And shortly afterwards, in addition to all the different physics-in-action experience, I learned about how car insurance excess works.
a) access all your files, and
b) roam the internet at will.
That was somewhat OK in the 80s, but it hasn't been since.Perhaps an idea to create a docs/features.md to mention what it can do. Might even help LLMs picking up your project. Thanks again, I'm very exited!