BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.gulas.ch//gpn24//talk//38ZLSX
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-gpn24-38ZLSX@cfp.gulas.ch
DTSTART;TZID=CET:20260606T223000
DTEND;TZID=CET:20260606T233000
DESCRIPTION:I just wanted Zulip notifications on my phone. So I started bui
 lding something myself - and fell into a rabbit hole.\n\nThis talk tells t
 he story of how I tried to solve a problem - and in doing so\, understood 
 how push notifications actually work. Why my first approach didn't scale. 
 Why almost every app uses Firebase or APNs. Why even Signal knocks at Goog
 le's door. And why\, since the Wyden letter of 2023\, this is a documented
  privacy problem: "We kill people based on metadata."\n\nI'll show what al
 ternatives exist with UnifiedPush and ntfy\, how I built a bridge for Zuli
 p\, and why the same problem applies to your Prometheus alerts\, Grafana n
 otifications\, and CI/CD pipelines. And what all of this has to do with di
 gital sovereignty.
DTSTAMP:20260516T173209Z
LOCATION:ZKM Kubus
SUMMARY:Why Even Signal Calls Apple & Google - Merle
URL:https://cfp.gulas.ch/gpn24/talk/38ZLSX/
END:VEVENT
END:VCALENDAR