Field DTSTAMP in iCal contains wrong value

[dasniko]

The field DTSTAMP in our iCalendar stream (events.ics) contains a wrong date value.
Currently it contains the event date itself, but it should contain the last modification time of the event.

First, I thought I could solve it with a custom Jekyll plugin to read the file modification time. This works like a charme locally, but GitHub Pages restricts the usage of custom plugins "due to security concerns".
So, I don't see an automated option at the moment.

A possible solution (or workaround) could be to maintain a frontmatter attribute manually in each talk file. But that needs manual attention everytime the event is updated.

The implication of not having a proper DTSTAMP value in our iCalender stream is, that iJUG won't publish our events on their Mastodon account.
Personally(!), I don't care about that as I still don't see the importance of Mastodon today (compared to Twitter in good old times pre-Musk).
So, I leave up the possible solution to someone else... Feel free to provide a proposal.

(the same is relevant for the Cyberland website/ical feed)

[ascheman]

I would like a better understanding of the underlying problem: We should update the DTSTAMP whenever we change the event? One purpose is to allow proper Mastodon announcements by iJUG? Do we have more information about their intent or why it imposes a problem there?

However, the issue reminds me of a problem I never issued. Once published (and imported into my calendar via my subscription to the published events.ics file), I never see updates on it, even if the event changes, eg., if the location is changed. Could that be the same reason?

[dasniko]

iJUG uses a new software to automatically publish appointments from JUGs to their Mastodon channel. This software seems to be very restrictive to RFC of iCalendar.
If this is the same cause for your local issue, I can't tell, I never experienced issues here. "Works on my machine"