Expose user lists via CalDAV.

[RokeJulianLockhart]

Describe your suggested feature

This application allows the user to create "to watch" and "watched" lists. However, these cannot be accessed by the user in a uniform manner with their other tasks lists. This is problematic for me, because it prevents me knowing cohesively what I still have yet to watch alongside the things that I track elsewhere (for instance, if unavailable via this application).

Other details

Would depend upon #549 (comment), I expect.

bookwyrm-social/bookwyrm#2952 (comment)

Additional context

Read-only exposure would easily be enough for me, at least for now, because it would still allow me to easily see offline what's in each list, although it wouldn't allow me to cache offline changes to later be applied when online, like modification support would.

Relevant:

0. https://gitlab.com/gitlab-org/gitlab/-/issues/14390
1. [FR] Add CalDAV support. taigaio/taiga-back#128 (comment)
2. [Feature Request] Task support (CalDAV?) raindropio/app#82 (comment)
3. [Feature Request] Expose lists via CalDAV. wishlephant/wishlephant-website#1 (comment)
4. [Enhancement] Expose user lists via CalDAV. bookwyrm-social/bookwyrm#2952 (comment)
5. Expose wishlist entries as CalDAV tasks. ValveSoftware/steam-for-linux#10019 (comment)

Acknowledgements

• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I will fill out all of the requested information in this form.

[recloudstream]

Hello rokejulianlockhart.
Please do not report any provider bugs here. This repository does not contain any providers. Please find the appropriate repository and report your issue there or join the discord.

Found provider name: Stream1

[self-similarity]

The lists are exposed to extensions and through backup, it would be very easy to write an extension to make an automatic backup or export the list in any manner you like. It is not worth spending development time implementing CalDAV due to this in my opinion.

[RokeJulianLockhart]

@self-similarity, #550 (comment)

The lists are exposed to extensions and through backup, it would be very easy to write an extension to make an automatic backup or export the list in any manner you like

Those can't be updated in real time, however, nor can they be managed in a cohesive manner, such as DAVx5.

Anyone with more than a few films on their watchlist simply can't use the in-built list functionality without some way of synchronizing it with their other lists.

[C10udburst]

Those can't be updated in real time

🤨

[RokeJulianLockhart]

#550 (comment)

@C10udburst, I manage my watchlists throughout the day because I'm a bit of a nerd. My sister does the same, because she's studying film at university. Those two use cases require that the list always be up-to-date. Managing backups simply isn't feasible in that case. Also, anyone not technically competent simply wouldn't bother to consume the backups, whereas a simple CalDAV URI is significantly easier to manage (via DAVx5) (even if it's a local content: or file: URI).

[C10udburst]

DAV would be very niche feature - not many people even know what DAV is. So i feel like it would work much better as an extension. While technically not real time, I don't think it matters that much whether the update happens while in app or after you close it.

[RokeJulianLockhart]

DAV would be very niche feature - not many people even know what DAV is.

I think you'd be surprised, @C10udburst. A great many normal people use lots of calendars and calendar sync services. Even the aforementioned niche synchronizer https://play.google.com/store/apps/details?id=at.bitfire.davdroid&hl=en&gl=US has a good few hundred thousand installations from just one source (it's more popular at https://f-droid.org/en/packages/at.bitfire.davdroid/ because it's free there, but that source doesn't track installation metrics because they're morons).

I'd say that that amount of people is comparable or more than the amount who use Cloudstream at least, right? And there would definitely be overlap in the userbase. At the very least, without it, I'm sure you understand why Cloudstream's built-in list tracking functionality is a bit useless to a lot of people, and that any other option would require more development time and be less versatile and convenient.

So i feel like it would work much better as an extension.

I like that idea. The more modular the better, eh? However, I'm unfamiliar with the concept of a Cloudstream extensions. I see that providers are manually installable, but I don't see anything in the app's GUI that allows a user to manage extensions.

While technically not real time, I don't think it matters that much whether the update happens while in app or after you close it.

That all depends upon how many changes are made and why. Indeed, it not being real time would suit most use cases, although it'd be a bit silly to do the work to implement support and not have it real time. At the very least, the current backup format isn't (exposed as) a standard consumable local DAV server.

[Blatzar]

but I don't see anything in the app's GUI that allows a user to manage extensions.

Extensions can provide a button which opens a completely extension based UI in which the extension can do whatever it wants. Few extensions need this which is why you might not have seen it. In this hypothetical UI you could configure the CalDAV settings however you want.

At the very least, the current backup format isn't (exposed as) a standard consumable local DAV server.

I think backup was made as an example in this case, not the be-all and end-all. Extensions run arbitrary code and I do not see a reason they could not expose a live DAV server.

[RokeJulianLockhart]

That's brilliant to hear. I wasn't aware that Cloudstream had such a robust extension system! It sounds like the perfect solution.