A smart redirecting gateway for various frontend services
Find a file
Ben Busby 919dd6f602
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-15 17:12:59 -07:00
.github/workflows Support teddit, piped, and simplytranslate 2021-12-15 17:12:59 -07:00
config Use format str for search engine queries 2021-11-29 16:31:55 -07:00
img Convert logo to SVG 2021-11-12 17:04:34 -07:00
lib Remove FARSIDE_NO_ROUTER env var 2021-12-09 15:33:58 -07:00
test Fix formatting 2021-11-12 14:40:05 -07:00
.formatter.exs Setup basic Plug.Router framework for serving requests 2021-10-22 18:28:12 -06:00
.gitignore Write results of update script to file for debugging 2021-10-22 18:07:59 -06:00
index.eex Add margin to service list ul element 2021-11-23 14:36:54 -07:00
LICENSE Initial commit 2021-10-21 15:50:04 -06:00
mix.exs Use quantum core for update scheduling 2021-11-24 09:35:21 -07:00
mix.lock Use quantum core for update scheduling 2021-11-24 09:35:21 -07:00
README.md Remove FARSIDE_NO_ROUTER env var 2021-12-09 15:33:58 -07:00
services.json Support teddit, piped, and simplytranslate 2021-12-15 17:12:59 -07:00

Farside

Latest Release MIT License Elixir CI

A redirecting service for FOSS alternative frontends.

Farside 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.

Demo

Service Page Farside Link
Libreddit /r/popular https://farside.link/libreddit/r/popular
Nitter User Profile https://farside.link/nitter/josevalim
Invidious Home Page https://farside.link/invidious
Bibliogram User Profile https://farside.link/bibliogram/u/kbdfans
Whoogle Search "Elixir" https://farside.link/whoogle/search?q=elixir
Searx Search "Redis" https://farside.link/searx/search?q=redis

How It Works

The app runs with an internally scheduled cron task that queries all instances for services defined in services.json every 5 minutes. For each instance, as long as the instance takes <5 seconds to respond and returns a 200 status 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
  • /ping
    • A passthrough "ping" to redis to ensure both app and redis are working
  • /: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 <libreddit instance URL>/r/popular
    • Note that a path is not required. /libreddit for example will still redirect the user to a working libreddit instance

When a service is requested with the /:service/... endpoint, Farside requests the list of working instances from Redis and returns a random one from the list and adds that instance as a new entry in Redis 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.

Development

  • Install redis
  • Install elixir
  • Start redis: redis-server /usr/local/etc/redis.conf
  • Install dependencies: mix deps.get
  • Initialize redis contents: mix run -e Farside.Instances.sync
  • Run Farside: mix run --no-halt
    • Uses localhost:4001

Environment Variables

Name Purpose
FARSIDE_TEST If enabled, bypasses the instance availability check and adds all instances to the pool.