v3 is coming out soon

[A Former User]

@girish Live streaming was odd. It was unable to reach the server. Seems like it needed port 1935 and thats where my issue was? I think I'll try forking the cloudron app repo and try seeing if theres anything I can do there to properly expose that port? I imagine it was a firewall issue.

EDIT: It also broke federation though they commited a few changes since that seem to address it. So perhaps its better to wait until an RC2 to start re-packaging it or just for a full 3.0.0 release.

[A Former User]

@girish Would you be ok with me pushing a branch with the v3 WIP package? It just needs a few changes as far as I can tell. I'd need access. I can just fork it and make my changes there if thats easier.

[girish]

@atrilahiji You should have access now. Thanks!

[A Former User]

@girish Thanks! Pushed a branch and testing now.

[A Former User]

Ok so the delay is incredibly large (up to a minute off) and there is no chat. Testing this against OwnCast. You know, I really would like Peertube to be the place for my livestreams but if theres 0 interaction I don't think it will work for me.

[plusone-nick]

@atrilahiji Chat is for sure needed to succeed in the long run and 1 min delay is way too much - i think i saw that owncast has a 8-10 second delay - recently found this one on reddit - says "sub-second latency" https://www.ovenmediaengine.com/

[imc67]

Peertube 3.0.0 was just released!!!!

https://github.com/Chocobozzz/PeerTube/releases/tag/v3.0.0

[A Former User]

@imc67 Got it!

@girish MR for you when you have a sec: https://git.cloudron.io/cloudron/peertube-app/-/merge_requests/1

[A Former User]

Looks like its merged. Just waiting on the release. I imagine they're quite busy though

I the mean time I suppose yall could pull down the repo and update manually. Seems to work well.

[girish]

@atrilahiji The tests need fixing, @nebulon is fixing them.

[A Former User]

@girish Oh whoops! Hah didn't realize the tests were broken :^)

[nebulon]

Alright, tests succeed now and I have published a new package.

I just noticed now that from the merge request the version is actually a major package version upgrade, so you have to manually update this from the dashboard.