A daily mirror of Neko's treebird repository https://code.nekobit.net/fossil/treebird/home
Find a file
me@ow.nekobit.net 31efb281a4 Query parser
FossilOrigin-Name: fb3dec10d90e0beac45bcef20f4f0b7ba9fcc1a446d602e4484a0d0fa5a9e856
2022-02-01 03:10:09 +00:00
dist Config page 2022-02-01 00:19:04 +00:00
meta Index and meta 2022-01-17 06:19:46 +00:00
src Query parser 2022-02-01 03:10:09 +00:00
static Query parser 2022-02-01 03:10:09 +00:00
.gitignore Mastodont load 2022-01-20 04:45:33 +00:00
config.h Fix mastodont include 2022-01-19 05:07:30 +00:00
LICENSE File to C converter 2022-01-16 22:43:16 +00:00
Makefile Config page 2022-01-31 22:22:48 +00:00
README.md Initial 2022-01-16 05:39:07 +00:00

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.