Table of Contents
Fediverse (Federation system)
Introduction
OASIS contains its own Fediverse module, a bridge that lets you connect and manage your accounts on other federated social networks — starting with Mastodon — directly from inside the network.
The main idea behind this implementation is to send and receive content across the Fediverse without locking you into a single platform and without storing any third-party data in your append-only log. Your timeline is fetched live and rendered on the fly, so OASIS stays light while you stay connected to the wider federated world.
How it works (rules)
- Nothing third-party is stored: Remote posts are requested live for each visit and shown ephemerally. They are never written into your `.ssb` feed, so your log is not filled with other people's content.
- Local credentials only: Your access token is kept in a local, private configuration file. It is never published to the network, never committed to any repository, and never shown back in the interface.
- Privacy by default: Every outbound request uses the same uniform browser headers for all OASIS users, so no per-user metadata leaks and the origin is protected.
- Proxied media: Remote avatars, images and videos are fetched through the OASIS backend (hiding your IP) with anti-SSRF protection. Remote HTML is always sanitized before display.
Purpose
The Fediverse module of OASIS is not merely a Mastodon client — it is a statement about how federation should feel from a libre, privacy-first network.
By letting you reach the wider Fediverse without surrendering your data, your metadata or your attention, it treats other networks as peers rather than silos. Remote content stays ephemeral, your identity stays yours, and your origin stays hidden — yet you can still participate fully in the global conversation.
Ultimately, its purpose is to connect OASIS to the rest of the federated world on the community's own terms — sending and receiving content freely, while keeping the network light, private and humane as it grows.
