There’s a lot of other terrible things about social media, but a specific material terrible thing that might be the subject of regulation is how addictive it is.
You don’t get to the usage per day that social media platforms have without at least a little addictiveness. It’s addictive! We regulate liquor and cocaine and casinos, why not regulate the addictive structure of social media?
I suggest an objective and direct avenue of regulation: make the services increase latency in server responses, by setting a minimum latency to UI loading animations (including initial page loads, infinite scroll loads, page swipes, skeletons and bouncy balls, etc).
- Lowering latency is proven to increase usage, increasing latency is proven to decrease usage. So it’s already known to work.
- It’s not censorship if you just slow down every response.
- Everyone agrees on what a UI loading animation is. It gets non-application multi-page websites, SPA-backed things, mobile apps, and so on.
- It’s like a two line implementation with respect to technical difficulty to implement, if they use any sane animation library.
- It can be applied to any social media provider without reference to the structural form of the provider, as long as they’re on the Internet, because everyone agrees what a loading animation is.
- It can be verified objectively with a timer and it can also be verified objectively by a third party. So you can’t do the Volkswagen bamboozling of the regulators because it’s much less annoying to do independent testing of UI transition latency than of car emissions.
- It’s not hard to do definitional wriggling about non-abusive or abusive content: it’s surprisingly difficult to do definitional wriggling to get out of being defined as social media itself.
- I think the most viable definitional wriggling is to pretend that things are multiplayer video games with low-latency requirements. But there are already existing pretty viable regulatory attacks on MMORPG addiction pioneered by East Asian countries.
- One hangup is differences between media forms of the services. There’s probably a material difference between video content and other content because video content is comparatively longer-running. But that difference can also be articulated pretty well and maybe you would have longer latencies for video content.
- Such a policy would be adjustable depending on how much less addictive potential folks want.
I recommend about 2.0 second minimum latencies, which seem to be noticeable and effective at reducing browsing to about 50 minutes a day in my case.
You could note that HTTP responses are even better defined, but you could do wibbly things with transitions to get around this. You could also do a mandated pre-load black screen with scary messages on it, like cigarette cartons, but this is harder to deal with infinite scrolls and other dark UI patterns.
I know I posted a dealio a bit back about how I do this personally for myself but after a few years of this I believe that there are surprisingly few material obstacles to just turning it into policy.