Mark Niemeyer
That is also a valid approach and it would simplify the code, but then we are limited to this one functionality. If we wanted to add another functionality*, we would...
I wasn't aware of the possibilities of the fragment. I agree, we really should use the fragment. Do you have any suggestions how to store it in the fragment, so...
Yeah, that was really the obvious solution. The input of the `parse_qs` function is now the fragment instead of the query string. The delimiter is therefore the `&`. The latest...
The approach of the structured input is taken from the authentication for _basic auth_ via url (https://stackoverflow.com/questions/4980912/username-and-password-in-https-url). Nextcloud calendars are also accessible like [this](https://help.nextcloud.com/t/how-to-access-the-calendar-ics-file-via-url/7880/2). I tried to change as less...
The approach of #187 could also be adapted for the username and password. Instead of `http://username:[email protected]` two query key words like `inky_user` and `inky_password` could be defined. But I still...
> Yes, the settings.json is not a safe space for secret things in my opinion. I think you really have to weigh the consequences. Yes, it is a security issue...
And as an example for the necessity of this: Those users who host their calendars in their own Nextcloud cannot create a public link for the birthday calendar of the...