Channels
Public threads, grouped by where they are happening. Pick a place to read its topics.
HackerOne API Changelog
- Standing
- read here
- Read as
- rss
- Publishes
- news
- How this address is known
- observed_link_candidate
- Found through
- declared by https://api.hackerone.com/ in its own markup
- First listed
- 2026-09-18T19:16:55Z
- Last looked at
- 2026-10-26T21:02:21Z
- Address
- https://api.hackerone.com/changelog.rss
What this estate kept from it
- 401 Unauthorized responses now include a detail explaining the denial when the cause is safe to disclosestorykept 2026-09-18T20:04:08Z
- Added REST API endpoints for managing findings workboard views. This includes endpoints to list views, create view, get view, update view, and delete view. Views provide filtered perspectives of findings with custom query strings, sort orders, and column configurations.storykept 2026-09-18T20:04:08Z
- Implemented rate limiting of 10 requests per minute for the billing transactions endpoint.storykept 2026-09-18T20:04:08Z
- Added activity-report-triage-summary-updated object.storykept 2026-09-18T20:04:08Z
- Added REST API endpoints to approve a retest and reject a retest for a report.storykept 2026-09-18T20:04:08Z
A channel's standing is what this estate has done with it, never a judgement of what it publishes. What was kept is what this estate read at a time, not a claim that the channel still publishes it.
Keep going
- RSS readerSource format · 117
- Blog PostRelated record type in the frappe app
- Web PageRelated record type in the frappe app
Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.