็ฎไฝไธญๆ
EnglishWhat Is rimgo.codeberg.page?
Updated
rimgo.codeberg.page is a directory page for rimgo instances. It presents a random selection entry point and lists public instances grouped by network type: standard instances, Tor instances, and i2p instances. It is not itself a full rimgo frontend for browsing content; it is the page you use to find and pick an instance. If you already know which instance you want, you can skip this page entirely. If you want a privacy-friendly alternative frontend and don't know where to start, this page is the starting point.
What the page actually offers
The page is organized around four headings:
- ๐ฎ Random Selection โ a single entry point that sends you to a randomly chosen instance.
- All โ the general list of public instances.
- Tor instances โ instances reachable only through Tor.
- i2p instances โ instances reachable only through an i2p-configured browser.
The page's own description states the trade-off directly: Tor instances "provide improved privacy but require the use of Tor Browser," and i2p instances "provide improved privacy but require the use of a browser configured to use i2p."
Choosing between the three groups
| Group | Reachable with | Privacy level | When to use it |
|---|---|---|---|
| All | A normal browser | Standard | You just want a working instance fast |
| Tor instances | Tor Browser | Improved | You want traffic routed through Tor and already have Tor Browser |
| i2p instances | A browser configured for i2p | Improved | You already use i2p and want to stay inside that network |
The key decision is not which instance is "best" but which network you are already set up to use. A Tor instance is useless if you open it in a regular browser, and the same applies to i2p instances. Match the instance group to the browser you actually have.
How to use it
- Open rimgo.codeberg.page.
- If you don't care which instance you get, use ๐ฎ Random Selection.
- If you want a specific network, pick from All, Tor instances, or i2p instances according to your browser setup.
- Follow the instance link and use rimgo from there.
Expected result: you land on a working rimgo instance rather than a dead or unreachable one.
Common sticking points
- Using a Tor or i2p instance in a normal browser. It will not load. The network requirement is real, not optional.
- Treating the directory as the service. This page lists instances; the actual frontend behavior happens after you follow a link.
- Assuming all instances behave identically. They are separate deployments, so availability and uptime can differ. If one fails, try another from the same group.
The short version
Use rimgo.codeberg.page when you need to find a rimgo instance and don't have one bookmarked. Pick Random Selection for speed, All for a standard browser, or the Tor / i2p groups if you already run those networks. The page's only job is to get you to an instance that matches your setup.