Edit history

Problem

I'm writing this in frustration. Everytime I see Fluxer online, I open it to work on my new community, and as I'm writing a message, in the middle of it it throws me on the loading screen image I get that you are having issues and working on fixing them, but yesterday I lost the contents of my long post about 5 times. Related open discussions:

1. https://feedback.fluxer.com/p/1000 (describe the issue partially)
2. https://feedback.fluxer.com/p/975

Proposed solution

I suggest that in case you have updated the container, the Update button should be manual in the corner of the screen, not automatic. So that the user can finish their work in the UI before they click on it. I suggest also that instead of throwing me on the loading screen in case of a connectivity issue, you show a red line on top saying "failed to connect", as in old discord. nowadays Discord doesn't even do that. instead, they show me the cached version of the server, and when I go to an uncached server, it says "messages failed to load". I don't even get any interruptions in my workflow as a user. I think it's best to make it seamless with updates, errors, etc, like discord did. Even if discord sometimes has connectivity issues, it will preserve my undelivered messages locally. Additionally, it's good to preserve the content of the text fields when I leave text in them in say LocalStorage. I'm pretty sure Discord is doing that, as I'm reopening the app and the text is still there. For every contact in the DMs and for every channel in the server.

Problem

I'm writing this in frustration. Everytime I see Fluxer online, I open it to work on my new community, and as I'm writing a message, in the middle of it it throws me on the loading screen image I get that you are having issues and working on fixing them, but yesterday I lost the contents of my long post about 5 times. Related open discussions:

1. https://feedback.fluxer.com/p/1000 (describe the issue partially)
2. https://feedback.fluxer.com/p/975

Proposed solution

I suggest that in case you have updated the container, the Update button should be manual in the corner of the screen, not automatic. So that the user can finish their work in the UI before they click on it. I suggest also that instead of throwing me on the loading screen in case of a connectivity issue, you show a red line on top saying "failed to connect", as in old discord. nowadays Discord doesn't even do that. instead, they show me the cached version of the server, and when I go to an uncached server, it says "messages failed to load". I don't even get any interruptions in my workflow as a user. I think it's best to make it seamless with updates, errors, etc, like discord did. Even if discord sometimes has connectivity issues, it will preserve my undelivered messages locally. Additionally, it's good to preserve the content of the text fields when I leave text in them in say LocalStorage. I'm pretty sure Discord is doing that, as I'm reopening the app and the text is still there. For every contact in the DMs and for every channel in the server.

Notes (optional)

No response

Checks

• ☑ I searched for existing discussions and didn't find a duplicate.

Problem

I'm writing this in frustration. Everytime I see Fluxer online, I open it to work on my new community, and as I'm writing a message, in the middle of it it throws me on the loading screen image I get that you are having issues and working on fixing them, but yesterday I lost the contents of my long post about 5 times. Related open discussions:

1. https://github.com/orgs/fluxerapp/discussions/445 (describe the issue partially)
2. https://github.com/orgs/fluxerapp/discussions/389

Proposed solution

I suggest that in case you have updated the container, the Update button should be manual in the corner of the screen, not automatic. So that the user can finish their work in the UI before they click on it. I suggest also that instead of throwing me on the loading screen in case of a connectivity issue, you show a red line on top saying "failed to connect", as in old discord. nowadays Discord doesn't even do that. instead, they show me the cached version of the server, and when I go to an uncached server, it says "messages failed to load". I don't even get any interruptions in my workflow as a user. I think it's best to make it seamless with updates, errors, etc, like discord did. Even if discord sometimes has connectivity issues, it will preserve my undelivered messages locally. Additionally, it's good to preserve the content of the text fields when I leave text in them in say LocalStorage. I'm pretty sure Discord is doing that, as I'm reopening the app and the text is still there. For every contact in the DMs and for every channel in the server.

Notes (optional)

No response

Checks

• ☑ I searched for existing discussions and didn't find a duplicate.