A daily mirror of Neko's treebird repository https://code.nekobit.net/fossil/treebird/home

Find a file

me@ow.nekobit.net b6fcd4b05d Set client_id and client_secret FossilOrigin-Name: df7cc4b2205a6ff3aca9c7d8abdc93ab2aa34af3b3b07d7ed7450b9d4b6eb375		2022-02-15 20:36:16 +00:00
dist	Login page	2022-02-15 02:56:16 +00:00
meta	Index and meta	2022-01-17 06:19:46 +00:00
src	Set client_id and client_secret	2022-02-15 20:36:16 +00:00
static	Login page	2022-02-15 02:56:16 +00:00
.gitignore	Mastodont load	2022-01-20 04:45:33 +00:00
config.h	Change config option	2022-02-11 04:31:24 +00:00
LICENSE	File to C converter	2022-01-16 22:43:16 +00:00
Makefile	Login page	2022-02-15 02:56:16 +00:00
README.md	Initial	2022-01-16 05:39:07 +00:00

README.md

RatFE

A pleroma frontend for rats.

The goal is to create a frontend that's lightweight enough to be viewed without JS, but usable enough to improve the experience with JS.

RatFE uses C with FCGI, mastodont-c (another library that complements RatFE) for communication, and plain JavaScript. It also uses sqlite3 to store any user-specific information and groups.

Isn't FCGI outdated?

No.

Isn't Sqlite3 slow?

No, in fact, it may likely be faster than if it were using postgresql. The pleroma server communicates using postgresql because there are lots of incoming requests and outgoing requests on the server, and there can be multiple requests at once occuring, which get queued. We don't need that kind of speed and we shouldn't interfere with it anyway.

Plus, Sqlite3 is only being used for user groups and possibly some session information.

Rat?

Rats are c00l.