Trying nextcloud again (I gave up on v26 ish due to lack of time to work out why nothing would work)
v30.0.2 seems a tiny bit more stable.
Any news on federated calendar sharing?
AFAICT it’s been stalled since ~2016
Are there any plans to implement this? Sharing a “public link” is both insecure and read only.
The only secure “solution” is for my phone to have both nextcloud accounts (one from each server) on it, which is a horrible solution, since I can’t see both calendars in the NC web calendar app on my server, only by logging in to the one I’m federating with, which kinda defeats the point…
I’ve made some notes on other issues:
Calendar - does not federate at all
Calendar - unable to re-share a locally shared calendar via DAV
Maps - cannot see a list of favourites
Maps - first doubleclick opens a menu and selects an offsite link (expected to scale). Subsequent doubleclicks work as expected (zoom in)
Files - Moving a folder over another folder (with the same name) DELETES one of the copies rather than merges them (luckily this was noticed and the deleted copy rescued from trash.) This is seriously weird and dangerous.
Stupid defaults - trash and versions default to autodelete, and I can find no user visible indication of this or controls for it in the UI(its only available in config.php)
Is this the corresponding feature request to your problem?
For the other issues, make sure if you can find bug reports on github, there you can then follow the status. If there aren’t bug reports yet, feel free to open a new bug report.
Yes - I found that [calendar sharing github issue] searching previously - but aside from trivia, it’s not been touched for 2 years. Is anyone actually doing any work on it?
Re other issues - Perhaps - the Files issue came up in my searches - seems like a whopper of a misfeature that has been around a LONG time.
Any idea why it is this way? It’s conter to every other file manager I have ever used - Windows, Linux, MacOS, RISC OS…
Additionally, if you move a selection of files, rather than folders, you get one dialogue per file asking what to do, and clicking on the “all” button seems to mean “all of this one file”, and makes no difference - you have to click new or old for every single file. For more than a dozen or so files, this is an untenable process, and cannot be cancelled.
Unfortunately, we don’t have insights of what the company is planning to do on a longer term. Once they start working on it, or someone else, you’d see some activity on github. So probably there is no one working on it right now.
