[GH-ISSUE #40] Feature request: Stop trying to sync without a username and password even entered. #37

Closed
opened 2026-02-25 22:35:54 +03:00 by kerem · 5 comments
Owner

Originally created by @mannp on GitHub (Dec 15, 2017).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/40

Thanks for the plugin, its great, but this niggles me every time I have to setup a new user.

At each point of adding details fail2ban bans the client for repeated incorrect connections, meaning I have to unban and quickly enter the details.

It doesn't make sense for the plugin to try and connect without any details / complete details.

Can the plugin connect when the details are all added, or have it that it starts trying to connect on a force start by the user?

Thanks for your consideration.

Originally created by @mannp on GitHub (Dec 15, 2017). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/40 Thanks for the plugin, its great, but this niggles me every time I have to setup a new user. At each point of adding details fail2ban bans the client for repeated incorrect connections, meaning I have to unban and quickly enter the details. It doesn't make sense for the plugin to try and connect without any details / complete details. Can the plugin connect when the details are all added, or have it that it starts trying to connect on a force start by the user? Thanks for your consideration.
kerem closed this issue 2026-02-25 22:35:54 +03:00
Author
Owner

@marcelklehr commented on GitHub (Dec 15, 2017):

I've tried to improve the behavior of the automated connectivity check in v1.3.1, so that it waits for the user to pause typing until it checks the credentials. Given that you were apparently still on 1.3.0 when making the comment, I encourage you to try the new version to see if the new behavior is better :)

<!-- gh-comment-id:351982516 --> @marcelklehr commented on GitHub (Dec 15, 2017): I've tried to improve the behavior of the automated connectivity check in v1.3.1, so that it waits for the user to pause typing until it checks the credentials. Given that you were apparently still on 1.3.0 when making the comment, I encourage you to try the new version to see if the new behavior is better :)
Author
Owner

@marcelklehr commented on GitHub (Dec 18, 2017):

Upon further negative feedback tapping in the same hole, I decided to drop the validation altogether, because nothing will explode if people use the force sync button for testing their account the first time. In fact the validation only tested authentication, but not the whole sync process, so it kinda offers a false security. tl;dr thanks for you sensible advice and happy syncing :)

<!-- gh-comment-id:352553899 --> @marcelklehr commented on GitHub (Dec 18, 2017): Upon further negative feedback tapping in the same hole, I decided to drop the validation altogether, because nothing will explode if people use the force sync button for testing their account the first time. In fact the validation only tested authentication, but not the whole sync process, so it kinda offers a false security. tl;dr thanks for you sensible advice and happy syncing :)
Author
Owner

@mannp commented on GitHub (Dec 18, 2017):

@marcelklehr I personally much prefer your revised method in 1.3.2 👍 thanks for that.

I can add a user and when I am happy with the settings, force a sync.

No more fail2ban resetting.

Keep up the great work :)

<!-- gh-comment-id:352561573 --> @mannp commented on GitHub (Dec 18, 2017): @marcelklehr I personally much prefer your revised method in 1.3.2 👍 thanks for that. I can add a user and when I am happy with the settings, force a sync. No more fail2ban resetting. Keep up the great work :)
Author
Owner

@marcelklehr commented on GitHub (Dec 18, 2017):

Thanks :)

<!-- gh-comment-id:352571396 --> @marcelklehr commented on GitHub (Dec 18, 2017): Thanks :)
Author
Owner

@github-actions[bot] commented on GitHub (Mar 21, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:1478281150 --> @github-actions[bot] commented on GitHub (Mar 21, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#37
No description provided.