I think he hit both of us, sped off and weaved through traffic to get away. Sigh. Got his plate though, so guess who will hopefully get a visit from the police soon.
Since it's the end of the month, I've cleared used up my 500/500 included, as well as $555 USD, but then below the on-demand it says $650/user.
I'm a little confused about the $555 vs the $650?
(I am capped here, Composer 2.5 works still of course, but I can't use anything else, so the 555/555 is definitely a limit that's applying.
So they have systems that can scan & weigh all our packages, and then take the action to send a $3.90 adjustment to my account. Okay, frankly, I'm fine with that. Sometimes it's a bit sus. My 30x30x5 mailers somehow occasionally scan as 31x31x5, and somehow I owe an extra $3. Okay, fine, whatever.
But never an overpayment -- Surely their scanners detect this just as well, right? If the onus is on me to "bill it correctly", but then they get the chance to claw any extra for my mistake, why do they not also refund the difference?
Seems dishonest and dodgy to me.
So version 1.5 is out now! I haven’t actually posted here since the 1.0 release, so I thought I’d post again to see if more people are interested.
https://apps.apple.com/au/app/pandawatch/id6758112923
Entirely on-device, supports Bambu cloud or LAN only mode for talking to your printers, LAN discovery, multi-camera feeds, an at a glance dashboard view of status.
A lot of bugs fixed, iPad quirks resolved, and a new watch app in this release!
This is a project I started at the end of last year for myself. I have 9 printers, and Handy just doesn’t cut it for at-a-glance view on the phone. Home Assistant is great for a dashboard, and I still run that on a screen above my desk, this isn’t a replacement, it’s an additional tool, or something for someone that just wants a quick view.
1 printer or many, it’s useful to anyone. Or so I hope.
Android version is still coming, slowly, so stay tuned. I’ve finally gotten myself an older galaxy to test properly.
This has been a labor of love, I built it for myself, took feedback from people that tried it out in version 1, and I think it’s a really well rounded app now.
So please, check it out, ask questions, request features! I’d love to know what else this could do for you!
I’ve been able to use the api key to set it up in Riders own “chat agent” and it works flawlessly, but of course can’t code from there. I’ve also got it working with openclaw and some scripting projects and it doesn’t miss a beat.
I setup ProxyAI in Rider and configured deepseek there and it passes the tests, and can do some work, but it regularly gets “agent gave 400 error” while trying to do agentic coding work.
I’m guessing this is due to how it’s being called not the model itself. Anyone know a better rider plugin that works with DSv4, and/or overall tools instead of rider? (macOS development)
So I run a number of small side projects, all basic s3 + cloud front + lambda APIs, cheap/almost free. I’ve been paying $4/mo for work mail for one mailbox with many domains mapped to it, to get support and basic emails from them all.
With workmail going away, I’d been considering moving to azure, but now I’ve been thinking about jira service desk. This isn’t personal mail or “conversational” mail, it’s support or enquires about my small projects, it actually makes sense to handle them as tickets rather than mail.
Anyone tried this path instead of a mailbox for their projects?
This has been happening way too often of late. Doesn't matter if I'm using Opus 4.7 or 4.6 (though switching to the other when it happens seems to help) -- I just hate how much it interrupts a flow. Set up a long running task to go, building out a spec and come back to find 3 minutes in it chucked that error. AGAIN.
Do better amazon, you're literally hosting the models!
Now just gotta sell the Model X!
Maybe this is a personal thing, but one thing I *really* like in Cursor is the ability to start writing prompt while the agent works. If I have more than one agent tab/chat open, I sometimes am writing more than one prompt to different tasks. In Cursor, each agent tab has it's own input text box, so I can be writing them there and when I switch, so does the prompt. In Kiro, there is a shared/common input box, and switching between tabs just changes where it will go.
So since the last few updates, my claw was having spates of slowing right down, high cpu/ram, and eventually gateway restarts. Tried the latest update, no change. It would work great for periods of time though. Seen other posts on here just saying certain versions are broken.
I had it diagnose itself. Initially it pointed to the telegram integration (I run 3 bots so maybe more bots means more chance to crash?), but offered little.
Eventually, it did a deep dive and found it was occasionally getting ipv6 dns results for telegram. Since my stack isn’t ipv6 capable, it would fail, and this led to resource leaks.
> Night and day difference. The current PID (1843168) has been up for 5h 11m with:
> • 0 liveness warnings
> • 0 ERROR-level log entries
> • 0 restarts
> • 0 sendChatAction failures or stuck sessions
> Compared to the pattern before — crashing every few hours with 80-second event loop freezes, 52% CPU pinned, and ~9 crashes/day — it's running clean. CPU usage dropped from 52% to 4.4% too.
> The 10:46 restart happened because the previous session (my long reply to you) was the one that got stuck. It wasn't the IPv6 fix that caused it — that was the old process dying from the backlog the earlier crash created.
> Since the config took effect (10:46 restart), it's been rock solid. The fix is working.
—————
> Found it. The Telegram doc explicitly mentions this. On Node 22+, OpenClaw defaults to autoSelectFamily: true (tries IPv4 and IPv6 simultaneously), and dnsResultOrder defaults to ipv4first. The problem is autoSelectFamily: true means it attempts IPv6 connections — and when those fail with ENETUNREACH, it cascades into event loop chaos.
> I'll set both autoSelectFamily: false (forces IPv4 only) and dnsResultOrder: "ipv4first" (as a belt-and-suspenders)
Finally something to sell the 2017 Model X for! (PS, anyone want a model X?)
