40351f934e
Interface for this is fiddly and probably requires real docs to be further developed without losing my mind doc the whole cache at some point + New cache ipc handlers for adding a new open web socket Web socket comes with some basic listeners, however very litte/nothing is being done check the health of these connections or to try when possible. + Cache now adds actual message objects to its message arrays instead of raw strings (wew) + Events module has been added to move the parsing logic/validation away from everything else + The basic Event structure has some niftier-than-you-think behavior for data acccess which the cache can leverage for more concise+ correct behavior |
||
|---|---|---|
| chan-like | ||
| docs | ||
| freechat-client | ||
| invites-manager | ||
| json-api | ||
| misc | ||
| rtc-server | ||
| scripts | ||
| tui | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| contributing.md | ||
| docker-auto-build.sh | ||
| LICENSE.txt | ||
| readme.md | ||
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