In content views we add repos that the hosts that subscribe to that content view will get. So this should decide what subscriptions the host will consume. Yet, we explicitly allocate subscriptions in activation keys. Any idea why this is so? https://showbox.bio/ https://tutuapp.uno/ https://vidmate.cool/
Since we are manually assigning subscriptions to an activation key , can it be possible that we can marry a content view with incompatible repos to an activation key.
A collaborative learning environment, enabling open source skill development.