4 ms·

Never heard about security txt files until now, but it makes a lot of sense! Regulations are a hit or miss (e.g the cookie notification rules have some good pa

Never heard about security txt files until now, but it makes a lot of sense! Regulations are a hit or miss (e.g the cookie notification rules have some good parts but I wonder if there isn't any room for improvement in the current "visiting a website for 10 seconds and clicking whatever the big button is so that I see the content in interested in" status quo. This one is not obtrusive, easy to implement (though only developers care about this part) and solves the problem.

b33j0r 3y ago
Heard of it, but I’m still wondering why every RFC looks like it’s from 1998. We work with structured data all the time. Then I remembered the armistice between yaml and toml and how I’m still confused about why the python community was torn asunder. (lol. One looked like python to devs on mac/linux, and one looked like python to windows users who used INI a lot. Only a true scotsman uses plaintext, HTTP-style)
- chrismorgan 3y ago
  There’s a lot of history involved, and a difference between authoring and publication formats. It’s only comparatively recently (2016–2019, can’t remember exactly and can’t be bothered looking it up) that they stopped having the canonical form of the published document being monospace plain text with fixed pagination. Now, it’s markup, and so it can readily be presented in quite different ways. Observe this security.txt RFC 9116 formatted in two different ways: https://datatracker.ietf.org/doc/html/rfc9116 https://datatracker.ietf.org/doc/html/rfc9116 https://www.rfc-editor.org/rfc/rfc9116.html https://www.rfc-editor.org/rfc/rfc9116.html
eru 3y ago
The government making rules for its own subdivisions is different from those other regulations that constrain what private third parties can do. The linked article explicitly mentions that they _hope_ private companies will adopt this standard; but there's no mention of any regulatory requirement on them.
midasuni 3y ago
Don’t set a cookie and you don’t need a cookie banner. Websites choose to display that banner, they don’t have to.

b33j0r 3y ago

Heard of it, but I’m still wondering why every RFC looks like it’s from 1998. We work with structured data all the time. Then I remembered the armistice between yaml and toml and how I’m still confused about why the python community was torn asunder. (lol. One looked like python to devs on mac/linux, and one looked like python to windows users who used INI a lot. Only a true scotsman uses plaintext, HTTP-style)

chrismorgan 3y ago
There’s a lot of history involved, and a difference between authoring and publication formats. It’s only comparatively recently (2016–2019, can’t remember exactly and can’t be bothered looking it up) that they stopped having the canonical form of the published document being monospace plain text with fixed pagination. Now, it’s markup, and so it can readily be presented in quite different ways. Observe this security.txt RFC 9116 formatted in two different ways: https://datatracker.ietf.org/doc/html/rfc9116 https://datatracker.ietf.org/doc/html/rfc9116 https://www.rfc-editor.org/rfc/rfc9116.html https://www.rfc-editor.org/rfc/rfc9116.html

eru 3y ago

The government making rules for its own subdivisions is different from those other regulations that constrain what private third parties can do. The linked article explicitly mentions that they _hope_ private companies will adopt this standard; but there's no mention of any regulatory requirement on them.

midasuni 3y ago

Don’t set a cookie and you don’t need a cookie banner. Websites choose to display that banner, they don’t have to.