Hacker News new | past | comments | ask | show | jobs | submit login

Whether a service is centralized or decentralized might matter a lot to us here, but to 99% of people it's utterly irrelevant. An implementation detail.

Therefore their mental model will equate Youtube (a service) with Peertube (an application used by multiple services). If illegal content is on some Peertube, it's "on Peertube" and it drags down all the other stuff that is "on Peertube". Just like how big advertisers withdraw all their campaigns from all of Youtube when a single popular Youtuber posts a particularly distasteful video. They don't recognize the substructure inside Youtube's community because, to the public majority, Youtube is a monolithic thing. It's going to be the same for Peertube. (Unless Peertube has a better marketing department than behemoths like Youtube, which it likely has not.)




The solution to that then is to not pretend like PeerTube is centralized by hijacking the name for your URL. If you're hosting an instance, give it a unique name. If MyCoolVideos.com is a peertube instance with a bunch of child porn, then MyCoolVideos.com is going to get labeled as a bad site, and no one will know or care if the underlying technology is PeerTube.

This is a problem with federated services in general. People always seem to want to register on the "official" instance, when really there is none. I think there should be a solution to help people make the decision, or better yet not force them to make a decision at all. Maybe some OpenID-type login/account system should be used instead of having to make an account on a single instance. Or simply stop trying to market the underlying tech, like Mastodon or PeerTube, since that's not going to make a difference to the end-user and will just confuse them.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: