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

Please stop trying to shill this. The crypto aspect always made the project look shady, and the massive security oversights really hammer home the fact that this is not a serious project.

AI growth is unlikely to be linear. We have seen a lot of hype in the last 12-18 month that give us ideas like "tokenmaxxing". But this is the same cycle that we have been before: hype -> disillusionment -> someone figures out a better way to use it -> next hype phase starts.

As it stands, even the people closest to this technology have barely figured out how to use it effectively.


Sometimes it's just Hype -> disillusionment, and then no one ever figures out a better way and it's dead technology.

Not saying that applies to AI, but it certainly applies sometimes.


I can hear the landfill full of those 3D glasses for home TVs shout in agreement

Plus all the blockchains.

It's really hard to bring everything there on my Segway, which is of course the only type of vehicle on the roads anymore.

AI has historically had a habit of disappearing for ten years and coming back once memories fade and the new story sounds enough different from the old one.

I don’t think this era is going to end with us all unemployed, but I do plan to be retired before the next cycle.


If you move fast enough, they can't find the vulnerabilities in your system before you deploy the next version.


Crypto was originally born during the Great Financial Crisis. It's not surprising that the idea of: "Hey, wouldn't it be neat if we didn't need any of that," seemed attractive back then, even though that is obviously far too simplistic a view of what the financial system actually does.

But the end result is that crypto currencies never really delivered on their promise, because they barely work in practice, and the only reason to engage with them is for gambling or crime. Anything else is just too slow, too expensive, too cumbersome, too error-prone, and just generally far too inconvenient. What's the point of a digital currency that is best stored on an air-gapped device that must never connect to any network?


Bitcoin was launched in 2008 way before the Dodd Frank act was passed


The Bitcoin genesis block literally contains the message:

> The Times 03/Jan/2009 Chancellor on brink of second bailout for banks

I would've thought the implication was kind of obvious? And I'm not sure why you mention Dodd-Frank -- there were many bailouts throughout 2007-2010 and the point of Dodd-Frank was to put an end to that scheme.


Whenever people talk about why you should host in the EU, this is just the most recent example for why should shouldn't.



US ISP ignore blocking orders and that was never challenged.


Host in Switzerland, that's where Quad9 operates from.


Switzerland is not in the EU, thankfully. And it seems to be one of the few places left in Europe where privacy is taken somewhat seriously.


Indeed. If it were just a question of Swiss law, we'd be in excellent shape. The problem is that France and Switzerland are both signatories to the Lugano Convention, while the US is not. As long as the Quad9 Foundation has to have a legal domicile somewhere, there will always be some lever that can be used against it. Switzerland was the best place, but does not offer perfect protection.


Switzerland has its own DNS blocklist that all ISPs obey. [1]

Quad9 doesn't obey it but I never understood how they can get away with that legally. I'd be interested in an explanation if someone knows more!

1. https://www.gespa.ch/en/fighting-illegal-gambling/access-blo...


Quad9 is not a telecommunications service provider as defined by Swiss law, which is where that application becomes enforced. Details of this (and many other things) can be found on the "Compliance and Applicable Law" section of the website. https://quad9.net/privacy/compliance-and-applicable-law/


Sounds like they get away with it legally because the law applies to ISPs and they’re not an ISP.

From your link:

> Internet service providers in Switzerland are obliged to take measures to prevent access to these domains (DNS blocking).


I suppose that's it.

It still feels a little strange that that loophole is allowed: everyone who has a Swiss ISP could switch to Quad9 and be strictly better off. But if everyone does that, then the DNS ban is completely ineffectual. Maybe I should let sleeping dogs lie.


I have a feeling the fact that people have to opt in to using Quad9 does a lot to help them in this case vs an ISP where all of their users are using the ISP’s DNS by default. But yeah it does seem like a “letter of the law vs spirit of the law thing”.


I opened the blocklist expecting some juicy Linux ISO sites and... it's all betting sites. I'm not even mad.


That's because the Swiss DNS blocking originated in an anti-unregulated-gambling law. Basically all unregulated gambling websites are blocked. There shouldn't be any other sites on that list.


I'm a little mad because it's the principle of the thing.

In practice the only site I occasionally want to check that's blocked is Polymarket. I don't trade on there myself, but I find it useful to check the odds of certain events.


I don't personally care about betting sites but it's the legal precedent and principle that the government can add anything to such a list and make obligatory.

"First they came for the shady weird-ass online gambling sites...."


Also, hosting location is kind of a deception for real ways to protect data, like E2EE, which work no matter the country.


Nuclear is to solar in terms of energy generation what hydrogen is to electric for cars: it's proponents keep arguing that the other thing doesn't work and will never work, and that you absolutely, positively need their approach. And then it just works and effectively kills off the other technology within a couple of years. Nuclear is basically already dead, and anyone starting new nuclear projects now will look extremely silly in 20-30 years when they finally come online.


They might not look silly because they will have material from which to make nuclear weapons, which is the principal reason we have nuclear power at all.


That is how you end up with a test suite that now takes 10x as long, unless you occasionally prompt the agent to consolidate and group tests.

There are still a lot of issues with coding that require intervention. Just recently, I had Astra detect a minor bug in an HTTP client that resulted in it deciding that the best approach would be to spend 1800 LOC on implementing its own from scratch. Some other time, Opus 5.5 was trying to tell me that test runs on a small to mid-sized application would take another three weeks until they would be fully finished.


The only time I really get tests which take crazy time is when I'm doing mobile dev, because emulator testing on my system is slow.


They are probably like 3-6 months away from just letting their agents work directly on prod after realising that repos don't scale enough.


If you need a reason, the modem and the baseband firmware have several unpatched vulnerabilities on that model, which is not something that an Android update can resolve.


Is there an easy way to tell if there are unpatched vulnerabilities in my phone's modem and baseband?


Based on the amount of modem CVEs posted in the monthly Android security bulletins, I think it's safe to assume that if you are no longer getting updates then there are unpatched vulnerabilities in them.


Based on the artificial delays Google introduces into the Android patching process, on the general crappiness of mobile firmware and the sleaziness of major mobile chipset vendors, I think it's safe to assume that even if you are supposedly getting updates, there are unpatched zero-day vulnerabilities in them. Usually under ongoing attack, at least by professional phone cracking software vendors and secret services.


>Based on the artificial delays Google introduces into the Android patching process, on the general crappiness of mobile firmware and the sleaziness of major mobile chipset vendors, I think it's safe to assume that even if you are supposedly getting updates, there are unpatched zero-day vulnerabilities in them.

Maybe if you include third party android OEMs like samsung, but google pixels are as up to date as you can get.


Pixels running GrapheneOS sure, but stock Pixels lag months behind patches that exist but not yet shipped. Check any bulletin and it links to git commits to months ago.


>Check any bulletin and it links to git commits to months ago.

Is there any evidence that the git commits weren't in the ROMs from months ago? The monthly ASB corresponds to when the bugs are publicly disclosed, not when they made it into ROMs.


Pixels only ship a tiny subset of the security preview patches early. Samsung ships a subset for their flagship devices too and it's likely larger than Pixels. Samsung lists these patches in their bulletins and you can retroactively figure out which were future Android Security Bulletin patches. Go through the vulnerabilities for September 2026 or October 2026 and search for them in Samsung's bulletin.

The only way to get the full set of security preview patches is through GrapheneOS. It's strange Google doesn't ship more for the Pixel OS but that's the way it is right now. It takes them around 4 weeks to make a release and even longer when including the time for adding changes to it so there's a long delay built into the process. They should fix it but are clearly not prioritizing it without media pressure that's not happening. They do a lot better than other OEMs but that's much different from doing a good job.


Android Security Bulletins don't list the vast majority of firmware, driver, HAL and especially Linux kernel vulnerabilities. Those list a large subset of the High and Critical severity Android Open Source Project (AOSP) vulnerabilities backported to older releases along with a tiny portion of non-AOSP vulnerabilities. AOSP vulnerabilities below High and Critical severity aren't backported so those aren't listed. Non-AOSP vulnerabilities for Pixels are covered in the Pixel Update Bulletins with many of those being vulnerabilities in components used by other devices. Each OEM is supposed to make their own equivalent to the Pixel Update Bulletins, but they aren't required to provide those updates to claim the latest patch level.


In a practical sense, what are the consequences of that? If you're careful about not installing random shit on your phone?


It has remotely exploitable vulnerabilities in the firmware, Linux kernel, kernel drivers, userspace drivers and HALs. Those don't require installing anything on your device to exploit. There are publicly available proof of concept exploits for a bunch of these vulnerabilities.


Assuming it gives ACE, could you not use the exploit to runtime patch the firmware to fix it?

Anyway, obvious clear reason why firmware signature gating should be illegal.


Well, it might be worth it reversing firmwares now with UART pins connected. A lot has changed in (agentic) reverse engineering.

BRB gonna try this out on my old Fairphone


OpenSSH don't have the same luxury of being able to ignore potential vulnerabilities.


Curl doesn't ignore vulnerabilities


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

Search: