Hey, Kinlan. Here's what you do. Once a month, on the same day every month, publish a browser change update. List every known upcoming change, and your best und

Hey, Kinlan. Here's what you do. Once a month, on the same day every month, publish a browser change update. List every known upcoming change, and your best understanding of when it will happen. List every change that has already happened, and when it happened. Include dates for these changes in both Canary and Production releases. Publish this update to Hacker News on the same day (and ideally, the same time) each month. It will not take too long before every dev in the world will be eagerly awaiting your update. The key is consistency. If you publish this update 100% reliably (Neither snow nor rain nor heat nor gloom of night...), then it will become the go-to way of hearing about browser issues. Extra Credit - Get your friends at Mozilla, Microsoft, Apple, etc. to contribute to the update for their respective browsers. If there was one place where ALL browser updates were documented, you will change the world.