frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Type Server Protocol

https://github.com/microsoft/pylance-release/blob/main/docs/tsp/type-server-protocol.md
154•adamnemecek•3h ago•113 comments

Sebastian Raschka's from-scratch video course on building reasoning models

https://magazine.sebastianraschka.com/p/building-reasoning-models
485•sgiannopoulos•6h ago•72 comments

Working with academic communities to build scientific understanding

https://openai.com/index/building-scientific-understanding-with-academic-communities/
21•jonluca•19m ago•5 comments

CSS-Tricks has a new owner

https://css-tricks.com/css-tricks-has-a-new-owner/
319•edent•6h ago•71 comments

Oldest GUI application that still runs on Windows 11

https://blog.enlyth.com/posts/oldest-windows-gui-app-win-11/
187•enlyth•3h ago•108 comments

Nietzschian Debugger

https://github.com/DilawarShafiq/nietzschian-debugger
105•dilawargopang•4h ago•33 comments

GPT-6.1 Terra

https://openai.com/index/introducing-gpt-6-1-terra/
401•meetpateltech•3h ago•254 comments

Microsoft offers voluntary buyouts to a quarter of its workforce

https://www.kuow.org/technology/2026-10-26/microsoft-offers-voluntary-buyouts-to-a-quarter-of-its...
68•mooreds•50m ago•36 comments

A Man from the Future: Why Johnny Can't Stop Abstracting

http://muratbuffalo.blogspot.com/2026/10/the-man-from-future-why-johnny-cant.html
77•aray07•4h ago•39 comments

Anthropic S-1

https://www.sec.gov/Archives/edgar/data/2130357/000162828026067168/anthropicpbc-sx1.htm
1372•SiNTEx•8h ago•1348 comments

Sigma Says the Compact, Modular FP2 Is the Ultimate Hybrid Camera

https://petapixel.com/2026/10/22/sigma-says-the-compact-modular-fp2-is-the-ultimate-hybrid-camera/
33•thm•3d ago•28 comments

Show HN: Hob - Open-source, on device alternative to Claude Cowork and ChatGPT

https://github.com/FrigadeHQ/hob
55•pancomplex•5h ago•16 comments

SIMD-accelerated computer vision on a $2 microcontroller

https://shraiwi.com/blog/simd-fast-esp32s3/
148•zdw•23h ago•51 comments

Diamond Transistor

https://www.df.com/diamond-transistor
101•Gravityloss•3d ago•55 comments

CorridorKey 2.0

https://corridorkey.com/
5•ravenical•37m ago•0 comments

The EPA Is Quietly Killing Its Web Archive

https://www.motherjones.com/environment/2026/10/epa-online-archive-deletion-zeldin-camp-lejeune-t...
165•robtherobber•2h ago•27 comments

Microsoft offers mass buyouts for roughly a quarter of its workforce

https://www.seattletimes.com/business/microsoft/microsoft-offers-mass-buyouts-for-roughly-a-quart...
595•doctorzook•6h ago•506 comments

Blaise Pascal invented fixed route public transport (2024)

https://humantransit.org/2024/12/one-of-the-greatest-inventions-in-the-history-of-human-transport...
244•skadamat•4d ago•129 comments

Birdwatching rewires the brain and slows cognitive decline

https://www.bbc.com/future/article/20261019-birdwatching-rewires-the-brain-and-slows-cognitive-de...
479•cisc•2d ago•184 comments

Pharo 14

https://pharo.org/news/2026-10-26-Pharo14Release.html
219•xkriva11•10h ago•54 comments

In Leaked Audio, Flock CEO Tells Cops Backlash to the Company Isn't Real

https://www.404media.co/in-leaked-audio-flock-ceo-tells-cops-backlash-to-the-company-isnt-real/
202•Frieren•4h ago•109 comments

Native Prometheus Integration with Nginx

https://categorica.io/blog/2026.10.16_nginx-stats-prometheus/
9•foxhill•3d ago•0 comments

US designates helium as a critical material

https://apnews.com/article/energy-critical-materials-minerals-helium-43da160adc1bad389fba0b9ffbd1...
136•rbanffy•3h ago•66 comments

Magic state cultivation on a superconducting quantum processor

https://arxiv.org/abs/2512.13908
4•kheal•2h ago•0 comments

Show HN: Glider 4.0 Unofficial Web Edition (Mac game port)

https://dbohdan.github.io/glider/
20•networked•22h ago•4 comments

Concerning behavior from a popular open-weight AI model

https://cohere.com/blog/concerning-behaviour-popular-open-weight-ai-model
219•matthieu_bl•5h ago•81 comments

Who killed the EV cert? A browser whodunit for Halloween

https://qwac.com/blog/who-killed-the-ev-cert
8•roddylindsay•3d ago•17 comments

World Wars I and II Military Aviation Museum Collection

https://www.militaryaviationmuseum.org/our-collection/
24•NaOH•3d ago•10 comments

Switzerland. Block by block. At 1:1 scale

https://blocks.manifold3d.ch/
442•theanonymousone•13h ago•211 comments

Fixing Tool-Call Accuracy in vLLM

https://www.ubicloud.com/blog/fixing-tool-call-accuracy-in-vllm
141•coffeemug•8h ago•64 comments
Open in hackernews

Who killed the EV cert? A browser whodunit for Halloween

https://qwac.com/blog/who-killed-the-ev-cert
8•roddylindsay•3d ago

Comments

