Skip to content


My feedback

1 result found

  1. 29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Wishlist » Events  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    matrudon commented  · 

    This, but from my (limited) experience with ICS I would add a few points that make it a bit more complex:

    The link should be public, calendar apps have (at least most of them) no ability to sign in to your app.

    Since the link is public, it should be impossible to guess or you're leaking user events to the whole world (in some cases it might be ok, but in most it's not). For example, /users/1/calendar.ics is not a good url, because it's easy to get someone else's id and fetch their calendar.

    You should provide a way to reset a calendar link if it leaks somewhere

    Because you can't control in how many calendars the user will subscribe and how often they will query your endpoint, it might be a good idea to pregenerate ICS file and store it somewhere like S3 (with a CDN in front) so you don't have to worry about multiple requests putting a strain on your server.

    You have to figure out what to do with past events. If you decide to keep them in ICS forever, the file might grow quite big. On the other hand, if you only put future events and past ones from e.g. last week, things will disappear from users' calendars, so you need to make sure it's ok.

    edit: typos

Feedback and Knowledge Base