JupiterBroadcasting / JupiterBroadcasting/jupiter.tube
Jupiter.tube - Show-specidic channels, PC20 initiatives
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I think the shows need their own channels on jupiter.tube...
JB wants to generate their own RSS feeds in order to enable Podcasting 2.0 (PC20) features. If I understand correctly, PeerTube will (eventually?) become the source of the RSS feed data for live streams (LIT tag) so that they can be made available to PC20 apps for streaming. Since each show is subscribed to individually, I think it will be a lot easier to automate adding the Live (LIT) tag during a live stream to each show's RSS feed if the live streaming is done in it's own show channel on jupiter.tube. I know Alecks Gates (@agates) is doing a lot of work to bring PC20 features to PeerTube.
If JB continues to populate jupiter.tube with shows, perhaps even uploading the "finished" versions (maybe with a fancy audio meter video like has been done for the YouTube releases), then it will be a lot nicer for listeners, when coming to the site, to hone in on the episodes they are interested in if they were kept in their own channels. @coder-radio, @self-hosted, @office-hours, @extras, etc... Nice and tidy. This would especially make sense if jupiter.tube generated all the RSS feeds.
I do think that there should be a channel for JB network-wide or special event live streams that are not necessarily specific to one show. Maybe the @jblive channel could become that. I do not think it would be a good "all shows" channel name. Maybe a separate @all-shows channel if that's something that is desired.
Just my 2bits. Thanks for your time and consideration.
Contributor guide
No contributing guide indexed for this repository
Research direction
No repository files or tests are identified. Start by reviewing the PeerTube channel setup for jupiter.tube and the proposed Podcasting 2.0 RSS and live-stream requirements. Done means the required show and network-wide channels, feed behavior, and implementation scope are agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100