Comments URL: https://news.ycombinator.com/item?id=49439078

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=49133120

Points: 2

# Comments: 1

The accessibility tree already solves this. Labels, roles, states, actions, input formats, validation feedback, it's all there. A screen reader user and an AI agent need the exact same information. If your site works for one, it works for the other.

If you find something an agent can't do through the accessibility layer, you've found something a disabled person's assistive technology can't do either. So fix accessibility. Don't build a parallel system.

I filed an issue on the W3C WebMCP repo asking for a concrete use case that (1) can't be handled by the accessibility tree, (2) isn't better served by a backend API, and (3) wouldn't also benefit assistive technology if added to the accessibility layer.

Curious if anyone can produce one.

Comments URL: https://news.ycombinator.com/item?id=47026761

Points: 3

# Comments: 1

For the copyright thing, I understand that there's legit ongoing debate around all this AI-assisted coding and copyrightability.

In this case of zpdf, while Claude Code did a lot of the heavy lifting on implementation, there was a real effort in architecture decisions, iterative prompting/refinement, debugging, testing, benchmarking.

My intent is zero restrictions: use it, fork it, sell it, whatever. WTFPL captures that spirit perfectly for me. It's as permissive as legally possible while being upfront about not caring.

The goal is just to make a useful tool freely available.

Edit: I have changed it to CC0.

ΑΛΕΞΑΝΔΡΟΣ ΤΡΙΑΝΤΑΦΥΛΛΙΔΗΣ Καθηγητής Τμήματος Βιολογίας, ΑΠΘ

     ΝΙΚΟΛΕΤΑ ΚΑΡΑΪΣΚΟΥ
     Επίκουρη Καθηγήτρια Τμήματος Βιολογίας, ΑΠΘ

     ΚΩΝΣΤΑΝΤΙΝΟΣ ΓΚΑΓΚΑΒΟΥΖΗΣ
     Μεταδιδάκτορας Τμήματος Βιολογίας, ΑΠΘ





     Γονιδιώματα
     Δομή, Λειτουργία και Εφαρμογές

I'll try my best to make it a really good one!

also, added python bindings.