I
@soller but all this should be voluntary and for the client to decide.
If the client sends a certain content restriction, then the server may opt to avoid sending such content. On the other hand, if the server sends a certain content type, the client can opt to not show it.
It should be illegal to send a wrong content type though. That is, if you don't want to care about the content types of your website, then just don't annotate, but don't claim that it's suitable for all audiences.
@soller arguably, there should be an HTTP standard where the client can send its age-restriction preferences, and the server can send the age restriction of its contents.
Or, since age restriction differs culturally, a semantic description of content type may be more useful. Such as "3-1 implied sexuality; 1-5 graphic violence".
Even as an adult that would be nice, because it reduces the "child walks in issue", and I don't want to see certain content either.
@promovicz @Lilith ach so, oh mein Gott.
@promovicz @Lilith Moment, seit wann hat Hetzner was mit der AfD zu tun?
