[PR #682] [MERGED] Anonymous view #941

New issue

Closed

opened 2026-02-25 20:37:10 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 20:37:10 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/benbusby/whoogle-search/pull/682
Author: @benbusby
Created: 3/14/2022
Status: ✅ Merged
Merged: 4/13/2022
Merged by: @benbusby

Base: main ← Head: feature/anonymous-view

📝 Commits (7)

7b8a852 Expand /window endpoint to behave like a proxy
02b9cab Add front end for enabling anonymous view
2abfbc3 Merge remote-tracking branch 'origin/main' into feature/anonymous-view
e7b70dd Implement filtering of remote content from css
efd505f Condense NoJS feature into Anonymous View
fcd51fe Exclude 'data:' urls from filter, add translations
b52f596 Add cssutils to requirements

📊 Changes

11 files changed (+255 additions, -55 deletions)

View changed files

📝 app/filter.py (+70 -10)
📝 app/models/config.py (+4 -1)
📝 app/routes.py (+57 -9)
📝 app/static/css/dark-theme.css (+5 -0)
📝 app/static/css/light-theme.css (+5 -0)
📝 app/static/settings/translations.json (+68 -34)
📝 app/templates/index.html (+4 -0)
📝 app/utils/misc.py (+12 -0)
📝 app/utils/results.py (+27 -1)
📝 app/utils/search.py (+2 -0)
📝 requirements.txt (+1 -0)

📄 Description

The current /window endpoint is used as a proxy currently, but only
for removing Javascript from the result page. This expands the existing
functionality to allow users to proxy search result pages through their
Whoogle instance.

Note that this feature will likely be merged in without being 100%
finished, since I'm unsure of how users intend to use the feature. With
some community testing, I'll get a better idea of A) how many people are
actually going to use this feature, and B) what aspects of the feature
are useful or not useful.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/benbusby/whoogle-search/pull/682 **Author:** [@benbusby](https://github.com/benbusby) **Created:** 3/14/2022 **Status:** ✅ Merged **Merged:** 4/13/2022 **Merged by:** [@benbusby](https://github.com/benbusby) **Base:** `main` ← **Head:** `feature/anonymous-view` --- ### 📝 Commits (7) - [`7b8a852`](https://github.com/benbusby/whoogle-search/commit/7b8a8525d594027157bdab429d00a7ece1633915) Expand `/window` endpoint to behave like a proxy - [`02b9cab`](https://github.com/benbusby/whoogle-search/commit/02b9cabe907e8b452c040531e254e15a34a8ec58) Add front end for enabling anonymous view - [`2abfbc3`](https://github.com/benbusby/whoogle-search/commit/2abfbc310fecb5563e65289c3cbeb70d94e92504) Merge remote-tracking branch 'origin/main' into feature/anonymous-view - [`e7b70dd`](https://github.com/benbusby/whoogle-search/commit/e7b70dd34da012cc94b1972a5a72de6e52b4f79a) Implement filtering of remote content from css - [`efd505f`](https://github.com/benbusby/whoogle-search/commit/efd505f1921b6831954698853e8b35b28c88f49f) Condense NoJS feature into Anonymous View - [`fcd51fe`](https://github.com/benbusby/whoogle-search/commit/fcd51fe73a9de2ad0adf0d12a9f5597125011967) Exclude 'data:' urls from filter, add translations - [`b52f596`](https://github.com/benbusby/whoogle-search/commit/b52f5967cba0a79133e8ff9ba6f1cc2e58312897) Add cssutils to requirements ### 📊 Changes **11 files changed** (+255 additions, -55 deletions) <details> <summary>View changed files</summary> 📝 `app/filter.py` (+70 -10) 📝 `app/models/config.py` (+4 -1) 📝 `app/routes.py` (+57 -9) 📝 `app/static/css/dark-theme.css` (+5 -0) 📝 `app/static/css/light-theme.css` (+5 -0) 📝 `app/static/settings/translations.json` (+68 -34) 📝 `app/templates/index.html` (+4 -0) 📝 `app/utils/misc.py` (+12 -0) 📝 `app/utils/results.py` (+27 -1) 📝 `app/utils/search.py` (+2 -0) 📝 `requirements.txt` (+1 -0) </details> ### 📄 Description The current `/window` endpoint is used as a proxy currently, but only for removing Javascript from the result page. This expands the existing functionality to allow users to proxy search result pages through their Whoogle instance. Note that this feature will likely be merged in without being 100% finished, since I'm unsure of how users intend to use the feature. With some community testing, I'll get a better idea of A) how many people are actually going to use this feature, and B) what aspects of the feature are useful or not useful. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>