• 4 Posts
  • 189 Comments
Joined 4 months ago
cake
Cake day: August 29th, 2025

help-circle





  • Oh sorry, I mean, I think we should ban algorithmic feeds (by which I mean anything non-trivial – they usually have “latest unreads” etc. which is fine by me.). Possibly also systems which are both (a) not dedicated to a single topic, and (b) connect at least hundreds of thousands of people, and © have some built-in mechanism to facilitate forwarding content from others to other people directly adjacent to you on the graph (retweeting/reblogging/etc.).

    SMS, IRC, BBS, online chat – these all predate what are known as social media and they fit all my desiderata. No non-trivial algorithmic feed, and segregated into generally smaller communities.

    Bluesky, twitter (latest-from-friends), Mastodon – I am skeptical of these, even if they have no non-trivial algorithmic feeds. While individuals will typically have less than ten thousand “friends”/“following” per se, the friend graph still forms a network which comprises millions of people. Of course, traditional systems like email are similar, so this would probably be okay if not for reblogging/retweeting/etc., which is basically a human-powered recommender system.

    Twitter (under normal usage), Facebook, Instagram, TikTok, tumblr – hard no, these fit none of the desiderata, and I think they’re clearly “social media” and also clearly harmful.

    YouTube and Reddit I think are acceptable if we ban the non-trivial feeds (i.e. restrict to subscriptions-only, no recommender systems, no “best”, “hot”, etc.)










  • Well, that same problem exists with many of the proposed verification models, like credit cards (how can you verify this is my credit card?) , photo ID, etc.

    Here’s my proposal: your browser can send a request to a verification body (could be the government directly, let’s say) to respond to the challenge from the website you’re accessing, without sending information about which website is asking for the challenge. The verifier sends a cryptographically-signed approval back. The browser forwards this to the website. To prevent comparisons of timing as a deanonymization method, the browser can wait a random period of time before forwarding the request both ways.






  • None of these are good arguments against introducing a ban. Worst argument of all is that “we shouldn’t ban it for 15 year olds because that wouldn’t protect 16 year olds.” Seriously? Is that intentional rage bait?

    I think it’s more than clear by now that algorithmic feeds are hazardous, at least without significant effort in research and safeguards which nobody seems to be doing. So yeah, I’d say: definitely ban algorithmic feeds for teenagers. Hell, ban them for everyone if you must.

    Gating should be done either by ZKP (zero-knowledge proofs, which don’t expose any information to any party other than “I’m at least x years old” – look this up if this is a new concept to you) or device-side by standardizing and streamlining child safety locks.