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

Find a file

me@ow.nekobit.net 2e7d660001 Lots of theming, switch to tables, 1.0 theme (kind of broken) FossilOrigin-Name: 85a54793932f8c64100306d0256946770b89396afb9f603bb11de8398a1c4337		2022-03-01 20:36:20 +00:00
dist	Lots of theming, switch to tables, 1.0 theme (kind of broken)	2022-03-01 20:36:20 +00:00
meta	Index and meta	2022-01-17 06:19:46 +00:00
src	Lots of theming, switch to tables, 1.0 theme (kind of broken)	2022-03-01 20:36:20 +00:00
static	Lots of theming, switch to tables, 1.0 theme (kind of broken)	2022-03-01 20:36:20 +00:00
.gitignore	Mastodont load	2022-01-20 04:45:33 +00:00
config.h	URL Prefix, skeleton theme, fix flat theme	2022-02-22 19:24:41 +00:00
LICENSE	File to C converter	2022-01-16 22:43:16 +00:00
Makefile	Display emoji reacts	2022-03-01 04:30:51 +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.