Call center services in india

Durable Object alarm loop: $34k in 8 days, zero users, no platform warning 9 by thewillmoss | 0 comments on Hacker News. Sharing this as a warning to anyone using Cloudflare Durable Objects with alarms. Root cause: My DO agent's onStart() handler called this.ctx.storage.setAlarm() on every wake-up without checking whether an alarm was already scheduled. Combined with 60+ preview Worker deployments each creating independent DO instances, this created a runaway self-health-check loop. Timeline: - April 3: loop began (zero DO usage before this date) - April 4-5: peaked at ~930 billion row reads/day - April 11: found it, fixed it - April 15: $34,895 invoice due with no billing response yet The fix: // Before (dangerous) async onStart() { await this.ctx.storage.setAlarm(Date.now() + 60_000) } // After (safe) async onStart() { const existing = await this.ctx.storage.getAlarm() if (!existing) { await this.ctx.storage.setAlarm(Date.now() + 60_000) } } Other things worth doing: - Strip D...

Ask HN: Is Claude Getting Worse? 5 by sahli | 10 comments on Hacker News. It feels like most Claude Code users have already noticed a quality drop in the Claude models. As a Claude Pro subscriber (Web version; I don't use Claude Code), I’ve seen a clear decline over the last couple of weeks. I can’t complete tasks in a single turn anymore. Claude often stops streaming because it hits some internal tool-call/turn limit, so I have to keep pressing “Continue.” Each continuation has to re-feed context, which quickly burns through tokens and quota. The model also makes more mistakes and fails to fully complete tasks it used to handle reliably. This is especially frustrating because Sonnet 4.6 was a real step up: it could produce long, correct code in one pass much more often. That seems basically gone now. As a paying Pro user, I honestly find myself using free alternatives like DeepSeek and Z.ai (GLM) more than Claude lately. I’ve also stopped touching Opus entirely—it’s so token-hu...

Any engineers here with experience of clinical data standards? 2 by kalturnbull | 0 comments on Hacker News. I'm building an open-source initiative for a personal health record app. I used to work on a national platform for NHS Scotland, so this is a subject I'm passionate about. I'm hoping to chat to engineers with experience of openEHR or FHIR. For context: https://plotline.care

Is anyone actually using OpenClaw? 32 by misterchocolat | 32 comments on Hacker News. I don't use it personally, and neither does anyone in my circle...even though I feel like I'm super plugged into the ai world

Ask HN: My ISP is telling my neighbors their slow internet is because of me 2 by skarz | 2 comments on Hacker News. I have about 54TB of Internet Archive torrent backups on my home servers. I am on an unlimited gig plan with Mediacom and typically upload about 10 terabytes a month. I have been doing this for over a year and have never once gotten any sort of notification or complaint from Mediacom. Note: I live in a gated community and my daughter confirmed he was wearing a Mediacom shirt and drove a Mediacom truck. My neighbor (see below) confirmed a Mediacom tech rep was at her house per her support ticket. Well, today I came home and my underage daughter told me the internet wasn't working and also said someone from Mediacom came to the house and was asking questions about our internet usage and what I do for a living and stuff like that. He asked her if she had been downloading stuff. He said he was in the area investigating network congestion and that he identified the prob...

GitHub gave webhook secrets away in webhook call 3 by time4tea | 0 comments on Hacker News. Couldn't see this on a Web page... From an email: We're writing to let you know that between September 2025 and January 2026, webhook secrets for webhooks you are responsible for were inadvertently included in an HTTP header on webhook deliveries. This means that any system receiving webhook payloads during this window could have logged the webhook secret from the request headers. Webhook deliveries are encrypted in transit via TLS, so the header containing the secret was only accessible to the receiving endpoint in a base64-encoded format. We have no evidence to suggest your secrets were intercepted. This issue was fixed on January 26, 2026. Please read on for more information. User privacy and security are essential for maintaining trust, and we want to remain as transparent as possible about events like these. GitHub itself did not experience a compromise or data breach as a result...