-
Notifications
You must be signed in to change notification settings - Fork 14
Discussion: Swarm<>YouTube #182
Comments
Yes |
I generally would support to switch, but the Swarm implementation is still somewhat limited as we currently only have 1 encoding. The Etherna team is working on getting multiple version up and better support for different network conditions. Until that time, I think it's better to keep YT as the default |
It's perhaps worth highlighting #183 right now, which would resolve the issue with lack of renditions/encodings :) |
Definitely something on our rader. Do you have more info about how Livepeer's solution work? Either way, I think it would be ideal if this could get integrated as part of a DIP |
This was raised as a DIP here: https://forum.devcon.org/t/devcon-archive-optimise-video-streaming-from-decentralised-storage/2359 |
Cool. Would you be up to add additional information, implementation details, resources, etc. |
I think in this case we do not need a DIP as it is a pure (IMHO uncontentious) software issue and we can just do it via issues/PRs. But I would also be most interested in answers to the questions. |
Not sure I agree. For this specific issue (making Swarm the default player) you’re right. It should be an easy switch. Although there’s more to it than just flipping a bit, imo.
The Swarm/Etherna option in it’s current state is not sufficient enough in UX, due to available/performance. It only contains an 720p encoding. I know Etherna was working on getting multiple added. I’ll follow up with them for an update. This was all part of their DIP.
The other linked issue from Chris would add a completely new option using Livepeer’ CDN and Arweave. While this sounds interesting, I’d rather see a similar route as Swarm/Etherna and someone leading such a proposal and efforts.
…On Fri, Dec 9, 2022 at 08:30, ligi ***@***.***> wrote:
I think in this case we do not need a DIP as it is a pure (IMHO uncontentious) software issue.
—
Reply to this email directly, [view it on GitHub](#182 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AGGFNQH6QBTUD3AF3Q75VYLWMMX6TANCNFSM6AAAAAASOFUL4A).
You are receiving this because you commented.Message ID: ***@***.***>
|
yes - that's why I prefixed it discussion - to discuss what needs to be done before switching it around - sure there is work to be done before.
let's maybe do it inline and summon @costgallo
sure - I see chris as leading the effort here. Still not sure if for pure software enhancements we need a DIP - but if you want it I will not stay in the way. |
It seems we agree on someone leading these efforts. The reason I‘m bringing up DIPs, is that it structures the way we discuss/accept these kind of improvements. It makes the process open and fair for others to interact. DIP proposals usually include more details which are useful starting point for discussion. I do agree that (for software changes) it would be easier to handle it all via issues/PRs. Not switching back/forth between GitHub and forum. In that case, I do feel we should document and ‘formalize’ that process a bit. Some idea/feature request templates could solve this already. Will connect separately on how such a template might look like. Something else to keep in mind is that if we have IPFS, Swarm and Livepeer/Arweave as a video player option, I don’t think it’s fair anymore to select any as the default player. |
Hi, Mirko from Etherna here. |
Currently YouTube is the default and swarm is the second (fallback) option.
Should we turn this around?
The text was updated successfully, but these errors were encountered: