searxng/.git/searx/plugins/https_rules, branch master Unnamed repository; edit this file 'description' to name the repository. [drop] plugin HTTPS rewrite - rule base is to old (update is to big) 2021-04-22T09:47:16+00:00 Markus Heiser markus.heiser@darmarit.de 2021-04-21T13:23:32+00:00 247c46c6b0c6e7f4fbbc4642bf288c51dcf20a33 The usefulness of the _HTTPS rewrite_ plugin is questionable: - the 36 rule files have not been updated since 2015 [1] - actual there are 23760 rule files in the https-everywhere repo [2] For the first, we can remove this plugin. For a complete new implementation, it might be good to know that there is a project "https-everywhere : Privacy for Pythons" [3] related: https://github.com/return42/searx-next/issues/8 [1] https://github.com/return42/searx-next/tree/d187a1d/searx/plugins/https_rules [2] https://github.com/EFForg/https-everywhere/tree/master/src/chrome/content/rules [3] https://github.com/jayvdb/https-everywhere-py Signed-off-by: Markus Heiser <markus.heiser@darmarit.de> 
The usefulness of the _HTTPS rewrite_ plugin is questionable:

- the 36 rule files have not been updated since 2015 [1]
- actual there are 23760 rule files in the https-everywhere repo [2]

For the first, we can remove this plugin.  For a complete new implementation, it
might be good to know that there is a project "https-everywhere : Privacy for
Pythons" [3]

related:  https://github.com/return42/searx-next/issues/8

[1] https://github.com/return42/searx-next/tree/d187a1d/searx/plugins/https_rules
[2] https://github.com/EFForg/https-everywhere/tree/master/src/chrome/content/rules
[3] https://github.com/jayvdb/https-everywhere-py

Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
[mod] https rewrite pluginification 2015-04-12T22:30:12+00:00 Adam Tauber asciimoo@gmail.com 2015-04-12T22:30:12+00:00 d2a636f75d24953f5094ea97ab54a8a4353a65ff