Planned Features for ClipCascade

[Sathvik-Rao]

#	Feature	Difficulty	Time Taking	Notes
1	iOS Implementation	3	3	High difficulty, time-consuming, $$ for deployment
2	Multiuser Support	1	2	Easier to implement, moderate time commitment
3	OIDC/OAuth Authentication	2	2	Medium difficulty and time commitment
4	Clipboard Data Storage	1	2	Easy to implement, moderate time commitment
5	Image and File Support	3	3	High difficulty, time-consuming

Please vote for the one you believe is most important to implement first or the one you need the most, and leave comments on the others.

[Sathvik-Rao]

5 - Image and File Support ✅
2 - Multiuser Support ✅ (Implemented as part of encryption enhancements, tied to database functionality for multi-user support.)

[applesoff]

Both File and Image Support work great. I wish there weren't 1 MB file size restraints on android though. Any way to set a preferred folder for each OS so that you do not have to specify each time you click download?

[Sathvik-Rao]

Hi @applesoff you can increase the limit in the server CC_MAX_MESSAGE_SIZE. Files and images are not an issue with android because they are not stored on clipboard directly, but with text there is ~1MB limit.
In next update I will include preferred folder field in login page.

[Sathvik-Rao]

Are you suggesting a preferred location for file downloads on click download file(s), or should all received files be saved to that location automatically?

[applesoff]

A preferred location for downloads when clicking the "download files" button would make the most sense as I have 4 devices synced with CC. I do plenty of copying files on my devices without wanting to send them so if it was automatically downloaded that may lead to a lot of files being added to a de ice you did not want.

[Sathvik-Rao]

Hi @applesoff
In the latest release, the "download files" feature is available for the desktop app with a preferred location, but for Android, files are accessed based on user permissions. Automatic downloads on Android require additional file permissions, which is why it hasn't been implemented yet.

[Johnr24]

I would love the ability to download files to my clipboard without having to click "download files" so I could just ctrl+c on one mac and paste it into the directory on another

[zezretro]

Small bump for removing the lower dock icon in OSX and leaving only the upper menu bar icon

[HumanMus1c]

Webdav sync support.

[wjcarpenter]

Regarding OIDC ...

A lot of people doing self-hosting also run a reverse proxy. Once you've set up SSO in the reverse proxy for one application, it's usually pretty easy to set it up for others. It's much simpler, both for the people running ClipCascade and for the ClipCascade developer to do SSO in the reverse proxy SSO environment. All you really need are configs for the reverse proxies that you trust and some one or more HTTP headers that will tell you the user identity. (Optional: another config that disables userid/password authentication.)

Of course, not everybody runs a reverse proxy that does the SSO stuff. But implementing the full OIDC flow in the ClipCascade code is a much bigger job. (I dunno ... maybe there is some nice library that does all that for you.) Maybe implementing SSO via a trusted reverse proxy would be a good, lower-effort first step. It also allows for other SSO schemes (for example, SAML or mTLS) without needing code in ClipCascade.