Go to file
shockrah c4d7eb9111 * api::channels::list_channels has more relevant docs
Better matching against return types so we're not throwing away errors
	This just entails swapping the if let for a match statement

* db-lib::Message::send has more updated docs on what variants of Response it returns

* api::messages::send_message has better error logging now and more relevant comments
2021-04-21 17:14:33 -07:00
2021-02-17 17:24:28 -08:00
2021-04-14 22:39:06 -07:00
2020-08-22 18:12:15 -07:00
2020-08-02 21:20:49 -07:00
2021-03-30 12:25:34 -07:00
2021-02-13 16:58:09 -08:00
2021-03-03 17:33:00 -08:00

FreeChat

What this is

A FOSS chatting platform that brings in more modern features that a lot of people have come to expect.

Why not just IRC/Discord/Slack/Mumble etc?

A tonne of IRC channel are basically dead since so many have moved to Discord/Slack. Why? Because those platforms have features that IRC just doesn't have. A lot of people have deemed those features worth the switch.

Discord/Slack are proprietary spyware with no real alternative. The quality of the service is high enough for people to ignore the datamining, it's time a proper client came by.

Mumble could work but has an awful reputation amongst regular non-technical users.

So it's a Discord/Slack clone?

Chat history is limited similar to nearly every chan/booru. This can be turned off to preserve all chat history.

The biggest difference is the lack of data collection; servers collect the following data:

  • User id - generated by the server

  • User password - generated by the server

  • User name - provided by user

  • User chat - How much depends on how the server was configured or if a message was pinned to NOT be deleted.

  • Users Status - user is online/offline: HOWEVER this is controlled by the user.

  • User permissions - To discern admins from less privileged users.

Working Status

Is this finished or almost finished?

Short: The API has basic functionality for chatting but still requires more endpoints to be fully featured. So yes the API at least is in a MVP state. But everything else is either in infancy or not done.

Long: No. A basic client is still underway and the chat API is missing a metric tonne of features. However The state of the chat API is such that it shouldn't be hard to implement many of the desired endpoints.

How to help - if you want to

Check the contributing guide

Description
FOSS Decentralized chat platform
Readme 11 MiB
Languages
Rust 69.1%
JavaScript 12.5%
Python 7.2%
TypeScript 3.4%
Shell 3.1%
Other 4.7%