matteska
Re:Reverse-Engineering the LCD Display Interface of the Nest 2nd Gen T...
on Friday September 26, 2025 @02:15AM (#45383283)
Pre-ordered! Thanks for the reverse engineering work!
Re:Alphabet selling Google Domains assets to Squarespace
on Thursday June 15, 2023 @10:00PM (#36350012)
Does this sale include Google Cloud's "Cloud Domains" feature? https://cloud.google.com/domains/docs
Re:Google is discontinuing Inbox
on Wednesday September 12, 2018 @03:47PM (#17972473)
When Google shutdown their RSS Reader, Feedly lived...
What’s the Inbox successor going to be?
Verizon 2018 Data Breach Investigations Report [pdf]
Tracking Users with CSS
Ex-Synack Engineers Raise $3M for Security Startup (YC S17)
The Best Way to Deploy Content Security Policy Headers
Re:Launch HN: Templarbit (YC S17) – Protect Your Web Apps from XSS Att...
on Tuesday July 25, 2017 @06:24PM (#14852404)
This is awesome! Let me know if I can help you getting started.
Re:Launch HN: Templarbit (YC S17) – Protect Your Web Apps from XSS Att...
on Monday July 24, 2017 @06:07PM (#14843177)
Thank you for your feedback! More resources and education material for developers will be coming very soon.
The default policy we provide is report-only. When we started we provided a very strict policy, but it broke too many apps. It was a major turn down for a lot of adopters. We are constantly evolving and are currently working on a feature that automatically generates tailored (stricter) policies depending on the reports we receive.
Re:Launch HN: Templarbit (YC S17) – Protect Your Web Apps from XSS Att...
on Monday July 24, 2017 @05:34PM (#14842926)
No domain verification is required at this point. Content-Security-Policies are ideally delivered through the HTTP response headers and then enforced by the browser. We are working on making the integration as easy and smooth as possible.
Re:Launch HN: Templarbit (YC S17) – Protect Your Web Apps from XSS Att...
on Monday July 24, 2017 @05:20PM (#14842802)
Thanks for finding this one. Just fixed it.