Synch Meeting Agenda

[bedeho]

• multiple resolutions: if we can at least get playback to work, then infra can plug in... conditional on not becoming redundant or in conflict with fuutre adaptive streaming.

• how are we dealing with category mapping? I believe it should be static, and creator should provide input in signup flow, but I don't know where we stand. This would also be a good place for a creator to discover that they may be trying to get into a service which does not match their content, it's not so clear how Gleev for example will signal this otherwise, perhaps a separate screen is needed about this regardless?

• Continuation of prior point. Does Gleev need some more custom messaging to make sure its clear what its about? e.g. Updating YPP page?

• Continuation of prior point. Should this be configurable so that Vintio and others can change?

• What is status of YPP being configruable as on or off in Atlas instance?

• How will we policy wise deal with people signing up, say with a cooking channel, even if we add all the messaging described? Obviously tehy should not receie a payout, but how will they learn about why they are not a fit?

• It's very unclear for me how YPP should work outside of Gleev+Vinteo: YPP has distinct parts

  1. who pays (until council does) and what are terms?: operationally it seems complex for us to start paying for all sorts of other gateways, so probably not?
  2. what creator backend to use: if there are distinct backends, different gateways may end up onboarding same creator, but perhaps this is totally fine, as council in the end probably will not reward duplicates?
  3. what synching infra to use: these could all be totally distinct.

[dmtrjsg]

Sharing my perspective ahead of the meeting.

1️⃣ Multiple resolutions

Strictly Technical question, tbc

2️⃣ Categories mapping

Channel categories

We don't have this concept at the moment, but YT does. So fetching their category during OB flow, and flagging to their attention that Gleev is a Web3/ Crypto focussed App, and irrelevant videos will be moderated out by the content curation team should work.

In terms of marketing there's no harm in positioning Gleev as a place for curated quality topical content.

⚠️ I am not sure how this can be made scalable maintaining the quality without some sort of ops involvement into manual approval of channels, based on YT content of new creators or similar.

Video uploads

I think a static list which creators map their videos to is devised by us based on this list would be a good start:

Categories: Investing Podcasts Conferences Reviews Tutorials News Memes Interviews Analysis Predictions Trading

ℹ️ Youtube categories list>

Film & Animation Music Autos & Vehicles Travel & Events Pets & Animals Sports People & Blogs Gaming Comedy Entertainment How-To & Style News & Politics Nonprofits & Activism Education Science & Technology

3️⃣ Specific Content Vertical Messaging

Certainly, on the Marketing website, YPP landing page and OB flow (with "acknowledging" that this app for Web3 creators only, Channel creating Flow) @dmtrjsg to raise an issue on GH

4️⃣ Custom Vertical Focus Messaging

Good idea, the only place configurable would be the creator OB flow, as everything else is specific to Gleev and should be optional when building the app.

5️⃣ Is YPP configurable/ optional?

@kdembler is best to confirm.

6️⃣ YPP Ops for Gleev

1. Only for single gateway for now as a form of piloting the programme, DAO can pick up after pilot is complete for the verticals of their choice.
2. Onboarding flow may be chosen to be different, and the compensation scheme as well. Multiple Backends are fine in this case in my very humble opinion.
3. Technical question @zeeshanakram3 and @kdembler is best to comment.

[dmtrjsg]

Resolutions after the meeting

1️⃣ At launch YT synch service would pull in 1080 default. If not available, then 720.

Multiple resolutions

Will be added later, perhaps right after launch.

• https://github.com/Joystream/atlas/issues/3317

Implementation will not be too hard as you can just fetch multiple and add them to channel bag with diff meta. Doable at reasonable cost. Some metadata complications for QN, and design work will be reqd for Atlas team.

Does it conflict with Adaptive streaming? There’s no reason to assume there is a conflict, it requires quite some extra work. Will be added to post-mainnet scope separately

• https://github.com/Joystream/atlas/issues/3318

2️⃣ CATEGORIES

1. YT sync scraps the YT category, and lets creator select a single category. Inform users that this will be propagated to all videos, but can be changed manually.
2. What they select is default display category for the video category.

Covered in

• https://github.com/Joystream/marketing/issues/292

3️⃣ . Custom messaging for Gleev on Sign up flows for creators and viewers landing page. Dima and Adam will figure out all the entry points and messaging that needs to be designed to inform users on what value prop does it have.

• https://github.com/Joystream/marketing/issues/292

4️⃣ YPP flow AND Gleev content vertical messaging needs to be optional to set up/configurable.

• https://github.com/Joystream/atlas/issues/3319
• https://github.com/Joystream/atlas/issues/3323

5️⃣ We are hiding the YPP, but not splitting the code base.

• https://github.com/Joystream/atlas/issues/3299

6️⃣ We will re-enforce the message that content category is important to adhere to in YPP landing page, Onboarding flow and YPP Dashboard. This messaging will need to be re-factored so its customisable.

• https://github.com/Joystream/marketing/issues/292

7️⃣ YPP Ops

1. Gateway operators pay for their YPP Programme
   • https://github.com/Joystream/joystream/issues/4337
2. Distinct Backends and separate Auth flow
3. Separate Sync Infra