aleclindz•3d ago
Spooky!
rdl•1h ago
I had no idea EU had mandated this from software developers/browser authors. I hope they can kindly go fuck themselves w.r.t. non-EU software not sold in EU (but merely available online for download by anyone).
9dev•26m ago
It’s so funny how Americans seem to assume it’s the natural order of things that the whole world has to comply with American regulation, but lo and behold if the EU dares to have laws of its own!
ameliaquining•10m ago
Do you have any reason to believe that your interlocutor is in favor of the U.S. government enforcing regulations beyond its borders?
mcc1ane•59m ago
https://scotthelme.co.uk/are-ev-certificates-worth-the-paper... https://www.troyhunt.com/extended-validation-certificates-ar...
mieko•52m ago
For nearly a decade, I've been occasionally tracking how many of the Cloudflare top-2K sites (earlier: Alexa) respond with an EV cert. And then also pull the SSL Labs score to see if there was any correlation.

If anyone is interested:

https://github.com/mieko/greenbar

I should probably chart out the changes throughout the years, but this was more of a curiosity hack.

sekinfo•19m ago
Great work, did a similar analysis recently but only for the top 50, and in fact none of the top 50 had an EV at the time of the survey.

I believe the only possible advantage of an EV is not a technical one, but rather an organizational one: it encourages the use of a single keypair on each server because Wildcard coverage is not allowed (although multi-domain is allowed). For what appear to be non-technical reasons, I have seen many entities copying their keypairs for Wildcard certs between servers, even between business critical on-prem backends and cheap shared hosting or budget VPS, or handing the keypair over to a contractor via email.

galadran•47m ago
Clarification: Browsers or other user-agents are not required to trust QWACs for use in TLS. We fought very hard for this.

However, there are obligations to display 2-QWACs if sites choose to use them. Their keys are not used to authenticate web domains or encrypt web traffic.

Disclosure: I was Mozilla's lead for this effort and also helped design 2-QWACs (for my sins).

roddylindsay•27m ago
2-QWACs are awesome! Thank you for your contributions!

Though I don't understand why they would atone for any sins. IMHO, you created the website identity infrastructure for the agentic web...

And yes, I hope I didn't imply that QWACs are trusted by default for TLS. 1-QWACs would have to come from an existing trusted CA to be recognized by the browser.

galadran•16m ago
Ah, the sins are more to do with the design of 2-QWACs.

All the design needed was for the browser to check the TLS cert and the QWAC cert covered the same domain name. Instead, folks at ETSI insisted very stubbornly on the signature from the QWAC over the cert used in TLS - which is an annoying complication for site operators - and provides little additional benefit.

I'd also like to see the EU encode more information in these certs. Knowing a company's address is not very useful (IMO), but a machine readable label that the site is regulated by $COUNTRY_NAME financial or medical regulator would be a much more useful signal.

Good luck in your endeavours!

roddylindsay•4m ago
Very interesting history, thank you for sharing. I had wondered about the design choices there.

Agree that the next step for 2-QWACs is additional corporate data (professional licensure like you mentioned, incorporation date) and eventually arbitrary claims vetted by a QTSP.

For an average human user, these additional claims are nearly useless since they're so buried in the browser UI...and even if they were more prominent, they wouldn't be of much benefit, as the EV history has shown.

But for an agent that knows to look out for these signals, extensible 2-QWACs will be extremely valuable.

michaelt•41m ago
> The Stripe we are all familiar was incorporated in Delaware, so there was not a collision. But both companies were described by a browser as “Stripe, Inc.”

As I recall, EV certificates also had the 'problem' that a lot of companies trade under names that aren't their full legal name, making the EV cert confusing. To use modern examples, twitter.com having an EV cert for "Space Exploration Technologies Corp", google.com having an EV cert for "Alphabet Inc" and suchlike.

sekinfo•32m ago
Question for HN regarding EV certs:

Have seen some entities request a large number of EV certs (more than 10, sometimes up to 40) for subdomains under a single domain. At the same time, they are requesting OV Wildcard certificates for the main domain, which have overlapping coverage with the EV certs. These entities do not have any regulatory requirements to use EV as far as I know.

Is there any point in doing this?

The overlap from the Wildcard would seem to nullify any theoretical advantage of the EV cert, given that both will be recognized as valid certs that can cover the subdomains. This in addition to the fact that browsers do not treat EV, OV and DV certs differently in any significant user-facing way since many years now.

Frequently these entities also use Let's Encrypt DV certs on some subdomains alongside their EV certs, so of course a CAA record cannot be used to limit emissions to the CA which emitted the EVs.

Can anyone think of a legitimate technical motivation to use EV certs alongside an overlapping Wildcard OV and various DVs?

orf•16m ago
anyone who has ever worked at a large non-technical company can tell you exactly where these requests came from
rgbrenner•13m ago
I remember when these rolled out.. it was just an obvious cash grab by cert vendors, trying to create a trust-badge in collusion with browsers.

Back then, cert vendors would try to sell you on "premium" certificates.. telling you that cheap ssl certificates weren't good enough, so you needed to pay for $100-300+/yr certificate, and you could show to your visitors by displaying silly trust seals like the "Thwarte Seal".. as if customers would know who the hell Thwarte is.

Then this EV seal was launched, displaying what was essentially a trust seal in the browser.. and these same vendors would charge $500+/yr for it.

I can't express how great it is that EV certs died.

ameliaquining•5m ago
The browser vendors, I think, were at least making a good-faith attempt to address a real security problem; it's not like they made any money from EV certificates. Even if it was inevitably going to be marketed somewhat predatorily, and ultimately didn't work out.
logartis•12m ago
Keeping identity separate from TLS makes a lot of sense to me!