Reminders lost when schedule updates

[MI-KY]

Hello,

I recently had this problem multiple times and therefore I wanted to ask: is it possible that Giggity looses all reminders set on various talks every time the schedule .xml is updated?
I had many reminders set for a conference and after some day when I reopened the app I saw the messagebox that the schedule gets loaded again (with the option to use thr cached version) and afterwards all my reminders where gone...

I retried to set reminders and after some day the same happened.
I don't know if the .xml has been updated and this forces Giggity to delete all reminders, but it's a bit hard to loose "all the work"...

[Wilm0r]

That definitely sucks, and is definitely not how the program was designed :( Which conference was this? If they didn't publish the schedule data properly this could happen, especially if it was an iCal file..

[MI-KY]

It was the SFSCON 2024 and happened also a year or two before. I can imagine that this has todo with some changes of the data. Also their official app deleted once all the reminders but when that happened Giggity did not... Am 14. Dezember 2024 02:56:07 MEZ schrieb Wilmer van der Gaast ***@***.***>:

…

That definitely sucks, and is definitely not how the program was designed :( Which conference was this? If they didn't publish the schedule data properly this could happen, especially if it was an iCal file.. -- Reply to this email directly or view it on GitHub: #392 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[Wilm0r]

Hrm, without snapshots of their schedule it'll be harder to explain this one, but I've saved a version of the file now, let's compare in a few weeks and see if the id's change randomly.

This does seem to be Pentabarf/frab data from a generator I've not seen before, guessing from the URL.. And this also looks odd: <event id="672dacda313f371e89446fb96a90ef5476947cbdfe1ef" unique_id="2024day2event11" bookmark="0" rating="0">

The unique_id attribute looks helpful by name but then what happens if a new event gets added in between 2024day2event10 and 2024day2event11, are the names unique and ~permanently attached to an event or only unique and nothing else.. :)

(But more importantly, Giggity does not know of that unique_id attribute at all anyway, and the question is, does the unique_id field already suggest that the other plain id field is not unique in a useful way?)

[MI-KY]

Hi, maybe something that could help you: had exactly the same thing happening today with the congress 38C3 (https://fahrplan.events.ccc.de/congress/2024/fahrplan/schedule/export/schedule.xml). Had marked some talks yesterday (worked also correctly the whole day) and today when i opened all the selections are gone.

[Wilm0r]

Oof, sorry that sucks 😔 Just to be sure, you've not mixed up the base and the merged CCC schedules?

[MI-KY]

Oh man, I'm sorry! This time it was my fault because 38c3 has two entries in Giggity and i took the wrong one today. Sorry again!

[Wilm0r]

Pfew, glad I guessed that one correctly :)

It'd be nice to have a better way to deal with variants like this and share selections properly. With UUIDs as identifiers theoretically it could just store them all together. Let me think about that for next year!

[MI-KY]

Thanks a lot! And generally thank you sou much for your helpfull app :-)