Customized Piped Instance capability added

[Klos54]

Is there an existing issue for this?

• I have searched the existing issues

Pain

Currently, our application or platform offers a limited selection of pre-configured Piped instances for our users. This limitation can be frustrating for many users who are looking for greater customization of their experience. They feel restricted in their choice and sometimes forced to use an instance that doesn't quite match their needs. This can lead to a less satisfying user experience, and even drive some users to seek alternatives.

Suggested solution

To solve this problem, I propose adding the ability for users to add their own customized Piped instance from the application settings. This feature would offer increased customization, allowing users to choose the Piped instance that best suits their needs, based on their specific preferences or requirements. It would also provide essential flexibility, enabling users to switch easily between different Piped instances without having to modify the application's source code. This scalability would deliver a better user experience, giving users greater control over their Piped environment.

Useful resources

No response

Additional information

No response

[mab122]

This maybe related to #542 which suggests using some 3rd party hosted instance of piped. I think the app itself shouldn't have any hardcoded instances, that would also reduce sudden loads on random instances after an update/release.

It would be also nice to add invidious support which was previously suggested in: #293

I will try to find time and work on this.

[KRTirtho]

I think the app itself shouldn't have any hardcoded instances,

It isn't hard coded. The list is fetched from piped's GitHub Wiki where they regularly add/remove/update instances officially

[Scorpoon]

+1 for custom piped instances. I have my own, privately hosted instance at home which I can reach via my always on VPN.