[Bug]

[JimmyPowell]

Bug Description

桌面版客户端webdav同步存在问题

Steps to Reproduce

我设置了webdav的服务器地址、用户名和密码，然后点击检查可用性，桌面版的一直提示错误，但是网页版的没有问题，可以正常备份。

Expected Behavior

请求帮助

Screenshots

No response

Deployment Method

• [x] Docker
• [ ] Vercel
• [ ] Server

Desktop OS

win 11

Desktop Browser

No response

Desktop Browser Version

No response

Smartphone Device

No response

Smartphone OS

No response

Smartphone Browser

No response

Smartphone Browser Version

No response

Additional Logs

桌面版版本：2.11.2 网页端版本：2.10.3

[nextchat-manager[bot]]

Please follow the issue template to update description of your issue.

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: [Bug]

[H0llyW00dzZ]

I've been knowing it, anyways for @fred-bf whoever owner this repo, it's better to focusing fix a bug, and improve the performance instead of adding another ai especially unstable ai lmao, like previous owner @Yidadaa

[fred-bf]

@H0llyW00dzZ

1. Ollama is currently the most requested feature, and it makes a lot of sense to allow more people to use almost all open-source models supported by Ollama. Regarding the stability issues with Ollama, it largely depends on the user's local service and the models themselves. It's worth noting that several companies have already deployed and used it in production environments.

2. The focus of the open-source community is on collaborative efforts and project maintenance. Working together, we can better address issues and, more often than not, this collaboration is driven by shared interests. It's crucial not to prioritize personal preferences in blaming others for how issues are addressed. If you have the time to assist in resolving issues that impact your usage, your contribution would be greatly appreciated.

3. Reproducing and addressing issues of different nature takes time, and it doesn't mean all issues must be resolved before introducing new features to the project.

[H0llyW00dzZ]

@H0llyW00dzZ

1. Ollama is currently the most requested feature, and it makes a lot of sense to allow more people to use almost all open-source models supported by Ollama. Regarding the stability issues with Ollama, it largely depends on the user's local service and the models themselves. It's worth noting that several companies have already deployed and used it in production environments.
2. The focus of the open-source community is on collaborative efforts and project maintenance. Working together, we can better address issues and, more often than not, this collaboration is driven by shared interests. It's crucial not to prioritize personal preferences in blaming others for how issues are addressed. If you have the time to assist in resolving issues that impact your usage, your contribution would be greatly appreciated.
3. Reproducing and addressing issues of different nature takes time, and it doesn't mean all issues must be resolved before introducing new features to the project.

2. The focus of the open-source community is on collaborative efforts and project maintenance. Working together, we can better address issues and, more often than not, this collaboration is driven by shared interests. It's crucial not to prioritize personal preferences in blaming others for how issues are addressed. If you have the time to assist in resolving issues that impact your usage, your contribution would be greatly appreciated.

I don't think so you are working together, every time when I look you always alone even ignoring pull req you can see this so many pull req that not even close/accept it literally you are ignoring it

[fred-bf]

@H0llyW00dzZ Some of the discussion here has gone off topic. I'll address the question regarding this area. Due to bandwidth constraints, we prioritize merging PRs that can be quickly reviewed. For PRs with broader implications, we gradually conduct thorough testing before merging.

[JimmyPowell]

@H0llyW00dzZ @fred-bf Thank you all for your efforts and attention to this issue. I've noted the discussion around the project's direction and feature implementation, but I would like to re-emphasize the WebDAV synchronization concern. I understand that resources in open-source projects are limited, and everyone's contributions are based on a love for the community and selfless donation of personal time.

If possible, I hope my issue could receive further attention. I believe this would not only assist me but could also be beneficial to other users who may face similar challenges. If there is any way I can help with diagnosing the issue, or if more information is needed from my side, please let me know.

At the same time, I am open to the project's future developments and look forward to the introduction of new features and improvements. I understand that this may take time, and that the introduction of each new feature needs to balance stability with innovation.

Thank you once again for everyone's hard work and support.

[H0llyW00dzZ]

@H0llyW00dzZ @fred-bf Thank you all for your efforts and attention to this issue. I've noted the discussion around the project's direction and feature implementation, but I would like to re-emphasize the WebDAV synchronization concern. I understand that resources in open-source projects are limited, and everyone's contributions are based on a love for the community and selfless donation of personal time.

If possible, I hope my issue could receive further attention. I believe this would not only assist me but could also be beneficial to other users who may face similar challenges. If there is any way I can help with diagnosing the issue, or if more information is needed from my side, please let me know.

At the same time, I am open to the project's future developments and look forward to the introduction of new features and improvements. I understand that this may take time, and that the introduction of each new feature needs to balance stability with innovation.

Thank you once again for everyone's hard work and support.

Anyways

I might made my own synchronization solution, written in Go later, instead of fixing bugs in WebDAV. This is because WebDAV is quite outdated and no longer aligns with modern standards.

[H0llyW00dzZ]

it's so easy to implement because the data its contain json