Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] support for /e/os webdav accounts #1559

Open
Derisis13 opened this issue Aug 24, 2024 · 2 comments
Open

[Feature] support for /e/os webdav accounts #1559

Derisis13 opened this issue Aug 24, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@Derisis13
Copy link

Is your feature request related to a problem? Please describe.

/e/os has a built-in webdav client. It's a fork of dav5x, the source is accessible here: https://gitlab.e.foundation/e/os/AccountManager
JTX board currently doesn't recognize this as a viable backend.

Describe the solution you'd like

I wish to use this built-in account manager/webdav client as a synchronization backend instead of separately installing dav5x.

Describe alternatives you've considered

Dav5x works fine for synchronization, as far as I can tell, it isn't bothered by the /e/ client.

Additional context

If work from the /e/ side is required to achieve this, leave it be, since I can't upgrade to the latest release due to a bug.

Your current device and version

  • Device: [Xiaomi Redmi Note 8T]
  • Android version: [Android 13]
  • jtx Board version: [2.09.01]
  • Downloaded from: [/e/'s "App Lounge", which I think gets it from F-droid but I'm not 100% on that]
@Derisis13 Derisis13 added the enhancement New feature or request label Aug 24, 2024
@BaumiCoder
Copy link

The reason for this problems seems to be a change in DAVx5 fork of the /e/ project, as @patrickunterwegs explaint in a GitHub Dicussion. An issue at /e/ project about this exists here, but was closed as inactive.

@Derisis13
Copy link
Author

Oh I see. Sorry I made a duplicate, I didn't look at the discussions, only issues.
I find it very unlikely that /e/ will do anything about their fork, it hasn't seen any activities for years from what I've seen.
Feel free to close the issue if there's nothing you can do with reasonable effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants