A daily mirror of Neko's treebird repository https://fossil.nekobit.net/treebird
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
nekobit c2f859d6bd
Remove libpcre from building
5 months ago
.fossil-settings Improved unit testing 8 months ago
dist Update JS 5 months ago
docs Improve docs 5 months ago
meta Emoji picker progress 11 months ago
perl Memory page 5 months ago
scripts JS Emoji picker 9 months ago
src Memory page 5 months ago
templates Memory page 5 months ago
test Stress tests 5 months ago
CREDITS Credits and JS stuff 10 months ago
LICENSE File to C converter 1 year ago
Makefile Remove libpcre from building 5 months ago
README.md Fix JS 5 months ago
config.def.h Load perl 8 months ago


NOTE: This software is not finished. Any bugs are likely noted


Treebird logo

A very lightweight Pleroma frontend.

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.

Treebird uses C with FCGI, mastodont-c (library designed for Treebird, but can be used for other applications as well), Perl, and optional JavaScript for the frontend (100% functional without javascript, it only helps). Uses RE:DOM (2kb JS library) to assist with DOM creation and native JS apis. (Already bundled)


PleromaFE, pleroma's default frontend, uses way too much Javascript to be usable (and doesn't even support all of it's own API features...). BloatFE is great, but designed only around Mastodon's api, and isn't as modern or as lightweight as it could be. Soapbox is soapbox and does soapbox things.

This led me to one choice, to develop my own frontend.


Treebird respects compatibility with old browsers, and thus uses HTML table layouts, which are supported even by most modern terminal web browsers. The core browser we aim to at least maintain compatibility with is Netsurf, but most other browsers like GNU Emacs EWW, elinks, render Treebird just alright.


Please view the CREDITS file.


See INSTALL.md for instructions on Apache/Nginx.