No more or less than sending age information or registering an ID does. In all cases they must track content classification at some granularity (individual resource, single page, subdomain, some other scheme) and act on that information. The only thing that varies is how they act.
Yes, when it's client-sent they can hide classified parts of the page. When it's server-sent you either mark the whole website 18+ or you hide 18+ content for everyone.
You're just making things up. There's no technical reason a header based solution can't be granular. It could also specify alternative resources similar to how multiple image resolutions are handled today. It all depends on what is standardized.
Right now the only one I'm aware of is RTA which theoretically applies on a per-request basis although I expect that approximately all present usage is uniform site wide.
No more or less than sending age information or registering an ID does. In all cases they must track content classification at some granularity (individual resource, single page, subdomain, some other scheme) and act on that information. The only thing that varies is how they act.
Yes, when it's client-sent they can hide classified parts of the page. When it's server-sent you either mark the whole website 18+ or you hide 18+ content for everyone.
You're just making things up. There's no technical reason a header based solution can't be granular. It could also specify alternative resources similar to how multiple image resolutions are handled today. It all depends on what is standardized.
Right now the only one I'm aware of is RTA which theoretically applies on a per-request basis although I expect that approximately all present usage is uniform site wide.
3 replies →