Edit history

Earlier versions of [Self-Hosted] #0000 discriminator doesn't consider self-hosted instances, newest first.

Current version | Edited by Rex
Changes
[image](https://feedback.fluxer.com/p/674#f-670)Removed: ### ChecksRemoved: Removed: - ☑ I searched existing issues.Removed: - ☑ I wrote this report in my own words, except for direct translation if needed.Removed:
Show

[Self-Hosted] #0000 discriminator doesn't consider self-hosted instances

Summary

This issue is a reopening issue for #170 (got closed during bulk cleanup)
Username discriminator check when changing to #0000 only checks !isVisionary and doesn't consider self-hosted instances. https://github.com/fluxerapp/fluxer/blob/41ec2544cf3c048cf99c3e8d00bc84ad5308efdf/fluxer_app/src/features/user/components/modals/FluxerTagChangeModal.tsx#L318

Steps to reproduce

  1. Setup self-hosted instance
  2. On a non-visionary account, attempt to use #0000 discriminator.
  3. Username modal shows error

Environment

Version: Latest (Self-Hosted) as of this issue sent. OS: Linux 7.0.11-1-cachyos Browser: Version 149.0.7827.53 (Official Build, ungoogled-chromium) Arch Linux (64-bit) Device: Desktop PC

Logs or screenshots

image
Edited by Rex
Changes
### SummaryRemoved: > This issue is a reopening issue for [#256](https://feedback.fluxer.com/p/170) (got closed during bulk cleanup)Added: > This issue is a reopening issue for [#170](https://feedback.fluxer.com/p/170) (got closed during bulk cleanup)Username discriminator check when changing to `#0000` only checks !isVisionary and doesn't consider self-hosted instances.
Show

[Self-Hosted] #0000 discriminator doesn't consider self-hosted instances

Summary

This issue is a reopening issue for #170 (got closed during bulk cleanup)
Username discriminator check when changing to #0000 only checks !isVisionary and doesn't consider self-hosted instances. https://github.com/fluxerapp/fluxer/blob/41ec2544cf3c048cf99c3e8d00bc84ad5308efdf/fluxer_app/src/features/user/components/modals/FluxerTagChangeModal.tsx#L318

Steps to reproduce

  1. Setup self-hosted instance
  2. On a non-visionary account, attempt to use #0000 discriminator.
  3. Username modal shows error

Environment

Version: Latest (Self-Hosted) as of this issue sent. OS: Linux 7.0.11-1-cachyos Browser: Version 149.0.7827.53 (Official Build, ungoogled-chromium) Arch Linux (64-bit) Device: Desktop PC

Logs or screenshots

image

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.
Edited by Rex
Changes
1. Setup self-hosted instanceRemoved: 2. On a non-visionary account, attempt to use [#0000](https://github.com/fluxerapp/fluxer/issues/0) discriminator.Added: 2. On a non-visionary account, attempt to use `#0000` discriminator.3. Username modal shows error
Show

[Self-Hosted] #0000 discriminator doesn't consider self-hosted instances

Summary

This issue is a reopening issue for #256 (got closed during bulk cleanup)
Username discriminator check when changing to #0000 only checks !isVisionary and doesn't consider self-hosted instances. https://github.com/fluxerapp/fluxer/blob/41ec2544cf3c048cf99c3e8d00bc84ad5308efdf/fluxer_app/src/features/user/components/modals/FluxerTagChangeModal.tsx#L318

Steps to reproduce

  1. Setup self-hosted instance
  2. On a non-visionary account, attempt to use #0000 discriminator.
  3. Username modal shows error

Environment

Version: Latest (Self-Hosted) as of this issue sent. OS: Linux 7.0.11-1-cachyos Browser: Version 149.0.7827.53 (Official Build, ungoogled-chromium) Arch Linux (64-bit) Device: Desktop PC

Logs or screenshots

image

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.
Edited by Rex
Changes
> This issue is a reopening issue for [#256](https://feedback.fluxer.com/p/170) (got closed during bulk cleanup)Removed: Username discriminator check when changing to [#0000](https://github.com/fluxerapp/fluxer/issues/0) only checks !isVisionary and doesn't consider self-hosted instances.Added: Username discriminator check when changing to `#0000` only checks !isVisionary and doesn't consider self-hosted instances.https://github.com/fluxerapp/fluxer/blob/41ec2544cf3c048cf99c3e8d00bc84ad5308efdf/fluxer_app/src/features/user/components/modals/FluxerTagChangeModal.tsx#L318
Show

[Self-Hosted] #0000 discriminator doesn't consider self-hosted instances

Summary

This issue is a reopening issue for #256 (got closed during bulk cleanup)
Username discriminator check when changing to #0000 only checks !isVisionary and doesn't consider self-hosted instances. https://github.com/fluxerapp/fluxer/blob/41ec2544cf3c048cf99c3e8d00bc84ad5308efdf/fluxer_app/src/features/user/components/modals/FluxerTagChangeModal.tsx#L318

Steps to reproduce

  1. Setup self-hosted instance
  2. On a non-visionary account, attempt to use #0000 discriminator.
  3. Username modal shows error

Environment

Version: Latest (Self-Hosted) as of this issue sent. OS: Linux 7.0.11-1-cachyos Browser: Version 149.0.7827.53 (Official Build, ungoogled-chromium) Arch Linux (64-bit) Device: Desktop PC

Logs or screenshots

image

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.
Original by Rex
Show

[Self-Hosted] #0000 discriminator doesn't consider self-hosted instances

Summary

This issue is a reopening issue for #256 (got closed during bulk cleanup)
Username discriminator check when changing to #0000 only checks !isVisionary and doesn't consider self-hosted instances. https://github.com/fluxerapp/fluxer/blob/41ec2544cf3c048cf99c3e8d00bc84ad5308efdf/fluxer_app/src/features/user/components/modals/FluxerTagChangeModal.tsx#L318

Steps to reproduce

  1. Setup self-hosted instance
  2. On a non-visionary account, attempt to use #0000 discriminator.
  3. Username modal shows error

Environment

Version: Latest (Self-Hosted) as of this issue sent. OS: Linux 7.0.11-1-cachyos Browser: Version 149.0.7827.53 (Official Build, ungoogled-chromium) Arch Linux (64-bit) Device: Desktop PC

Logs or screenshots

image

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.