Allow providers to be off-by-default in the web UI #93

New issue

Closed

opened 2026-01-11 10:02:53 +00:00 by ian · 0 comments

ian commented

2026-01-11 10:02:53 +00:00

Owner

Request by S50U.

Currently, whether a spot/alert provider is enabled or not is a config-file decision made by the server owner. If a provider is disabled, it cannot be used. If it is enabled, then it is providing data to Spothole. There is a separate toggle for the web UI, controllable by the user, that sets whether they want to see that data on the page. This always defaults to enabled.

The main Spothole server disables the RBN provider as it's a lot of data that most users won't want. However, this setup means that users can't get it from Spothole at all.

The request is for Spothole to have a setup where a spot provider is enabled, but when the web UI is loaded for the first time, the default state is for that provider to be turned off on the UI side.

That way, the RBN data would still be in the system, and while a user wouldn't see it on the web UI by default, they could then opt-in to seeing it.

Request by S50U. Currently, whether a spot/alert provider is enabled or not is a config-file decision made by the server owner. If a provider is disabled, it cannot be used. If it is enabled, then it is providing data to Spothole. There is a separate toggle for the web UI, controllable by the user, that sets whether they want to see that data on the page. This always defaults to enabled. The main Spothole server disables the RBN provider as it's a lot of data that most users won't want. However, this setup means that users can't get it from Spothole at all. The request is for Spothole to have a setup where a spot provider is enabled, but when the web UI is loaded for the first time, the default state is for that provider to be turned off on the UI side. That way, the RBN data would still be in the system, and while a user wouldn't see it on the web UI by default, they could then opt-in to seeing it.