Conversation

Notices

1. Embed this notice
   william.maggos (wjmaggos@liberal.city)'s status on Tuesday, 28-May-2024 09:53:47 JST william.maggos

   We need a default #peertube server, right?

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 28-May-2024 09:53:44 JST silverpill

     in reply to

     • 3dcandy
     • err head :pc2black: 🏴‍☠️ ✂️

     @errhead @wjmaggos @3dcandy

     Do content consumers actually need a PeerTube account?
     I think there might be other ways to alleviate instance choice anxiety

   • Embed this notice
     3dcandy (3dcandy@mastodon.social)'s status on Tuesday, 28-May-2024 09:53:45 JST 3dcandy

     in reply to

     @wjmaggos why?

   • Embed this notice
     err head :pc2black: 🏴‍☠️ ✂️ (errhead@podcastindex.social)'s status on Tuesday, 28-May-2024 09:53:45 JST err head :pc2black: 🏴‍☠️ ✂️

     in reply to

     • 3dcandy

     @3dcandy @wjmaggos

     >why?

     Because the biggest hurdle for new users is instance choice anxiety

     Because small instances frequently go down ruining the experience for users.

     Because ~90% of users are content consumers, not creators, and don't benefit particularly from the decentralized part of the infrastructure

     Because now with the export/import support viewers can easily migrate off the default instance when they decide to become creators or migrate to a particular instance.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 28-May-2024 18:58:08 JST silverpill

     in reply to

     • 3dcandy
     • err head :pc2black: 🏴‍☠️ ✂️

     @errhead @wjmaggos @3dcandy

     I think you're right, other solutions require dev work, but centralization caused by default instances is usually irreversible, they tend to grow bigger over time (and more generally in federations, big instances are getting bigger - email, matrix and mastodon are good examples)

     An ideal protocol should work like RSS. There, the cost of participation for content consumers is almost zero. One just needs a client. The cost of participation for content producers is low (one can use any static site generator), and they enjoy all the benefits of decentralized infrastructure.

     How we can get to that point with ActivityPub? Some ideas:

     - More efficient servers. Instance setup should be as simple as creating a static website with an RSS feed
     - Read-only accounts. These users can participate as content consumers, but the cost for instance operators is much lower because they don't require moderation.
     - Universal UIs. People shouldn't be forced to create accounts on different federated services.
     - Pulling from outbox. Instance blocks punish content consumers for no reason, and this can be fixed by switching to pull model in some situations.

   • Embed this notice
     err head :pc2black: 🏴‍☠️ ✂️ (errhead@podcastindex.social)'s status on Tuesday, 28-May-2024 18:58:09 JST err head :pc2black: 🏴‍☠️ ✂️

     in reply to

     • 3dcandy
     • silverpill

     @silverpill @wjmaggos @3dcandy

     Some do, some don't

     almost all want a simple address they can go to to experience PeerTube and joinpeertube is much more user hostile than they are looking for in a default site.

     >I think there might be other ways to alleviate instance choice anxiety

     Me too, but they are on the dev side and not available yet. Until that point the ops side should be doing what it can.