Accountability
Corrections and contact
Found a summary that misses context, a broken link, or a record attached to the wrong source? Report it in the public HackerLinks repository.
Report a correction
Open an issue with the HackerLinks page URL, the statement or link that needs attention, and the original source that supports the correction. General questions can use the same contact path. Please do not include private information.
Open a GitHub issueHow corrections are handled
Reports are checked against the linked Hacker News discussion or other original source. When a report is confirmed, the checked-in record is corrected so the next static build carries the change across the site. Original comments remain authoritative.
Measurement and privacy
Telegram subscription links attach a coarse source label so HackerLinks can distinguish direct Hacker News conversions from other site subscriptions. The site does not send the referring URL to Telegram and does not persist the label in browser storage. The bot reports aggregate conversion counts and does not expose subscriber identifiers in analytics output. HackerLinks also uses cookie-free Cloudflare Web Analytics for aggregate traffic and performance measurement. Read the privacy notice for the data, legal basis, retention, service providers, and visitor rights.
Sponsorships and affiliate links
HackerLinks currently has no paid placements, sponsorships, or affiliate commissions. Selection is not sold. If that policy changes, any paid or affiliate relationship will be disclosed next to the affected link and on this page.