Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/benbusby/farside
A smart redirecting gateway for various frontend services
https://github.com/benbusby/farside
elixir privacy redirect
Last synced: about 11 hours ago
JSON representation
A smart redirecting gateway for various frontend services
- Host: GitHub
- URL: https://github.com/benbusby/farside
- Owner: benbusby
- License: mit
- Created: 2021-10-21T21:50:04.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-10-30T00:17:47.000Z (4 months ago)
- Last Synced: 2024-10-30T02:49:39.480Z (4 months ago)
- Topics: elixir, privacy, redirect
- Language: Elixir
- Homepage: https://farside.link
- Size: 714 KB
- Stars: 756
- Watchers: 7
- Forks: 47
- Open Issues: 36
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- alternative-frontends - x
- alternative-front-ends - Farside - oriented alternative frontends, such as Nitter, Libreddit, etc. This allows for users to have more reliable access to the available public instances for a particular service, while also helping to distribute traffic more evenly across all instances and avoid performance bottlenecks and rate-limiting. (Redirection / Other services)
- alternative-frontends - x
README
[](https://github.com/benbusby/farside/releases)
[](http://opensource.org/licenses/MIT)
[](https://github.com/benbusby/farside/actions/workflows/tests.yml)
Contents
1. [About](#about)
2. [Demo](#demo)
3. [How It Works](#how-it-works)
4. [Cloudflare](#regarding-cloudflare)
5. [Development](#development)
1. [Environment Variables](#environment-variables)
6. [Search Integration](#search-integration)
1. [Kagi](#kagi)
2. [Whoogle Search](#whoogle-search)
## About
A redirecting service for FOSS alternative frontends.
[Farside](https://farside.link) provides links that automatically redirect to
working instances of privacy-oriented alternative frontends, such as Nitter,
Libreddit, etc. This allows for users to have more reliable access to the
available public instances for a particular service, while also helping to
distribute traffic more evenly across all instances and avoid performance
bottlenecks and rate-limiting.
Farside also integrates smoothly with basic redirector extensions in most
browsers. For a simple example setup,
[refer to the wiki](https://github.com/benbusby/farside/wiki/Browser-Extension).
## Demo
Farside's links work with the following structure: `farside.link//`
For example:
Service
Page
Farside Link
Scribe
View Medium post
https://farside.link/scribe/@ftrain/big-data-small-effort-b62607a43a8c
Libreddit
/r/popular
https://farside.link/libreddit/r/popular
BreezeWiki
Balatro Wiki
https://farside.link/https://balatrogame.fandom.com
SearXNG
Search "EFF"
https://farside.link/searxng/search?q=EFF
SimplyTranslate
Translate "hola"
https://farside.link/simplytranslate/?engine=google&text=hola
Lingva
Translate "bonjour"
https://farside.link/lingva/auto/en/bonjour
Rimgo
View photo album
https://farside.link/rimgo/a/H8M4rcp
Note: This table doesn't include all available services. For a complete list of supported frontends, see: https://farside.link
Farside also accepts URLs to "parent" services, and will redirect to an appropriate front end service, for example:
- https://farside.link/https://balatrogame.fandom.com/wiki/Abandoned_Deck will redirect to a [BreezeWiki](https://gitdab.com/cadence/breezewiki) instance
- https://farside.link/reddit.com/r/popular will redirect to a [Libreddit](https://github.com/spikecodes/libreddit) or [Teddit](https://codeberg.org/teddit/teddit) instance
- etc.
## How It Works
The app runs with an internally scheduled cron task that queries all instances
for services defined in [services.json](services.json) every 5 minutes. For
each instance, as long as the instance takes <5 seconds to respond and returns
a successful response code, the instance is added to a list of available
instances for that particular service. If not, it is discarded until the next
update period.
Farside's routing is very minimal, with only the following routes:
- `/`
- The app home page, displaying all live instances for every service
- `/:service/*glob`
- The main endpoint for redirecting a user to a working instance of a
particular service with the specified path
- Ex: `/libreddit/r/popular` would navigate to `/r/popular`
- If the service provided is actually a URL to a "parent" service
(i.e. "youtube.com" instead of "piped" or "invidious"), Farside
will determine the correct frontend to use for the specified URL.
- Note that a path is not required. `/libreddit` for example will still
redirect the user to a working libreddit instance
- `/_/:service/*glob`
- Achieves the same redirect as the main `/:service/*glob` endpoint, but
preserves a short landing page in the browser's history to allow quickly
jumping between instances by navigating back.
- Ex: `/_/nitter` -> nitter instance A -> (navigate back one page) -> nitter
instance B -> ...
- *Note: Uses Javascript to preserve the page in history*
When a service is requested with the `/:service/...` endpoint, Farside requests
the list of working instances from the db and returns a random one from the list
and adds that instance as a new entry in the db to remove from subsequent
requests for that service. For example:
A user navigates to `/nitter` and is redirected to `nitter.net`. The next user
to request `/nitter` will be guaranteed to not be directed to `nitter.net`, and
will instead be redirected to a separate (random) working instance. That
instance will now take the place of `nitter.net` as the "reserved" instance, and
`nitter.net` will be returned to the list of available Nitter instances.
This "reserving" of previously chosen instances is performed in an attempt to
ensure better distribution of traffic to available instances for each service.
Farside also has built-in IP ratelimiting for all requests, enforcing only one
request per second per IP.
## Regarding Cloudflare
Instances for each supported service that are deployed behind Cloudflare are
not included when using [farside.link](https://farside.link). If you would like
to also access instances that use Cloudflare (in addition to instances that do
not), you can either use [cf.farside.link](https://cf.farside.link) instead, or
deploy your own instance of Farside and set
`FARSIDE_SERVICES_JSON=services-full.json` when running.
If you do decide to use [cf.farside.link](https://cf.farside.link) or use the
full instance list provided by `services-full.json`, please be aware that
Cloudflare takes steps to block site visitors using Tor (and some VPNs), and
that their mission to centralize the entire web behind their service ultimately
goes against what Farside is trying to solve. Use at your own discretion.
## Development
- Install [Go](https://go.dev/doc/install)
- Compile with `go build`
### Environment Variables
Name
Purpose
FARSIDE_TEST
If enabled, bypasses the instance availability check and adds all instances to the pool
FARSIDE_PORT
The port to run Farside on (default: `4001`)
FARSIDE_DB_DIR
The path to the directory to use for storing instance data (default: `./`)
FARSIDE_CF_ENABLED
Set to 1 to enable redirecting to instances behind cloudflare
FARSIDE_CRON
Set to 0 to deactivate the periodic instance availability check
## Search Integration
### Kagi
https://kagi.com
On the settings page, go to `Search > Advanced > Open Redirects` and setup your redirects.
With the exception of BreezeWiki, most redirect rules can just extract the path of the
link you're visiting and append them to whichever Farside redirect you want to use.
For example:
##### Medium -> Scribe
`^https://medium.com/(.*)|https://farside.link/scribe/$1`
##### Fandom -> BreezeWiki
`^https://([^/]+).fandom.com/(.*)|https://farside.link/breezewiki/$1/$2`
### Whoogle Search
https://github.com/benbusby/whoogle-search
Whoogle automatically routes eligible links through Farside when the `Replace
Social Media Links` option in the home page settings menu is enabled.