Itʼs amazing how much research was put into storing recurring events.
Itʼs also amazing how complex this seemingly simple process is.
Iʼm almost done with the list of active sessions. It was a really interesting thing as I never did anything similar with Flask before. I also didnʼt find any existing solutions I could use (and will probably publish it as a separate Flask extension later.)
This also means I had to implement caching (although Iʼm not sure yet if the cache is the right place to store session data in) which also opens up the way for a lot of other things.
Anyone who tried to open an account on gitea.polonkai.eu, please request a new confirmation email; I had recently added a typo to my SMTP configuration.
Sorry for the invonvenience!
Privacy advocates, I’d like to ask for your help. What kind of privacy settings/features would you expect from a calendar application? Don’t mind if it’s already done in Calendar.social or already documented as an issue; I would really like to see the whole picture!
Response visibility can soon be set based on who is looking at the response list. E.g. if you set the response visibility to followers only, a random stranger won’t see if you are attending an (otherwise public) event.
Question: is a random stranger responds “going”, should they be handled as followers in this case? What about “not going”. And to complicate it even more, what about “maybe going”?
You can now create private events, which are visible only to invited people.
Whoa, it looks really bad on mobile…
Say hello to the new welcome page! If it feels like the copy of Mastodon’s About page, it’s not a coincidence; I’d be grateful if you would send me ideas on what should go there or how to change wording.
As captioning this image would be enormous work, I will soon fire up an instance with registration disabled, so people with low vision can check it out.
I just merged the UI facelift using Semantic UI. Itʼs still not beautiful, but much more pleasant for the eye.
this leaves Semantic, Bootstrap, Milligram, and Bulma in play. I’m strongly in favour for Semantic right now; that required the least modification to the designless pages and thus I find it really comfortable.
And here are the Semantic ones. This was the easiest to achieve (in terms of modifications needed for the plain no-design.)
Here are the milligram screenshots. I make an educated guess: this will be the harder to make it look right on mobile.
Seems like Jinja and Materialize are not close friends. Right now I can’t even make the time zone field to display, so I think I’ll try it later 😞
Here are the Bulma screenshots; I guess I will have to work a lot on the calendar view on mobile regardless of the framework…
And here is one with Bulma (again, not much work in it.)
There you have it, in no particular order.