Hello everyone, here iLxlo_, developer of Filo with a new blog post:
For several months we have been thinking that it was time to update the functions of the Filo API to improve the service we offer. The day has arrived.
We have released the first patches of version 2 of the Filo API and so far it is being a success.
What makes this version different from the previous one?
In this new version of the API we have:
- Strengthening security.
- Improved API responses.
- New endpoints.
- Redesign of Filo’s stats system.
- Privatization of the API. …
Today I come to give you good and bad news about the future of the blog, at least for this year. Here’s the good and bad news regarding Filo’s blog:
+ We have completely redesigned the blog, adding a dark color according to the Filo website (we will no longer damage your precious eyes when you read articles from our blog).
+ We have created a new section (it is still empty) dedicated to announcements and we will be adding more as the days go by.
+ We’ve redesigned the look of the articles in the Developer Notes: Weekly Edition. …
For a few months we have been able to verify that the growth of Filo has been increasing progressively, this has resulted in an increase in the consumption of resources (CPU, RAM).
The Filo’s Development Team has been investigating the situation and testing possible solutions to fix the problem, however none have worked.
We are currently making use of the tools that Discord provides us to avoid receiving events that we do not need. This helped us a lot, but it is not enough to correct the problem.
One of the final solutions to correct this problem is the semi-elimination of the member counter module.
What does semi-elimination of the member counter module mean?
This means that we are not going to eliminate the module completely, we will eliminate part of the functions of said module, parts that influence performance. The functions to be retired are: human counter and bot counter. …
Today we released a patch which completely affected the structure of the settings of each server.
This adjustment has greatly simplified organization and access to these. Linked to this change, we get a zero update of the config command which has had its systematics completely changed.
This zero update of the config command has been made in order to facilitate its configuration using common points, for example, before configuring a report webhook, you had to run the command f!config createReportsWebHook in the channel where you wanted the webhook, now to configure a report webhook you have to run the command f!config …