Remove Premiere and Connect references? #24

Closed
opened 2025-12-21 15:39:20 +01:00 by backuprepo · 6 comments
Owner

Originally created by @anthonylavado on GitHub (Dec 11, 2018).

In various spots, there are references to Premiere and Connect. Some of these were just links for more info (see #32 where I changed some of these).

We should look at how we can effectively “remove” these entries/links from the UI, so users don’t encounter them.

I imagine the underlying code can be left as is for now (if there’s no way to call it, is it really there?). That way if we opt to rebuild connect somehow, we have somewhere to start from.

Originally created by @anthonylavado on GitHub (Dec 11, 2018). In various spots, there are references to Premiere and Connect. Some of these were just links for more info (see #32 where I changed some of these). We should look at how we can effectively “remove” these entries/links from the UI, so users don’t encounter them. I imagine the underlying code can be left as is for now (if there’s no way to call it, is it really there?). That way if we opt to rebuild connect somehow, we have somewhere to start from.
backuprepo 2025-12-21 15:39:20 +01:00
Author
Owner

@JustAMan commented on GitHub (Dec 11, 2018):

I vote for complete removal. I can not imagine the need for re-implementing Connect if we never plan to do paid features... and I rather we do not. Paid support is fine, though, if someone asks.

@JustAMan commented on GitHub (Dec 11, 2018): I vote for complete removal. I can not imagine the need for re-implementing Connect if we never plan to do paid features... and I rather we do not. Paid support is fine, though, if someone asks.
Author
Owner

@ajdunevent commented on GitHub (Dec 11, 2018):

I have a lifetime Emby Premiere subscription which I got at the beginning of 2016 when the project was, as far as I knew, fully open source and, I think, before the nag screens and moving of important features to paid only (offtopic: imagine how irritated I am about their license bait-and-switch). Though I have no right to weigh in on this topic as I'm not even remotely a developer, I also vote for complete removal. If something like Premiere is left in, it should only unlock at most very minor, optional features (like a "Thanks for your support" badge and, I don't know, maybe an alternative color theme). And, most importantly, the developers should be willing to accept without grief that their open source project might be forked to allow those very minor, optional features without payment.

@ajdunevent commented on GitHub (Dec 11, 2018): I have a lifetime Emby Premiere subscription which I got at the beginning of 2016 when the project was, as far as I knew, fully open source and, I think, before the nag screens and moving of important features to paid only (offtopic: imagine how irritated I am about their license bait-and-switch). Though I have no right to weigh in on this topic as I'm not even remotely a developer, I also vote for complete removal. If something like Premiere is left in, it should only unlock at most very minor, optional features (like a "Thanks for your support" badge and, I don't know, maybe an alternative color theme). And, most importantly, the developers should be willing to accept without grief that their open source project might be forked to allow those very minor, optional features without payment.
Author
Owner

@joshuaboniface commented on GitHub (Dec 11, 2018):

@JustAMan I firmly said as much on Reddit, so definitely - let's just strip it all out.

I already hid the badge on the Admin Dashboard page.

@joshuaboniface commented on GitHub (Dec 11, 2018): @JustAMan I firmly said as much on Reddit, so definitely - let's just strip it all out. I already hid the badge on the Admin Dashboard page.
Author
Owner

@napcae commented on GitHub (Jan 10, 2019):

Information: This issue is being worked on in PR 412. Referencing here so this issues gets closed when the PR gets merged.

@napcae commented on GitHub (Jan 10, 2019): Information: This issue is being worked on in [PR 412](https://github.com/jellyfin/jellyfin/pull/412). Referencing here so this issues gets closed when the PR gets merged.
Author
Owner

@JustAMan commented on GitHub (Jan 23, 2019):

Should be fixed by #412

@JustAMan commented on GitHub (Jan 23, 2019): Should be fixed by #412
Author
Owner

@anthonylavado commented on GitHub (Jan 23, 2019):

I can agree on this. Closing.

@anthonylavado commented on GitHub (Jan 23, 2019): I can agree on this. Closing.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#24
No description provided.