starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 14:16:12 +03:00

[GH-ISSUE #1023] Do not allow placeholder bob@example.com to actually become an active account #673

New issue

Closed

opened 2026-02-25 22:37:48 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 22:37:48 +03:00

Owner

Originally created by @sunjam on GitHub (Jan 24, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1023

bob@example.com becomes a real Floccus account for the user, sometimes in multiple instances for the new extension installations

Describe the solution you'd like

Do not actually allow the example instance to become active. If it must be automatically created, do not allow it to actually activate. Thank you for considering.

Originally created by @sunjam on GitHub (Jan 24, 2022). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1023 ### Is your feature request related to a problem? Please describe. bob@example.com becomes a real Floccus account for the user, sometimes in multiple instances for the new extension installations ### Describe the solution you'd like Do not actually allow the example instance to become active. If it must be automatically created, do not allow it to actually activate. Thank you for considering.

kerem

2026-02-25 22:37:48 +03:00

closed this issue
added the
enhancement

🙁 Not following issue template
labels

kerem commented

2026-02-25 22:37:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 24, 2022):

Hi @sunjam! This issue is being automatically closed because it does not follow the issue template.

@github-actions[bot] commented on GitHub (Jan 24, 2022): Hi @sunjam! This issue is being automatically closed because it does not follow the issue template.

kerem commented

2026-02-25 22:37:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jan 24, 2022):

Hi @sunjam 👋

How does this happen? I only get a real bob@example account when setting out to create a new account without changing the defaults.

@marcelklehr commented on GitHub (Jan 24, 2022): Hi @sunjam :wave: How does this happen? I only get a real bob@example account when setting out to create a new account without changing the defaults.

kerem commented

2026-02-25 22:37:48 +03:00

Author

Owner

@sunjam commented on GitHub (Mar 26, 2022):

Start adding a new account without completing the task and bob autofills into your client device. This happens to me basically every time I need to reinstall floccus.

@sunjam commented on GitHub (Mar 26, 2022): Start adding a new account without completing the task and bob autofills into your client device. This happens to me basically every time I need to reinstall floccus.

kerem commented

2026-02-25 22:37:48 +03:00

Author

Owner

@PSeQXh commented on GitHub (Apr 16, 2022):

Start adding a new account without completing the task and bob autofills into your client device

Same here, started but didn't complete the task, on Chromium on alpine 3.15 with Floccus extension v4.13.0. It could be that one needs to actively click on the 'floccus button in the extension bar' again to trigger some syncing. At least for me, when I clicked on that button, Floccus created an (reasonable) error log:

2022-04-16T02:07:28.115Z Starting sync process for account bob@example.org
2022-04-16T02:07:28.381Z Syncing failed with E019: HTTP status 404. Failed POST request. Check your server configuration and log.

@PSeQXh commented on GitHub (Apr 16, 2022): > Start adding a new account without completing the task and bob autofills into your client device Same here, started but didn't complete the task, on Chromium on alpine 3.15 with Floccus extension v4.13.0. It could be that one needs to actively click on the 'floccus button in the extension bar' again to trigger some syncing. At least for me, when I clicked on that button, Floccus created an (reasonable) error log: > 2022-04-16T02:07:28.115Z Starting sync process for account bob@example.org > 2022-04-16T02:07:28.381Z Syncing failed with E019: HTTP status 404. Failed POST request. Check your server configuration and log.

kerem commented

2026-02-25 22:37:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 3, 2022):

Revamped the account setup process which fixes this issue.

@marcelklehr commented on GitHub (May 3, 2022): Revamped the account setup process which fixes this issue.

kerem commented

2026-02-25 22:37:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 4, 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.

@github-actions[bot] commented on GitHub (May 4, 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.

kerem referenced this issue

2026-02-25 23:30:34 +03:00

[PR #673] [CLOSED] Bump sass-loader from 8.0.2 to 10.0.3 #1701

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#673

No description provided.

Rows
Columns