beenull/farside
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
farside/services.json

468 lines
14 KiB
JSON
Raw Normal View History

Output available instances and fallback URL to redis Once a list of available URLs has been determined for a particular service, the list is written as "service -> [list of instances]" to a local redis connection. These can then be used in the greater routing logic to pick a random instance from the list, or use a fallback instance if none are determined to be available.
2021-10-22 23:15:40 +00:00
[
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
{
"type": "libreddit",
"test_url": "/r/popular",
Add auto update instances for libreddit (#80) * Change libreddit's fallback URL to official instance's URL * Add auto update instances for libreddit
2022-12-11 20:45:13 +00:00
"fallback": "https://libreddit.spike.codes",
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
"instances": [
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://bob.fr.to",
"https://discuss.whatever.social",
"https://l.opnxng.com",
[CI] Auto update instances
2023-01-19 00:12:52 +00:00
"https://lbr.frail.duckdns.org",
[CI] Auto update instances
2023-01-31 00:14:22 +00:00
"https://libreddit.albr.to",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://libreddit.bus-hit.me",
"https://libreddit.dcs0.hu",
[CI] Auto update instances
2023-01-19 00:12:52 +00:00
"https://libreddit.de",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://libreddit.drivet.xyz",
"https://libreddit.esmailelbob.xyz",
"https://libreddit.foss.wtf",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://libreddit.kavin.rocks",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://libreddit.kylrth.com",
"https://libreddit.mha.fi",
"https://libreddit.northboot.xyz",
"https://libreddit.oxymagnesium.com",
[CI] Auto update instances
2023-01-31 00:14:22 +00:00
"https://libreddit.privacy.com.de",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://libreddit.privacydev.net",
"https://libreddit.projectsegfau.lt",
"https://libreddit.pufe.org",
"https://libreddit.pussthecat.org",
"https://libreddit.spike.codes",
"https://libreddit.strongthany.cc",
"https://libreddit.tiekoetter.com",
"https://libreddit.totaldarkness.net",
"https://lr.artemislena.eu",
"https://lr.mint.lgbt",
"https://lr.odyssey346.dev",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://lr.riverside.rocks",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://lr.slipfox.xyz",
"https://lr.vern.cc",
[CI] Auto update instances
2023-01-31 00:14:22 +00:00
"https://r.ahwx.org",
"https://r.darklab.sh",
"https://rd.777.tf",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://rd.funami.tech",
"https://reddit.invak.id",
"https://reddit.leptons.xyz",
"https://reddit.rtrace.io",
"https://reddit.simo.sh",
"https://reddit.smnz.de",
[CI] Auto update instances
2023-01-31 00:14:22 +00:00
"https://reddit.thekitty.zone",
[CI] Auto update instances
2023-01-13 00:16:44 +00:00
"https://reddit.utsav2.dev",
[CI] Auto update instances
2023-02-01 00:15:13 +00:00
"https://safereddit.com",
"https://snoo.habedieeh.re"
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
]
},
Support teddit, piped, and simplytranslate - teddit (https://teddit.net/about) A free and open source alternative Reddit front-end focused on privacy. Inspired by the Nitter project. - Piped (https://github.com/TeamPiped/Piped) An alternative privacy-friendly YouTube frontend which is efficient by design. - SimplyTranslate (https://simple-web.org/projects/simplytranslate.html) We aim to provide fast and private translations to the user without wasting much overhead for extensive styling or JavaScript ___ Also adds SimplyTranslate to the github pipeline, since they provide a list of the service's public instances. Closes #4
2021-12-16 00:09:00 +00:00
{
"type": "teddit",
"test_url": "/r/popular",
"fallback": "https://teddit.net",
"instances": [
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://i.opnxng.com",
[CI] Auto update instances
2022-02-04 00:39:53 +00:00
"https://incogsnoo.com",
[CI] Auto update instances
2022-06-22 00:11:46 +00:00
"https://rdt.trom.tf",
[CI] Auto update instances
2022-02-04 00:39:53 +00:00
"https://reddit.lol",
Remove cloudflare filter from update workflow The cloudflare filter, when performed as part of the github action workflow, doesn't seem to work nearly as reliably when run on an actual machine. The farside server will instead run the un-cloudflare script whenever it pulls in new changes to services-full.json, which should be a much more reliable approach to filtering out cloudflare instances.
2022-08-04 19:16:58 +00:00
"https://snoo.ioens.is",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://td.vern.cc",
[CI] Auto update instances
2022-02-04 00:39:53 +00:00
"https://teddit.adminforge.de",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://teddit.artemislena.eu",
[CI] Auto update instances
2022-02-04 00:39:53 +00:00
"https://teddit.bus-hit.me",
Add cf filter to nightly build, update services The cloudflare filter has been added back into the nightly build. Now that the filtering method uses direct querying of the instance IP(s), it should be more reliable than the namespace lookup (and more accurate). services.json has been updated with the latest filtered results from services-full.json as well.
2023-01-04 17:03:03 +00:00
"https://teddit.encrypted-data.xyz",
[CI] Auto update instances
2022-03-30 00:08:47 +00:00
"https://teddit.froth.zone",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://teddit.ggc-project.de",
"https://teddit.hostux.net",
"https://teddit.manasiwibi.com",
"https://teddit.namazso.eu",
[CI] Auto update instances
2022-02-04 00:39:53 +00:00
"https://teddit.net",
Support teddit, piped, and simplytranslate - teddit (https://teddit.net/about) A free and open source alternative Reddit front-end focused on privacy. Inspired by the Nitter project. - Piped (https://github.com/TeamPiped/Piped) An alternative privacy-friendly YouTube frontend which is efficient by design. - SimplyTranslate (https://simple-web.org/projects/simplytranslate.html) We aim to provide fast and private translations to the user without wasting much overhead for extensive styling or JavaScript ___ Also adds SimplyTranslate to the github pipeline, since they provide a list of the service's public instances. Closes #4
2021-12-16 00:09:00 +00:00
"https://teddit.pussthecat.org",
[CI] Auto update instances
2022-02-04 00:39:53 +00:00
"https://teddit.sethforprivacy.com",
Remove cloudflare filter from update workflow The cloudflare filter, when performed as part of the github action workflow, doesn't seem to work nearly as reliably when run on an actual machine. The farside server will instead run the un-cloudflare script whenever it pulls in new changes to services-full.json, which should be a much more reliable approach to filtering out cloudflare instances.
2022-08-04 19:16:58 +00:00
"https://teddit.tinfoil-hat.net",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://teddit.tokhmi.xyz",
[CI] Auto update instances
2022-02-04 00:39:53 +00:00
"https://teddit.totaldarkness.net",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://teddit.zaggy.nl"
Support teddit, piped, and simplytranslate - teddit (https://teddit.net/about) A free and open source alternative Reddit front-end focused on privacy. Inspired by the Nitter project. - Piped (https://github.com/TeamPiped/Piped) An alternative privacy-friendly YouTube frontend which is efficient by design. - SimplyTranslate (https://simple-web.org/projects/simplytranslate.html) We aim to provide fast and private translations to the user without wasting much overhead for extensive styling or JavaScript ___ Also adds SimplyTranslate to the github pipeline, since they provide a list of the service's public instances. Closes #4
2021-12-16 00:09:00 +00:00
]
},
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
{
"type": "bibliogram",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"test_url": "/p/Ch2WRmiLMjj",
Manually clear out dead bibliogram instances Also removes bibliogram from the auto-updater Bibliogram is discontinued, and many instances are going offline as a result. This clears out the ones that have already been deactivated, but the better solution would probably be to stop supporting bibliogram.
2022-09-15 17:19:18 +00:00
"fallback": "https://bibliogram.1d4.us",
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
"instances": [
[CI] Auto update instances
2022-08-02 04:24:46 +00:00
"https://bibliogram.1d4.us",
"https://bibliogram.froth.zone",
"https://bibliogram.priv.pw",
Update `beparanoid.de` domains Moved to femboy.hu. Fixes #85
2023-01-19 17:21:05 +00:00
"https://ig.femboy.hu",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://ig.tokhmi.xyz"
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
]
},
{
"type": "invidious",
"test_url": "/watch?v=eBGIQ7ZuuiU",
"fallback": "https://invidious.snopyta.org",
Restore missing invidious instances The latest CI update removed all invidious instances. Need to update CI to skip applying an update for a particular service if there is an error when fetching.
2022-02-07 18:40:56 +00:00
"instances": [
[CI] Auto update instances
2022-05-04 00:09:08 +00:00
"https://inv.bp.projectsegfau.lt",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://inv.odyssey346.dev",
"https://inv.riverside.rocks",
[CI] Auto update instances
2022-07-03 00:11:53 +00:00
"https://inv.vern.cc",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://invidious.baczek.me",
"https://invidious.dhusch.de",
Add cf filter to nightly build, update services The cloudflare filter has been added back into the nightly build. Now that the filtering method uses direct querying of the instance IP(s), it should be more reliable than the namespace lookup (and more accurate). services.json has been updated with the latest filtered results from services-full.json as well.
2023-01-04 17:03:03 +00:00
"https://invidious.drivet.xyz",
[CI] Auto update instances
2022-03-05 00:07:52 +00:00
"https://invidious.esmailelbob.xyz",
[CI] Auto update instances
2022-02-09 00:43:04 +00:00
"https://invidious.flokinet.to",
Add cf filter to nightly build, update services The cloudflare filter has been added back into the nightly build. Now that the filtering method uses direct querying of the instance IP(s), it should be more reliable than the namespace lookup (and more accurate). services.json has been updated with the latest filtered results from services-full.json as well.
2023-01-04 17:03:03 +00:00
"https://invidious.lidarshield.cloud",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://invidious.namazso.eu",
[CI] Auto update instances
2022-07-02 00:10:41 +00:00
"https://invidious.nerdvpn.de",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://invidious.privacydev.net",
[CI] Auto update instances
2022-04-27 00:10:11 +00:00
"https://invidious.sethforprivacy.com",
Add cf filter to nightly build, update services The cloudflare filter has been added back into the nightly build. Now that the filtering method uses direct querying of the instance IP(s), it should be more reliable than the namespace lookup (and more accurate). services.json has been updated with the latest filtered results from services-full.json as well.
2023-01-04 17:03:03 +00:00
"https://invidious.silur.me",
[CI] Auto update instances
2022-07-04 00:11:31 +00:00
"https://invidious.slipfox.xyz",
Restore missing invidious instances The latest CI update removed all invidious instances. Need to update CI to skip applying an update for a particular service if there is an error when fetching.
2022-02-07 18:40:56 +00:00
"https://invidious.snopyta.org",
[CI] Auto update instances
2022-05-12 00:10:24 +00:00
"https://invidious.tiekoetter.com",
[CI] Auto update instances
2022-03-04 00:08:43 +00:00
"https://invidious.weblibre.org",
[CI] Auto update instances
2023-01-07 00:13:22 +00:00
"https://iv.ggtyler.dev",
Add cf filter to nightly build, update services The cloudflare filter has been added back into the nightly build. Now that the filtering method uses direct querying of the instance IP(s), it should be more reliable than the namespace lookup (and more accurate). services.json has been updated with the latest filtered results from services-full.json as well.
2023-01-04 17:03:03 +00:00
"https://iv.melmac.space",
"https://vid.priv.au",
Restore missing invidious instances The latest CI update removed all invidious instances. Need to update CI to skip applying an update for a particular service if there is an error when fetching.
2022-02-07 18:40:56 +00:00
"https://vid.puffyan.us",
[CI] Auto update instances
2023-01-10 00:14:48 +00:00
"https://watch.thekitty.zone",
[CI] Auto update instances
2022-04-07 00:09:17 +00:00
"https://y.com.sb",
Restore missing invidious instances The latest CI update removed all invidious instances. Need to update CI to skip applying an update for a particular service if there is an error when fetching.
2022-02-07 18:40:56 +00:00
"https://yewtu.be",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://yt.artemislena.eu",
"https://yt.funami.tech"
Restore missing invidious instances The latest CI update removed all invidious instances. Need to update CI to skip applying an update for a particular service if there is an error when fetching.
2022-02-07 18:40:56 +00:00
]
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
},
Support teddit, piped, and simplytranslate - teddit (https://teddit.net/about) A free and open source alternative Reddit front-end focused on privacy. Inspired by the Nitter project. - Piped (https://github.com/TeamPiped/Piped) An alternative privacy-friendly YouTube frontend which is efficient by design. - SimplyTranslate (https://simple-web.org/projects/simplytranslate.html) We aim to provide fast and private translations to the user without wasting much overhead for extensive styling or JavaScript ___ Also adds SimplyTranslate to the github pipeline, since they provide a list of the service's public instances. Closes #4
2021-12-16 00:09:00 +00:00
{
"type": "piped",
"test_url": "/watch?v=eBGIQ7ZuuiU",
Update piped instances Fixes #86
2023-01-24 23:28:22 +00:00
"fallback": "https://piped.video",
Support teddit, piped, and simplytranslate - teddit (https://teddit.net/about) A free and open source alternative Reddit front-end focused on privacy. Inspired by the Nitter project. - Piped (https://github.com/TeamPiped/Piped) An alternative privacy-friendly YouTube frontend which is efficient by design. - SimplyTranslate (https://simple-web.org/projects/simplytranslate.html) We aim to provide fast and private translations to the user without wasting much overhead for extensive styling or JavaScript ___ Also adds SimplyTranslate to the github pipeline, since they provide a list of the service's public instances. Closes #4
2021-12-16 00:09:00 +00:00
"instances": [
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://watch.whatever.social",
Update piped instances Fixes #86
2023-01-24 23:28:22 +00:00
"https://yt.jae.fi",
"https://il.ax",
"https://piped.esmailelbob.xyz",
"https://piped.projectsegfau.lt",
"https://piped.privacydev.net",
"https://piped.palveluntarjoaja.eu",
"https://piped.smnz.de",
"https://piped.adminforge.de",
"https://piped.qdi.fi",
"https://piped.hostux.net",
"https://pd.vern.cc",
"https://piped.chauvet.pro"
Support teddit, piped, and simplytranslate - teddit (https://teddit.net/about) A free and open source alternative Reddit front-end focused on privacy. Inspired by the Nitter project. - Piped (https://github.com/TeamPiped/Piped) An alternative privacy-friendly YouTube frontend which is efficient by design. - SimplyTranslate (https://simple-web.org/projects/simplytranslate.html) We aim to provide fast and private translations to the user without wasting much overhead for extensive styling or JavaScript ___ Also adds SimplyTranslate to the github pipeline, since they provide a list of the service's public instances. Closes #4
2021-12-16 00:09:00 +00:00
]
},
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
{
"type": "nitter",
"test_url": "/twitter",
"fallback": "https://nitter.net",
"instances": [
"https://nitter.net",
"https://nitter.42l.fr",
"https://nitter.pussthecat.org",
"https://nitter.fdn.fr",
"https://nitter.1d4.us",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://nitter.kavin.rocks",
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
"https://nitter.unixfox.eu",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://nitter.namazso.eu",
"https://nitter.moomoo.me",
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
"https://bird.trom.tf",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://nitter.it",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://twitter.censors.us",
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
"https://nitter.grimneko.de",
"https://twitter.076.ne.jp",
Update services.json (#16) Add "*.bus-hit.me" instances, remove a few dead instances
2022-02-07 18:33:49 +00:00
"https://nitter.sethforprivacy.com",
Add new libreddit and nitter instances (#25) https://leddit.xyz, https://de.leddit.xyz https://nttr.stream https://de.nttr.stream
2022-03-22 15:32:30 +00:00
"https://nitter.bus-hit.me",
Add "unofficialbird.com" Nitter instance [skip ci] (#58)
2022-08-02 15:21:08 +00:00
"https://n.l5.ca",
Add cf filter to nightly build, update services The cloudflare filter has been added back into the nightly build. Now that the filtering method uses direct querying of the instance IP(s), it should be more reliable than the namespace lookup (and more accurate). services.json has been updated with the latest filtered results from services-full.json as well.
2023-01-04 17:03:03 +00:00
"https://unofficialbird.com",
"https://nitter.ungovernable.men"
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
]
},
Add scribe to supported services scribe (https://https://git.sr.ht/~edwardloveall/scribe) is an alternative frontend for Medium.
2021-12-07 03:15:49 +00:00
{
[CI] Auto update instances
2021-12-08 00:40:20 +00:00
"type": "scribe",
Fix missing slash in scribe test path
2021-12-08 23:36:00 +00:00
"test_url": "/@ftrain/big-data-small-effort-b62607a43a8c",
[CI] Auto update instances
2021-12-08 00:40:20 +00:00
"fallback": "https://scribe.rip",
"instances": [
"https://scribe.rip",
"https://scribe.nixnet.services",
[CI] Auto update instances
2022-02-04 00:39:53 +00:00
"https://scribe.citizen4.eu",
[CI] Auto update instances
2022-03-29 00:09:39 +00:00
"https://scribe.bus-hit.me",
[CI] Auto update instances
2022-08-02 04:24:46 +00:00
"https://scribe.froth.zone",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://scribe.esmailelbob.xyz",
"https://scribe.privacydev.net",
"https://sc.vern.cc"
[CI] Auto update instances
2021-12-08 00:40:20 +00:00
]
Add scribe to supported services scribe (https://https://git.sr.ht/~edwardloveall/scribe) is an alternative frontend for Medium.
2021-12-07 03:15:49 +00:00
},
Support teddit, piped, and simplytranslate - teddit (https://teddit.net/about) A free and open source alternative Reddit front-end focused on privacy. Inspired by the Nitter project. - Piped (https://github.com/TeamPiped/Piped) An alternative privacy-friendly YouTube frontend which is efficient by design. - SimplyTranslate (https://simple-web.org/projects/simplytranslate.html) We aim to provide fast and private translations to the user without wasting much overhead for extensive styling or JavaScript ___ Also adds SimplyTranslate to the github pipeline, since they provide a list of the service's public instances. Closes #4
2021-12-16 00:09:00 +00:00
{
"type": "simplytranslate",
"test_url": "/?engine=google&text=simplicado",
"fallback": "https://simplytranslate.org",
"instances": [
[CI] Auto update instances
2022-03-27 00:08:46 +00:00
"https://simplytranslate.esmailelbob.xyz",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://simplytranslate.manerakai.com",
Support teddit, piped, and simplytranslate - teddit (https://teddit.net/about) A free and open source alternative Reddit front-end focused on privacy. Inspired by the Nitter project. - Piped (https://github.com/TeamPiped/Piped) An alternative privacy-friendly YouTube frontend which is efficient by design. - SimplyTranslate (https://simple-web.org/projects/simplytranslate.html) We aim to provide fast and private translations to the user without wasting much overhead for extensive styling or JavaScript ___ Also adds SimplyTranslate to the github pipeline, since they provide a list of the service's public instances. Closes #4
2021-12-16 00:09:00 +00:00
"https://simplytranslate.org",
[CI] Auto update instances
2022-01-24 00:38:30 +00:00
"https://simplytranslate.pussthecat.org",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://st.odyssey346.dev",
[CI] Auto update instances
2022-05-25 00:11:19 +00:00
"https://st.privacydev.net",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://st.tokhmi.xyz",
[CI] Auto update instances
2022-05-13 00:11:29 +00:00
"https://tl.vern.cc",
[CI] Auto update instances
2022-01-24 00:38:30 +00:00
"https://translate.bus-hit.me",
Remove cloudflare filter from update workflow The cloudflare filter, when performed as part of the github action workflow, doesn't seem to work nearly as reliably when run on an actual machine. The farside server will instead run the un-cloudflare script whenever it pulls in new changes to services-full.json, which should be a much more reliable approach to filtering out cloudflare instances.
2022-08-04 19:16:58 +00:00
"https://translate.josias.dev",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://translate.namazso.eu",
[CI] Auto update instances
2022-02-03 00:38:41 +00:00
"https://translate.northboot.xyz",
[CI] Auto update instances
2022-06-04 00:09:56 +00:00
"https://translate.priv.pw",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://translate.riverside.rocks",
[CI] Auto update instances
2022-05-13 00:11:29 +00:00
"https://translate.slipfox.xyz",
[CI] Auto update instances
2022-02-18 00:47:56 +00:00
"https://translate.tiekoetter.com"
Support teddit, piped, and simplytranslate - teddit (https://teddit.net/about) A free and open source alternative Reddit front-end focused on privacy. Inspired by the Nitter project. - Piped (https://github.com/TeamPiped/Piped) An alternative privacy-friendly YouTube frontend which is efficient by design. - SimplyTranslate (https://simple-web.org/projects/simplytranslate.html) We aim to provide fast and private translations to the user without wasting much overhead for extensive styling or JavaScript ___ Also adds SimplyTranslate to the github pipeline, since they provide a list of the service's public instances. Closes #4
2021-12-16 00:09:00 +00:00
]
},
Support lingva translate service https://github.com/TheDavidDelta/lingva-translate
2021-12-17 16:45:06 +00:00
{
"type": "lingva",
"test_url": "/auto/en/hola",
"fallback": "https://lingva.ml",
"instances": [
"https://lingva.ml",
Remove dead lingva instance Fixes #70
2022-10-13 22:00:09 +00:00
"https://translate.igna.rocks"
Support lingva translate service https://github.com/TheDavidDelta/lingva-translate
2021-12-17 16:45:06 +00:00
]
},
Support imgur alternatives - Imgin (only one instance) - https://git.voidnet.tech/kev/imgin/ - Rimgo - https://codeberg.org/video-prize-ranch/rimgo Closes #11
2022-01-26 16:59:32 +00:00
{
"type": "rimgo",
"test_url": "/a/H8M4rcp",
"fallback": "https://i.bcow.xyz",
"instances": [
"https://i.bcow.xyz",
"https://rimgo.pussthecat.org",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://img.riverside.rocks",
Support imgur alternatives - Imgin (only one instance) - https://git.voidnet.tech/kev/imgin/ - Rimgo - https://codeberg.org/video-prize-ranch/rimgo Closes #11
2022-01-26 16:59:32 +00:00
"https://rimgo.totaldarkness.net",
"https://rimgo.bus-hit.me"
]
},
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
{
"type": "whoogle",
whoogle: Remove inactive instances, fix test url The default url redirects to a session validation url first (w/ status code 307). Disabling cookies by default allows a 200 code to be returned for successful searches.
2021-11-30 00:35:28 +00:00
"test_url": "/search?cookies_disabled=1&q=<%=query%>",
Add official whoogle fosshost instance to services
2021-11-29 23:28:12 +00:00
"fallback": "https://whoogle.fossho.st",
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
"instances": [
[CI] Auto update instances
2022-02-11 00:45:49 +00:00
"https://gowogle.voring.me",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://s.tokhmi.xyz",
[CI] Auto update instances
2021-12-24 00:39:09 +00:00
"https://search.sethforprivacy.com",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://wg.vern.cc",
[CI] Auto update instances
2023-01-31 00:14:22 +00:00
"https://wgl.frail.duckdns.org",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://whoogle.dcs0.hu",
[CI] Auto update instances
2022-02-09 00:43:04 +00:00
"https://whoogle.esmailelbob.xyz",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://whoogle.hostux.net",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://whoogle.privacydev.net",
"https://www.indexia.gq"
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
]
},
{
"type": "searx",
Use format str for search engine queries Although the current list of queries is only 2 elements ("time" and "weather"), this allows searches for Whoogle and Searx to be slightly more random, and potentially avoid any issues with their parent engine rate limiting them.
2021-11-29 23:25:00 +00:00
"test_url": "/search?q=<%=query%>",
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
"fallback": "https://searx.be",
[CI] Auto update instances
2021-12-15 00:38:29 +00:00
"instances": [
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://baresearch.org",
[CI] Auto update instances
2023-01-13 00:16:44 +00:00
"https://coppedge.info",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://darmarit.org/searx",
[CI] Auto update instances
2022-05-27 00:09:55 +00:00
"https://dynabyte.ca",
Add cf filter to nightly build, update services The cloudflare filter has been added back into the nightly build. Now that the filtering method uses direct querying of the instance IP(s), it should be more reliable than the namespace lookup (and more accurate). services.json has been updated with the latest filtered results from services-full.json as well.
2023-01-04 17:03:03 +00:00
"https://gsch.eu",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://northboot.xyz",
[CI] Auto update instances
2023-01-31 00:14:22 +00:00
"https://notsearch.uk",
"https://opnxng.com",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://paulgo.io",
"https://priv.au",
[CI] Auto update instances
2023-01-28 00:11:50 +00:00
"https://privatesearch.dev",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://s.frlt.one",
"https://s.trung.fun",
"https://s.zhaocloud.net",
"https://search.0relay.com",
"https://search.bus-hit.me",
"https://search.chemicals-in-the-water.eu",
[CI] Auto update instances
2023-01-19 00:12:52 +00:00
"https://search.cosyinternet.cafe",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://search.gcomm.ch",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://search.leptons.xyz",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://search.mdosch.de",
[CI] Auto update instances
2023-01-19 00:12:52 +00:00
"https://search.neet.works",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://search.ononoki.org",
"https://search.rabbit-company.com",
"https://search.rhscz.eu",
"https://search.rowie.at",
"https://search.sapti.me",
[CI] Auto update instances
2023-01-20 00:12:45 +00:00
"https://search.serginho.dev",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://search.smnz.de",
"https://search.suenram.us",
"https://search.unlocked.link",
[CI] Auto update instances
2023-01-10 00:14:48 +00:00
"https://search.us.projectsegfau.lt",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://search.zzls.xyz",
"https://searx.baczek.me",
[CI] Auto update instances
2023-01-25 00:13:52 +00:00
"https://searx.be",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.becomesovran.com",
"https://searx.catfluori.de",
[CI] Auto update instances
2023-02-03 00:12:37 +00:00
"https://searx.cthd.icu",
[CI] Auto update instances
2022-03-22 00:09:08 +00:00
"https://searx.divided-by-zero.eu",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.dresden.network",
"https://searx.ericaftereric.top",
[CI] Auto update instances
2023-02-02 00:13:02 +00:00
"https://searx.fi",
"https://searx.fmac.xyz",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.mastodontech.de",
"https://searx.mha.fi",
[CI] Auto update instances
2023-01-29 00:13:51 +00:00
"https://searx.namejeff.xyz",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.oakleycord.dev",
[CI] Auto update instances
2023-01-05 00:14:58 +00:00
"https://searx.priv.pw",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.prvcy.eu",
"https://searx.rasp.fr",
[CI] Auto update instances
2022-03-22 00:09:08 +00:00
"https://searx.ru",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.sev.monster",
[CI] Auto update instances
2023-01-30 00:13:12 +00:00
"https://searx.si",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.slipfox.xyz/searx",
[CI] Auto update instances
2022-07-15 00:11:37 +00:00
"https://searx.sp-codes.de",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.tiekoetter.com",
"https://searx.tuxcloud.net",
[CI] Auto update instances
2022-03-22 00:09:08 +00:00
"https://searx.webheberg.info",
[CI] Auto update instances
2023-01-20 00:12:45 +00:00
"https://searx.work",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://searx.xyz",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searxng.au",
"https://spot.murena.io",
"https://xo.wtf"
[CI] Auto update instances
2021-12-15 00:38:29 +00:00
]
Add support for Wikiless instances "A free open source alternative Wikipedia front-end focused on privacy" - https://codeberg.org/orenom/Wikiless
2022-02-25 00:27:34 +00:00
},
Support SearXNG Added a new seperate service for only redirecting to SearXNG instances. Note that plain "searx" redirects will use both SearX and SearXNG instances for those who don't have a preference between the two. Closes #23
2022-03-18 19:28:45 +00:00
{
"type": "searxng",
"test_url": "/search?q=<%=query%>",
"fallback": "https://searx.be",
"instances": [
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://baresearch.org",
[CI] Auto update instances
2023-01-13 00:16:44 +00:00
"https://coppedge.info",
Remove cloudflare filter from update workflow The cloudflare filter, when performed as part of the github action workflow, doesn't seem to work nearly as reliably when run on an actual machine. The farside server will instead run the un-cloudflare script whenever it pulls in new changes to services-full.json, which should be a much more reliable approach to filtering out cloudflare instances.
2022-08-04 19:16:58 +00:00
"https://darmarit.org/searx",
Add cf filter to nightly build, update services The cloudflare filter has been added back into the nightly build. Now that the filtering method uses direct querying of the instance IP(s), it should be more reliable than the namespace lookup (and more accurate). services.json has been updated with the latest filtered results from services-full.json as well.
2023-01-04 17:03:03 +00:00
"https://dynabyte.ca",
"https://gsch.eu",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://northboot.xyz",
[CI] Auto update instances
2023-01-31 00:14:22 +00:00
"https://notsearch.uk",
"https://opnxng.com",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://paulgo.io",
[CI] Auto update instances
2022-07-20 00:11:04 +00:00
"https://priv.au",
[CI] Auto update instances
2023-01-28 00:11:50 +00:00
"https://privatesearch.dev",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://s.frlt.one",
"https://s.trung.fun",
[CI] Auto update instances
2022-03-22 00:09:08 +00:00
"https://s.zhaocloud.net",
[CI] Auto update instances
2022-08-02 04:24:46 +00:00
"https://search.0relay.com",
[CI] Auto update instances
2022-03-22 00:09:08 +00:00
"https://search.bus-hit.me",
[CI] Auto update instances
2022-07-26 00:10:41 +00:00
"https://search.chemicals-in-the-water.eu",
[CI] Auto update instances
2023-01-19 00:12:52 +00:00
"https://search.cosyinternet.cafe",
[CI] Auto update instances
2022-07-14 00:11:53 +00:00
"https://search.gcomm.ch",
Update cloudflare filtered service list
2022-12-21 22:23:02 +00:00
"https://search.leptons.xyz",
[CI] Auto update instances
2022-04-04 00:08:37 +00:00
"https://search.mdosch.de",
[CI] Auto update instances
2023-01-19 00:12:52 +00:00
"https://search.neet.works",
[CI] Auto update instances
2022-06-05 00:11:36 +00:00
"https://search.ononoki.org",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://search.rabbit-company.com",
"https://search.rhscz.eu",
"https://search.rowie.at",
[CI] Auto update instances
2022-06-11 00:09:20 +00:00
"https://search.sapti.me",
[CI] Auto update instances
2023-01-20 00:12:45 +00:00
"https://search.serginho.dev",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://search.smnz.de",
"https://search.suenram.us",
"https://search.unlocked.link",
[CI] Auto update instances
2023-01-10 00:14:48 +00:00
"https://search.us.projectsegfau.lt",
[CI] Auto update instances
2022-05-07 00:08:36 +00:00
"https://search.zzls.xyz",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.baczek.me",
[CI] Auto update instances
2023-01-25 00:13:52 +00:00
"https://searx.be",
[CI] Auto update instances
2022-06-12 00:10:17 +00:00
"https://searx.becomesovran.com",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.catfluori.de",
[CI] Auto update instances
2023-02-03 00:12:37 +00:00
"https://searx.cthd.icu",
[CI] Auto update instances
2022-07-25 00:10:41 +00:00
"https://searx.ericaftereric.top",
[CI] Auto update instances
2023-02-02 00:13:02 +00:00
"https://searx.fi",
"https://searx.fmac.xyz",
[CI] Auto update instances
2022-08-02 04:24:46 +00:00
"https://searx.mha.fi",
[CI] Auto update instances
2023-01-29 00:13:51 +00:00
"https://searx.namejeff.xyz",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.oakleycord.dev",
[CI] Auto update instances
2023-01-05 00:14:58 +00:00
"https://searx.priv.pw",
[CI] Auto update instances
2022-04-06 00:08:42 +00:00
"https://searx.prvcy.eu",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.rasp.fr",
[CI] Auto update instances
2022-06-14 00:10:48 +00:00
"https://searx.sev.monster",
[CI] Auto update instances
2023-01-30 00:13:12 +00:00
"https://searx.si",
Remove cloudflare filter from update workflow The cloudflare filter, when performed as part of the github action workflow, doesn't seem to work nearly as reliably when run on an actual machine. The farside server will instead run the un-cloudflare script whenever it pulls in new changes to services-full.json, which should be a much more reliable approach to filtering out cloudflare instances.
2022-08-04 19:16:58 +00:00
"https://searx.slipfox.xyz/searx",
[CI] Auto update instances
2022-03-22 00:09:08 +00:00
"https://searx.tiekoetter.com",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searx.tuxcloud.net",
[CI] Auto update instances
2023-01-20 00:12:45 +00:00
"https://searx.work",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://searxng.au",
[CI] Auto update instances
2023-01-26 00:13:34 +00:00
"https://spot.murena.io",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://xo.wtf"
Support SearXNG Added a new seperate service for only redirecting to SearXNG instances. Note that plain "searx" redirects will use both SearX and SearXNG instances for those who don't have a preference between the two. Closes #23
2022-03-18 19:28:45 +00:00
]
},
Add support for Wikiless instances "A free open source alternative Wikipedia front-end focused on privacy" - https://codeberg.org/orenom/Wikiless
2022-02-25 00:27:34 +00:00
{
"type": "wikiless",
"test_url": "/wiki/Wikipedia?lang=en",
"fallback": "https://wikiless.org",
"instances": [
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://wiki.adminforge.de",
[CI] Auto update instances
2022-04-08 00:08:37 +00:00
"https://wiki.froth.zone",
[CI] Auto update instances
2022-06-22 00:11:46 +00:00
"https://wiki.slipfox.xyz",
[CI] Auto update instances
2022-05-21 00:09:29 +00:00
"https://wikiless.esmailelbob.xyz",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://wikiless.funami.tech",
Remove cloudflare filter from update workflow The cloudflare filter, when performed as part of the github action workflow, doesn't seem to work nearly as reliably when run on an actual machine. The farside server will instead run the un-cloudflare script whenever it pulls in new changes to services-full.json, which should be a much more reliable approach to filtering out cloudflare instances.
2022-08-04 19:16:58 +00:00
"https://wikiless.lunar.icu",
[CI] Auto update instances
2022-04-27 00:10:11 +00:00
"https://wikiless.northboot.xyz",
Add support for Wikiless instances "A free open source alternative Wikipedia front-end focused on privacy" - https://codeberg.org/orenom/Wikiless
2022-02-25 00:27:34 +00:00
"https://wikiless.org",
[CI] Auto update instances
2022-04-27 00:10:11 +00:00
"https://wikiless.sethforprivacy.com",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://wikiless.tiekoetter.com",
"https://wl.vern.cc"
Add support for Wikiless instances "A free open source alternative Wikipedia front-end focused on privacy" - https://codeberg.org/orenom/Wikiless
2022-02-25 00:27:34 +00:00
]
Add librarian (LBRY/Odysee frontend) Closes #36
2022-06-07 17:17:57 +00:00
},
{
"type": "librarian",
[CI] Auto update instances
2022-06-08 00:08:41 +00:00
"test_url": "",
Add librarian (LBRY/Odysee frontend) Closes #36
2022-06-07 17:17:57 +00:00
"fallback": "https://lbry.bcow.xyz",
"instances": [
"https://lbry.bcow.xyz",
"https://odysee.076.ne.jp",
"https://librarian.pussthecat.org",
"https://lbry.mutahar.rocks",
"https://librarian.esmailelbob.xyz",
"https://lbry.vern.cc"
]
Add proxitok (TikTok frontend) Closes #19
2022-06-21 22:12:12 +00:00
},
{
"type": "proxitok",
"test_url": "/discover",
"fallback": "https://proxitok.herokuapp.com",
"instances": [
"https://proxitok.herokuapp.com",
"https://proxitok.pussthecat.org",
"https://proxitok.privacydev.net"
]
Add support for librex search See: https://github.com/hnhx/librex Closes #47
2022-07-27 22:56:34 +00:00
},
{
"type": "librex",
"test_url": "/search.php?q=<%=query%>",
Update `beparanoid.de` domains Moved to femboy.hu. Fixes #85
2023-01-19 17:21:05 +00:00
"fallback": "https://search.femboy.hu",
Add support for librex search See: https://github.com/hnhx/librex Closes #47
2022-07-27 22:56:34 +00:00
"instances": [
Update `beparanoid.de` domains Moved to femboy.hu. Fixes #85
2023-01-19 17:21:05 +00:00
"https://search.femboy.hu",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://search.davidovski.xyz",
"https://search.funami.tech",
"https://librex.catalyst.sx"
Add support for librex search See: https://github.com/hnhx/librex Closes #47
2022-07-27 22:56:34 +00:00
]
Support libremdb and querte (imdb and quora alts) Includes support for redirecting via full url, ie: -> farside.link/https://www.imdb.com/title/tt0133093/ will redirect to a libremdb instance. Closes #48
2022-07-27 23:14:15 +00:00
},
{
Fix spelling of quetre (#55)
2022-07-31 17:05:48 +00:00
"type": "quetre",
Support libremdb and querte (imdb and quora alts) Includes support for redirecting via full url, ie: -> farside.link/https://www.imdb.com/title/tt0133093/ will redirect to a libremdb instance. Closes #48
2022-07-27 23:14:15 +00:00
"test_url": "/How-does-the-Z-boson-decay",
[CI] Auto update instances
2023-01-15 00:13:47 +00:00
"fallback": "https://quetre.iket.me",
Support libremdb and querte (imdb and quora alts) Includes support for redirecting via full url, ie: -> farside.link/https://www.imdb.com/title/tt0133093/ will redirect to a libremdb instance. Closes #48
2022-07-27 23:14:15 +00:00
"instances": [
[CI] Auto update instances
2023-01-15 00:13:47 +00:00
"https://quetre.iket.me",
Support libremdb and querte (imdb and quora alts) Includes support for redirecting via full url, ie: -> farside.link/https://www.imdb.com/title/tt0133093/ will redirect to a libremdb instance. Closes #48
2022-07-27 23:14:15 +00:00
"https://quora.vern.cc",
"https://quetre.pussthecat.org",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://quetre.tokhmi.xyz",
Support libremdb and querte (imdb and quora alts) Includes support for redirecting via full url, ie: -> farside.link/https://www.imdb.com/title/tt0133093/ will redirect to a libremdb instance. Closes #48
2022-07-27 23:14:15 +00:00
"https://quetre.projectsegfau.lt",
[CI] Auto update instances
2023-01-15 00:13:47 +00:00
"https://quetre.esmailelbob.xyz",
"https://quetre.odyssey346.dev",
"https://quetre.privacydev.net",
"https://ask.habedieeh.re",
"https://quetre.blackdrgn.nl",
"https://quetre.pufe.org",
"https://que.wilbvr.me"
Support libremdb and querte (imdb and quora alts) Includes support for redirecting via full url, ie: -> farside.link/https://www.imdb.com/title/tt0133093/ will redirect to a libremdb instance. Closes #48
2022-07-27 23:14:15 +00:00
]
},
{
"type": "libremdb",
[CI] Auto update instances
2022-08-02 04:24:46 +00:00
"test_url": "/title/tt0133093",
Support libremdb and querte (imdb and quora alts) Includes support for redirecting via full url, ie: -> farside.link/https://www.imdb.com/title/tt0133093/ will redirect to a libremdb instance. Closes #48
2022-07-27 23:14:15 +00:00
"fallback": "https://libremdb.herokuapp.com",
"instances": [
"https://libremdb.herokuapp.com",
"https://libremdb.pussthecat.org",
"https://libremdbeu.herokuapp.com",
Filter against cloudflare proxy (not nameservers) The previous approach to filtering cloudflare instances was checking if cloudflare nameservers were assigned to that domain. I believe this was too harsh of a filter, as quite a few instances were removed even though they were not using cloudflare's proxying feature. To solve this, the filtering script has been updated to manually fetch each IP associated with a domain and see if it returns the 1003 error that cloudflare proxied sites return when queried directly.
2022-12-09 17:57:39 +00:00
"https://lmdb.tokhmi.xyz",
Support libremdb and querte (imdb and quora alts) Includes support for redirecting via full url, ie: -> farside.link/https://www.imdb.com/title/tt0133093/ will redirect to a libremdb instance. Closes #48
2022-07-27 23:14:15 +00:00
"https://libremdb.esmailelbob.xyz"
]
Automate updates for list of searx instances (#3) * Create nightly update workflow for instances A nightly GitHub Actions CI workflow has been added to fetch new instances of supported services within Farside. Currently only Searx is supported, but obviously others could be added if there are similarly easy ways to fetch and filter instances programmatically. services.json has also been updated with the initial results of the workflow script. * Set headers for every HTTPoison request This serves as a workaround for bot blocking via filtron. * Expand filtering of searx instances New filter enforces: - No Cloudflare - Good TLS config - Good HTTP header config - Vanilla instances or forks - Instances with 100% search success
2021-11-26 16:12:46 +00:00
}
Output available instances and fallback URL to redis Once a list of available URLs has been determined for a particular service, the list is written as "service -> [list of instances]" to a local redis connection. These can then be used in the greater routing logic to pick a random instance from the list, or use a fallback instance if none are determined to be available.
2021-10-22 23:15:40 +00:00
]
Reference in a new issue Copy permalink