Emilien

I've implemented all the bot's features:
- Subscribe and unsubscribe from a list to get found by people
- Stop a discussion whenever you like
- Be able to change your username: by default “Anonymous”, you can change it with the command /username <username>. So you can use a fun nickname or reference :3
- Level system : The more you talk, the more levels you have, the more features you can use.
- Sending attachments (Only available from level 3 upwards)
- Native voice message integration (Only available from level 5 upwards)

I've implemented a whole system of accounts, groups and objects in order to have a clean and efficient API.

First of all, I added an account system to let the user choose his api key and root api.

Then I created a route to retrieve entities compatible with the API, and an object system to simplify requests to Home Assistant.
At first I made POST requests on the state of the entities, but having encountered certain bugs, I use the Home Assistant ‘turnoff’ and ‘turnon’ services to avoid bugs.

I've also added a group system, so that the user only has to make a few requests to turn off a large number of devices.

I've started the display, I've decided to do it in Rust, at first I was going to do it in Go but due to the complication with Golang, I'm doing it in Rust.

I'm using the GTK Layer API to put it on top of the other windows.

The details page is dynamic :3

The front end is now dynamic : I make requests at mail.hackclub.com to get information.

I finished the backend, I added the selected menu.

I've started on the frontend, adding a mail list (not yet dynamic) and a help menu.

I've added two commands: one to display the list of challenges, and another to clear the challenges in the database (reserved for the bot owner).

I've added the main function: retrieving challenges and sending messages when a challenge has been solved or not.

I started the bot, and added two commands: subscribe, and unsubscribe, which allow the user to subscribe to the feed, to send them messages when a challenge is solved, or when a challenge has been added.

I have added a README and some edits to finish the portfolio :3

I've added a system to view CTF or Hackathon certificates, for those who provide one.

I've added an internationalization system: I just have to add a file, to add a possible language, and I can just change the translations whenever I want in these files. For the moment, I'm only using French and English.

I've simply added the ability to easily change site data: rather than modifying the code directly, I just have to create or modify a file to change the list of my projects on the site.

I've also changed a few margins on the frontend.

I've started on the frontend: I've added my profile picture, the projects, events and social sections.

I've simply added a help menu and a README to simplify installation of the project.

I've added the parameters: now the main functionality is done.

I rerefactored the color system, to have a Get function where you just supply an enum value to get a color

I've refactored the flag printing system: instead of having a function to print each flag, I have a function to retrieve the flag colors, and a function to print the flags.

I've also added... lots of different flags!

I've added the “basic” flags: Lesbian, Gay, Bisexual, Transgender

I made a little PoC who print the bisexual flag :3 (my flag !!!)

I made a few modifications at the end of the project: I had a friend test the interface for feedback (which revealed a major problem).

So I changed the font to a static font, not just any monospace font. I also redid the responsive a bit so that it would work with the static font.

I've written the READMEs, but I've also added functionality to remove the servers from the database.

I've finished automatically updating the data on the stats page.
But I've also added a demo mode for the site.

I've started the backend of the page where you can see the statistics. I opted for a double data retrieval: one source coming from the project API, so as to have an almost instantaneous loading, then the other coming from a websocket sending the data every X seconds.

For the moment, I've only done the API part, to ensure clean loading and all the functions needed to easily integrate the websocket.

I've started the stats display interface. On PC, the interface will look like this. I've decided to use ASCII graphics to keep the style minimalist.

For the moment, this is just the front-end, as the back-end to display all the stats has not yet been integrated.

The next step is to make the interface... responsive.

I've added very little visually, but a lot on the backend.

I made the server list page functional, with a modal to retrieve the connection token. I've added the page for adding a server and the page for changing its password.

I've also added better management for the icons used in the project. I used custom elements in HTML to create a simpler icon system to avoid repetition.

I've also started a websocket, to update live information from the servers.

I started doing the client's backend and frontend. I decided to use Elysia, in particular so as not to slow down server development because I'm used to this framework, but also for server performance, Elysia having very good benchmark results.

For the frontend, I decided on a minimalist design to simplify use of the service, and because I'm not very good at design.

This is a little devlog to show my log system in Go, inspired by the log library I use in the client (logtape).

I've also added a system reconnection when the TCP connection is lost.

I've finished the socket, all the data is saved in the database. The translation part is finished.

I've also added a function to clear the database: every 10 minutes, all data older than 10 minutes is deleted.

The next step is to create the interface and a user system, and then run a websocket to receive information in real time.

I've started the translation part, which retrieves information from a TCP server and stores it in a database. For now, it only handles authentication and CPU name registration.

Each message sent to the server must be a JSON composed of three keys: Id, which corresponds to the server id; Type, which corresponds to the type of message (authentication, cpu name, cpu usage etc.); Data, which corresponds to the data to be stored.

For authentication, you need to provide a key and an id. This assembly of key and id is called a token, and is encoded in base64, which simplifies client installation. The key is generated by a SHA256 signature, encrypted with HMAC and a key specific to the server. This guarantees the authenticity of the data, to prevent a malicious person from sending false data to the server.

I've just added network statistics (bandwidth), i.e. the number of bytes sent and received in x seconds.

I tried to integrate CPU temperature but it's a bit more complex, maybe when I've finished the basic program.

I've added several features to the PoC: recovery of the CPU model name, and recovery of disks and its statistics.

Disk read doesn't just read mounted files, but will read every available disk, look to see if it's mounted, if mounted, retrieve the name of the folder where it's mounted, and retrieve the available size.

Both are based on linux system files: /sys/class/block (a folder) which has an equivalent folder on each disk, and /proc/cpuinfo which lists CPU info, including its model.

The basic plan was to make the server in C, but I finally decided to make it in Go, for the simple reason that Go is simpler and I don't have too much risk of memory leaks.

I started by making a PoC with the main information, such as CPU usage in percentage, memory info and swap info.

The most complicated part was CPU usage, because you have to read raw information, which means nothing when you don't know how to do it. Thanks Stackoverflow.