Hacker Newsnew | past | comments | ask | show | jobs | submit | esskay's commentslogin

I've heard this story before...in fact I've heard it several times, and funnily enough each time it involved GoDaddy. Stop. Using. Them.

I was just wondering if this might be the first incident. Are there any other public stories available?

I'd love for someone who's part of the USB-IF to try and explain what the heck they were thinking with their naming conventions. They're indefensibly awful in every way.


CaniRun's not a great tool - look how long its been since it's been updated. It's not got any of the qwen3.6 models on the list nor the new kimi one. In fact it's missing many of the "popular" models.


Care to back that up? We know they don't encrypt metadata - that's not a secret. Message content however is E2EE - thankfully these things get audited: https://blog.cloudflare.com/key-transparency/


This doesn't prove WhatsApp is encrypted at all. It proves that a directory of public keys is being logged and audited. That's it.

The protocol existing or being referenced doesn't prove it's what the production client is doing. That requires verifying the client code and behaviour end-to-end, not just the key directory.


Got it, so you can't back it up at all. You just made something up with zero actual evidence and rolled with it.


there have been claims as part of a recent lawsuit, which also influences peoples thinking

see: https://news.ycombinator.com/item?id=47738339

https://xcancel.com/BowesChay/status/2042399259316588793 (replies)


The onus is not on us to prove that it's not E2E encrypted, but on Meta/WhatsApp to prove that it is. The only way they can do that is by open-sourcing the client application, and providing a method for anyone to verify that the binary on their device was built from those sources, without modification.

Anything else is just theater. Anyone who is worried that their communications could get them arrested or attacked cannot safely use something like WhatsApp. There is no way to trust that a third party's keys haven't been added to a conversation, or that the client isn't leaking message content through some other means.


> The onus is not on us to prove that it's not E2E encrypted

It is when someone posts as if they've got hard evidence it's not.


it show whataspp key transparency is currently disabled since `Verified: Mar 13, 2026, 15:37:48 UTC`. any idea about this?

https://radar.cloudflare.com/key-transparency


I personally didn't see it as an ad. But it's hard not to question it when you see the before and after: https://github.com/laravel/boost/pull/758/changes/589394c44a...

Thats going to make any LLM agent change from "cool, we can deploy this anywhere" to "it only works on this one specific paid service thats overkill and more expensive for basically everyone" - its deceptive more than anything.


Try opencode go using kimi - its more than enough for most usecases unless you try something really stupid that you shouldn't be getting openclaw to do directly, like coding.


Yeah UK's currently going through the biggest rollout of renewable energy ever, the pace is insanely high. Theres new rules to allow plug in solar coming into effect too with kits already available for renters and such.


They announced they're thinking about amending regulations to allow plug in solar at some point. Hopefully something eventually actually gets done.


They're more than thinking about it, it's already going ahead :) https://www.gov.uk/government/news/government-to-make-plug-i...

British Gas, Octopus, etc are all prepping kits right now, Ecoflow has already got a certified product line sitting in UK warehouses ready to go. We're talking within a couple of months and it'll be running.


It always make me both roll my eyes and smile a little when i see someone daft enough to think they need some obscene setup - you dont. You never have. You are not Amazon, Microsoft, Google, etc. If you get to the point where you need that kind of setup you're already employing a dev ops team thats telling you that.

Stick whatever you're working on onto a ~$5/mo cheapo vps from someone like Hetzner, Digitalocean, etc and just get on with building your thing.


It'd make it a pain to stop abuse of their online platform when it launches, which is financially problematic given gta 5 online made rockstar billions.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: