Figured this would be something SocialHub would be interested in!
We had a little discussion about what went into, and what you can expect from Owncast’s first step into federation.
1 Like
feature request https://joinpeertube.org 
E.g. https://conf.tube
I’m afraid I don’t follow. What feature are you requesting? PeerTube isn’t a feature, it’s another piece of software.
If you’re talking about Owncast federating with PeerTube, that was originally in the cards, but when I went to do the work I found PeerTube was using an implementation of http-signature that was incompatible with federating with Owncast, so it had to be postponed. They’ve since upgraded, but PeerTube is still not being compatible.
PeerTube was not designed to follow non-PeerTube instances, and it’s going to be a never-ending fight to make it work, I’m afraid.
Is this something you want because you have a use case for it, or you just think it should exist?
1 Like
That would be a real pity and missed opportunity. Did you reach out to PeerTube project with these issues?
It’s in the schedule for eventual resolving, so hopefully it can be worked out.
I did reach out to them to resolve the first issue, but when further issues happened I realized it needs to be pushed off, as I can’t be spending all my time troubleshooting somebody else’s software.
I know it sounds harsh, and that I should be a better member of the community, but there’s only so many hours in the day and I’m trying to do things that help Owncast users directly first, and everything else comes second.
Of course if anybody wants to join me to just focus on just inter-service federation issues, I’d love to have you! But I’m the only one working on this, so I have to pick my battles.
2 Likes
To be honest, I do not understand the federation part because:
Video says, it will only support postive actions.
Loving that but:
If another piece of software in the fediverse sends an Owncast Actor an ActivityPub Activity,
how should it know, what it can send you ?
The conformance in ActivityPub means to support “the entirety”, otherwise all people loose content and fediverse makes less sense.
See https://www.w3.org/TR/activitypub/#conformance
ActivityPub conformant Client
This designation applies to any implementation of the entirety of the client portion of the client to server protocol.
ActivityPub conformant Server
This designation applies to any implementation of the entirety of the server portion of the client to server protocol.
ActivityPub conformant Federated Server
This designation applies to any implementation of the entirety of the federation protocols.
It should at least fall under one of these 3.
E.g. redaktor will support 1 and 2, wait for help and maybe support 3 …
I’m not interested in turning Owncast into another microblogging platform with polls and conversation threads.
You can say Owncast is “wrong” for not supporting these things, but these are not features that make any sense, whatsoever, to the project. Saying that every project that wants to utilize ActivityPub must support 100% of the features of the entirety of the Fediverse makes no sense.
If you want to converse with people install Pleroma, if you want to run a live stream install Owncast.