[GH-ISSUE #179] [BUG] settings set by user stored globally #124

New issue

Closed

opened 2026-02-25 20:34:57 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 20:34:57 +03:00

Owner

Originally created by @ghost on GitHub (Jan 21, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/179

Describe the bug

settings applied by users are set/stored globally/persistently.

To Reproduce

Steps to reproduce the behavior:

user changes setting, clicks apply.
other user opens whoogle from different computer, browser, etc to find that setting applied by previous user has been set globally.

Deployment Method

manual build with run executable.

Version of Whoogle Search

latest from source.

Desktop (please complete the following information):

any device

Smartphone (please complete the following information):

any device.

Additional context
instance is public.
i've also noticed that this issue is not just affecting my instance, but other public instances as well.

mine: https://whoogle.himiko.cloud
other: https://whoogle.sdf.org

Originally created by @ghost on GitHub (Jan 21, 2021). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/179 **Describe the bug** settings applied by users are set/stored globally/persistently. **To Reproduce** Steps to reproduce the behavior: user changes setting, clicks apply. other user opens whoogle from different computer, browser, etc to find that setting applied by previous user has been set globally. **Deployment Method** manual build with run executable. **Version of Whoogle Search** latest from source. **Desktop (please complete the following information):** any device **Smartphone (please complete the following information):** any device. **Additional context** instance is public. i've also noticed that this issue is not just affecting my instance, but other public instances as well. mine: https://whoogle.himiko.cloud other: https://whoogle.sdf.org

kerem

2026-02-25 20:34:57 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:34:57 +03:00

Author

Owner

@benbusby commented on GitHub (Jan 22, 2021):

Yeah this is a bit of a known issue. The intent for Whoogle was to only ever have individual instances rather than shared public ones, since public instances are incredibly easy for Google to rate limit or block altogether. Eventually I caved and added cookie based configs, with a "base config" that is used if cookies are unable to be set for some reason or are being blocked. Obviously something about this is broken and needs fixing, but figured context would be helpful here for why this is happening in the first place.

@benbusby commented on GitHub (Jan 22, 2021): Yeah this is a bit of a known issue. The intent for Whoogle was to only ever have individual instances rather than shared public ones, since public instances are incredibly easy for Google to rate limit or block altogether. Eventually I caved and added cookie based configs, with a "base config" that is used if cookies are unable to be set for some reason or are being blocked. Obviously something about this is broken and needs fixing, but figured context would be helpful here for why this is happening in the first place.

kerem commented

2026-02-25 20:34:57 +03:00

Author

Owner

@ghost commented on GitHub (Jan 22, 2021):

i set the main config file to read only, i think it fixed it? not exactly sure. anyways, i love whoogle, and yeah i understand that it's not meant for public use.

thanks <3

Sent from my iPhone

On Jan 22, 2021, at 9:17 AM, Ben Busby notifications@github.com wrote:

Yeah this is a bit of a known issue. The intent for Whoogle was to only ever have individual instances rather than shared public ones, since public instances are incredibly easy for Google to rate limit or block altogether. Eventually I caved and added cookie based configs, with a "base config" that is used if cookies are unable to be set for some reason or are being blocked. Obviously something about this is broken and needs fixing, but figured context would be helpful here for why this is happening in the first place.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ghost commented on GitHub (Jan 22, 2021): i set the main config file to read only, i think it fixed it? not exactly sure. anyways, i love whoogle, and yeah i understand that it's not meant for public use. thanks <3 Sent from my iPhone > On Jan 22, 2021, at 9:17 AM, Ben Busby <notifications@github.com> wrote: > > > Yeah this is a bit of a known issue. The intent for Whoogle was to only ever have individual instances rather than shared public ones, since public instances are incredibly easy for Google to rate limit or block altogether. Eventually I caved and added cookie based configs, with a "base config" that is used if cookies are unable to be set for some reason or are being blocked. Obviously something about this is broken and needs fixing, but figured context would be helpful here for why this is happening in the first place. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or unsubscribe.

kerem commented

2026-02-25 20:34:57 +03:00

Author

Owner

@benbusby commented on GitHub (May 5, 2021):

I think this can be closed now with the merging of #295 actually. Public instances can now set their own config settings on the backend and disable client side config changes. Config settings for users who have cookies enabled can also set session specific settings that shouldn't cause any global config changes.

@benbusby commented on GitHub (May 5, 2021): I *think* this can be closed now with the merging of #295 actually. Public instances can now set their own config settings on the backend and disable client side config changes. Config settings for users who have cookies enabled can also set session specific settings that shouldn't cause any global config changes.