It would be interesting to have multiple way to see the event depending on the user preferences:

• List with description (this is the current state)
  • compact version
• Grid with images (require #9 to be done first to avoid void)
• Sorting by date, see the next 7 days events, next 31 days events, the current week event, the current month event
• Sorting per language (require #11)

It would be nice to update the configuration file for having the option communities_url where:

communities_name = ['Commu 1', 'Commu 3']
communities_url = ['http://example.com', 'http://example.fr']

So the url of Commu 1 is http://example.com and for Commu 3 its http://example.com

Note old idea that I put somewhere else that i forgot to make an issue for

Like G-Neos-Mentor-Team:G-Neos-Mentor-Team.Calendar maybe?

Note old note that was not made as an issue

It would be interesting to have language information per event. For now all events on https://resonite-communities.com are in English but their is already an japanese calendar. If we want to also show their event here it would be interesting to have the language information link to the event.

Adding this would require to change the events to show based on the current region of the user defaulting to english if the region of the user is unknown.

It seems that the animated icon are not really well supported on the web client but works after a force refresh...

Problem

On the web client https://resonite-community.events/ the date show 2022 instead of 2023

Explanation

The year is hardcoded

Solution

Do not hardcode the date

For now it's not clear of how to add the bot to a discord server from the website. Their is a link to the about page but that's all their is no information clear.

It would be best to add explicitly an information to contact brodokk (and only brodokk since GrayBoltWolf will just redirect to brodokk instead).

It's seems today that the bot can be easily added and since their is no really setting to set an easy link should be on the website.

It seems like some event stay in the redis cache even so it has been restart. The perfect solution would be to fix that during the rewrite.

The structure of the project is not good and slow the development of new feature on top on not being clean.

Problem

Some time an events appear multiple time, spamming the list, growing every hours and can take down frames on Resonite client.

Explanation

Because of simplicity of the API for Resonite, the first version of the API has been made based on the name of a community. Which is a big mistake if the name of the community change.

Possible solution

We need to use an external ID, or an internal ID, for now communities only use discord calendar but their is a system to manage event via a bot and google calendar.

The current system for manage the image is not perfect, it would be nice to have:

• a placeholder background image for an event if their is none
• a placeholder image for a community if their is none
• repeat the image background by themself to keep the same resolution for the image even if the resolution is different

When the server name is changed and the configuration is out of date the events are added multiple time.

A solution possible would be to log about it and not update any events.

For now for getting communities information and streamer information a full restart of the application is necessary.

It would be interesting to have:

• An auto reload of the configuration file somehow
• Update from different API like discord or twitch

Note: For now, no known client is using this v2, so it's not yet frozen

It will be only useful if a discord server have a lot of events but it could be cool to have the bot generate a list of events for the following week in a one simple and condensed block.

A bit like https://chroniclebot.com/ is doing

Problem

When an instance is connected to another instance it will show the event multiples time growing every hours and can take down frames on Resonite client.

Explanation

The last update have some code refactored and not everything have been fully tested, like the fact that one instance will look at another instance events to also list them on the current one. The idea behind this update was to list the communities available on the instance.

Possible solution

Update the code to handle the new API format.

It would be interesting to output the calendar into a google agenda.

The question is how make people able to subscribe to some communities event and not all of them.

Either with tags or separated calendars

Problematic

As for now either the title, the description, or the location of the event must contain the word Resonite for the event being returned by the API. But if this not the case the service failed with an error. Not sure if the process also die but it seems to be the case

Solution

Just ignore and log the error should be enough

Note old note that was not made as an issue