Clean default whitelist

[JackNUMBER]

Is your feature request related to a problem? Please describe.
This might be confusing when a part of the displayed bridge by default are not working when you install the project for the first time. Especially when some are famous website (Instagram, OpenClassroom, ...), it can be expected that these bridge are the most most working ones.

Describe the solution you'd like
Use working and well maintained bridges.
Increase visibility of active bridges even if it's small websites, RSS-Bidges' users needs are greater than GAFAM visibility.

Additional comments
A track to find used/active bridge can be the amount of commits and issues during past months.
This update can be done several times a year to show the project is active and follow contributors activity.

[em92]

Especially when some are famous website (Instagram, OpenClassroom, ...), it can be expected that these bridge are the most most working ones.

Describe the solution you'd like
Use working and well maintained bridges.

I will tell about maintaining problems in general.

At the moment there is no maintainer InstagramBridge and FacebookBridge. Previous maintainers of InstagramBridge were pauder (probably his twitter, https://github.com/pauder returns 404), @pmaziere and @teromene. They gave up finally. I don't blame them, pretty sure they spent their free time and for free. But enthusiasm is limited. The same about free time.

The same thing about FacebookBridge. Mentioned people also maintained it (excluding pauder and including @logmanoriginal).

What to do here finally? I would suggest to find someone who will maintain those bridges for money. Users of those bridges could donate maintainer (In general Facebook could pay its employees for making RSS feed on their own site, but it does not care). I am fine, if we could add something like "Donate" button on the bridge card, but in general donation scheme must be discussed before implementing.

[JackNUMBER]

I perfectly get the point, I maintain some bridges and they are not completely working at this moment 😅. There is no attempt to blame anyone here. I tried to take the issue by the other side: expose popular bridges could be a good way to make RSS-Bridge shines or get some new contributors. The default whitelist is an important step when you discover RSS-Bridge, that is why I propose an update.

The donation is a good idea!

[em92]

Started discussion about donation. #2063

[dvikan]

I very much agree that the default whitelist should contain only working bridges. Give nice user experience for first-timers.

[logmanoriginal]

The whitelist is meant to highlight some of the most frequently used bridges, so that novice users don't get overwhelmed when they enter the site for the first time (or offended by some of the options...). It is nearly impossible to guarantee fully functional bridges as sites are changing at a rapid pace (hence the lack of enthusiasm when you have walked the walk hundreds of times).

It probably makes sense to have a test suite for whitelisted bridges. That way broken bridges are caught early on and can be addressed before a release. Still, this doesn't mean that a bridge gets fixed. It is much more likely that it is going to be kicked from the whitelist...

[Bockiii]

@logmanoriginal Testsuite is in an "almost done" state and will be continued when the main "issue and pr cleanup action" is done. See here

I want to move this to a repo owned by rss-bridge organization and definitely rework the storage, probably work with a .db file that gets updated instead of the .csv file. But the main chunk of work is done.

[dvikan]

the whitelist is been modified since this issue.

the default list is now:

enabled_bridges[] = Youtube
enabled_bridges[] = Twitter
enabled_bridges[] = Telegram
enabled_bridges[] = Reddit
enabled_bridges[] = Filter
enabled_bridges[] = Vk
enabled_bridges[] = FeedMerge
enabled_bridges[] = Twitch
enabled_bridges[] = ThePirateBay