Using Peertube without peering

zauberberg · Juin 23, 2020, 1:37

Hi there,
I am from a small climate activist group called haccers against climate change.
We are currently using voctoweb as a platform for our recordings (https://hacc.media)
I stumbled upon peertube and it seems to solve some problems for us but some new ones would be opened.
We dond’t need and don’t want the peering, especially between the users of the platform.
Is there a way to use the service like any « old » one eg. no peering, just serving and receiving from one server/cdn?

I know it kind of defeats the purpose auf peertube, but we’re not that much into pering stuff and handling all the legal consequences

Mindiell · Juin 23, 2020, 4:00

I think it defeats also the purpose of « fighting against climate change » because peering is used to help reduce the weight on your server by sharing the video being watched across all viewers.

Maybe what you don’t want is the ActivityPub part (social networking and all that stuff) ?

zauberberg · Juin 23, 2020, 10:02

I don’t want to start a discussion about what is good or bad for the climate and I don’t want to start a discussion without real sources and scientific evidence.

Yes, I also want to disable the ActivityPub part, but additionally I don’t want the viewers to peer data between each other.

I think I found the option in the config file and I will try that out:

github.com

Chocobozzz/PeerTube/blob/develop/config/production.yaml.example#L139


    # 'nobody': Do not accept remote redundancies
    # 'anybody': Accept remote redundancies from anybody
    # 'followings': Accept redundancies from instance followings
    accept_from: 'anybody'


csp:
  enabled: false
  report_only: true # CSP directives are still being tested, so disable the report only mode at your own risk!
  report_uri:


tracker:
  # If you disable the tracker, you disable the P2P aspect of PeerTube
  enabled: true
  # Only handle requests on your videos.
  # If you set this to false it means you have a public tracker.
  # Then, it is possible that clients overload your instance with external torrents
  private: true
  # Reject peers that do a lot of announces (could improve privacy of TCP/UDP peers)
  reject_too_many_announces: false


history:

Thanks for any additional help an suggestions on this topic

Mindiell · Juin 24, 2020, 5:58

No problem, I was just trying to help about what you wanted or not (because lot of people don’t know exactly the differences between peering and ActivityPub and all those stuff ).

gerhardbeck · Novembre 15, 2020, 8:59

did it work? We need to switch off peering, too for data protection reasons (says my data protection officers)

rigelk · Novembre 15, 2020, 9:36

It should work as what you want is exactly what the config file comment says.