Skip to main content

Blog

Keep an eye on this page to stay informed about important changes to frei.chat.

2024-01-19 Workers up again

The workers problem has been solved and they are up again. Maybe you have experienced slow message / media transfer to external servers, if not I'm happy it went all good over the last days. Especially mobile apps have sufferd from that single worker setup with log loading screens (> 2 or 3 seconds).

Now with workers there shouldn't have any of these bad latence and messages / media should arrive much faster. The mobile apps should also sync faster when you open the app after a longer time.

2024-01-16 Troublesome day

Today I decided to update to the new Traefik configuration. Unfortunately, this proved to be a major problem.
The configuration in the playbook is still quite young, but since I had good results on my test instance, I took the step. Unfortunately, I discovered that the frei.chat setup is currently not compatible with the configuration.
The problem was the current worker configuration, which splits up certain background processes and is supposed to provide better performance. Unfortunately, Traefik doesn't seem to be configured correctly for the workers to function correctly. Unfortunately there were a few restarts today because the error was difficult to reproduce.
After a few hours of troubleshooting, a delicious, energizing tiramisu and two hours of sleep, I tried it again and was able to narrow down the source of the error to the workers. The setup will now run again on the non-worker setting until the problem with the workers has been resolved.
Please excuse the many restarts.

I also decided to limit the retention time to 7 days for local and remote media. But uploads of up to 250MB in size are now possible. Profile pictures are not affected.

There are no updates... Had a configuration issue which went online. There is no change but you still have to consent again. Sorry!

Additionally I've added history information to the Privacy Policy and Terms of Use pages. No other changes were made to the pages at all!

Update 17:30 Uhr

The developer of the playbook changed some variable names which manage the port definition for internal services. Had to deploy twice to find the correct combination. Therefore frei.chat was unavailable a bit longer than usual during restart.

2024-01-12 Trying to fix MatrixHQ states

Some weeks ago ppl tried to join the huge MatrixHQ room on matrix.org. This room is

2024-01-09 New website logo, First steps and updated pages

Todays announcement is about presenting the new frei.chat logo and informing about a fresh update of most of the pages, like Bots, Bridges and Services.

If you would like to link frei.chat on your website, you can of course use the logo in conjunction with.

frei.chat now has a new public space for RSS feeds. Each room is assigned a feed and updates once an hour.

The Postmoogle bot allows every user to receive and send emails via frei.chat. The Bots page describes what you need to do for your personal email address.

I have created a "First steps" guide on how to start on frei.chat for new users.

2024-01-06 Revision of the website

I've been working on redesigning the frei.chat website for a few hours now. I switched from the mkdocs for materials software to Bookstack, which makes working on the individual pages much easier.
In addition to updates to the Bridges, Bots and Services pages, illustrated instructions for the first steps to your own frei.chat account have now been added.
In addition, you now have a clear overview of the changes to the frei.chat server on the announcements page.

2024-01-05 Update of the Signal bridge bot

Singal

If you want to have all Signal chats in you very own Signal space you have to run the command !signal sync-spaces in you personal Singal management room.

Maubot

The new maubot can be invited in every unencrypted room. It response to many commands and mostly used for fun actions.

2024-01-04 New Signal bridge bot

The new Signal bridge was installed on top of the existing installation. All devices which have been connected before the 3rd of January 2024 needs to be re-linked manually. Every command has to start with the prefix !signal so talk to the bridge bot.

In case you have problems with the Signal bot please kick the user @signalbot:frei.chat out of the management room, leave that room, create a new unencrypted room and invite the bot again.

Back to top