FOSS Decentralized chat platform
Go to file
shockrah b289f5c811 * Fixing /badge/update/name parameters for basic test
Basically we weren't sending the right data to prompt a 200 response

!!! the /badge/delete test is breaking previous tests idk why
Even though this test comes close to last it still manages to break
the tests that come before it. The problem may lie with the fact that
because its a much faster route by design that its e2e latency btfo's
the routes before it, allowing it to finish before they do.
This likely causes a race condition.
2021-06-07 23:53:49 -07:00
chan-like new job for channer build 2021-02-17 17:24:28 -08:00
docs ! Finsihed goal on roadmap 2021-05-12 15:00:39 -07:00
freechat-client * messages.recent_messages now uses the /message/recent 2021-04-27 13:40:12 -07:00
invites-manager ignoring sample env file 2020-08-22 18:12:15 -07:00
json-api * Fixing /badge/update/name parameters for basic test 2021-06-07 23:53:49 -07:00
misc updated logo 2020-08-02 21:20:49 -07:00
rtc-server + Adding commandline parameter parser for specifying wss-hmac and api-hmac 2021-04-27 13:24:59 -07:00
scripts - Removing rtc parts for th pure api testing 2021-05-29 14:35:13 -07:00
tui - Removing more behavior from the cache for complexity reduciton 2021-04-14 22:44:57 -07:00
.gitignore Ignoring secret hmac files 2021-04-25 12:40:53 -07:00
.gitlab-ci.yml * Fixing issue where a rougue popd broke the whole job 2021-05-12 16:19:41 -07:00
.gitmodules Submodule for wiki theme 2021-02-13 16:58:09 -08:00
contributing.md More background information regarding what can use the help or not 2020-12-12 16:36:40 -08:00
LICENSE.txt Updating base license to GPL3 2021-03-03 17:33:00 -08:00
readme.md + Adding roadmap 2021-05-08 21:28:43 -07:00
roadmap.md * Moving rtc calls to build under rtc feature flag 2021-05-17 14:49:01 -07:00

FreeChat

Roadmap

For a more detailed write-up on where the project is going check the roadmap

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