• 1 vote
    Still happening for me Version 2026.10.100, Beta 12, Channel Beta, Build 2816, Android 15 (arm64), Device OnePlus HD1901, Locale en-DE, Push unifiedpush, Flutter 3.47.8, Dart 3.13.7
  • 1 vote

    Feel free to mark this as fixed!!

    Okay, i figured out what caused this. for some reason the default limit configuration in my instance had a default-user trait applied to it. I dont know if I set that or if that was a leftover from an update. Removing it fixed the issue.
  • 1 vote
    Fixed, this works now!
  • 1 vote
    This is fixed! Thanks for the quick work <3 tested it with a .txt file which were broken previously.
  • 1 vote
    Can confirm this issue. The settings are incorrectly reflected in the mobile app. E.g. ( The Create Posts permission on Web/Desktop appears as Send Messages on mobile.) (You can test this by opening the settings on 2 seperate platforms and switching the settings on and off and observing the changes on the other one) Version 2026.10.100, Beta 5, Channel Beta, Build 2667, Android 15 (arm64), Device OnePlus HD1901, Locale en-DE, Push unifiedpush, Flutter 3.47.7, Dart 3.13.5
  • 1 vote
    Still happening with the most recent api container.
    CONTAINER           REPOSITORY                     TAG                 PLATFORM            IMAGE ID            SIZE                CREATED
    fluxer-api-1        ghcr.io/fluxerapp/fluxer-api   v1                  linux/amd64         d6c88636efc1        1.91GB              8 hours ago
    
    To clarify i have FLUXER_S3_ENDPOINT referencing the buckets virtual host like this: https://[bucket-name].s3.[region-code].[server-provider].com This might be an issue of Path_Style and Virtual_Style S3 requests clashing somewhere.
  • 1 vote
    Not really a bug, it has a scroll bar on the bottom so all the accounts are still accessible. this should be a feature request for improval of the ui instead.
  • 1 vote
    Can still reproduce with the same steps. Updated my self-hosted instance to the latest version. Tried using a separate browser to avoid caching. (My instances premium model is set to everyone)ran into some similar issues, have made a report for them here: #3919 Canary Web 2026.1012.2059, Linux (x64), Firefox 157.0, Locale en-US
  • 2 votes
    Can confirm that this is happening on the latest version of both canary desktop and web.
    • Desktop:
    Canary Desktop 2026.1009.45608, Web 2026.1011.125152, Linux 7.2.9-100.fc43.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-GB
    • Web:
    Canary Web 2026.1011.125122, Linux (x64), Firefox 157.0, Locale en-US

    Recreation Steps

    • Make a self-hosted instance with usernames as the login method
    • Login with an existing account
    • Open the Account Switcher
    • Choose to add a new account
    • Click "Register an Account"
    • Observe that the Email field is present and not treated a optional (it shouldnt really be here in the first place. the register link does not have it)
  • 2 votes
    After talking about it more, i have realized that it maybe wont be as easy to implement as i originally thought. tho this is how it could work:
    • the current system of having everyones tag be #0000 in the background could be kept
    • change it so the system ignores everything that isnt #0000 as a tag when on a username instance without tags.
    • implement a configuration in the instance config that lets admins set allowed characters and input a regex filter that usernames have to pass.
    this way admins could make users in their instance adhere to a certain username-scheme. this would let admins decide on their own how to style tags for their instance or make usernames follow some other scheme. For example:
    • Different Tag styles using an arbitrary character: #xxxx, *xxxx, ~xxxx
    • Email like username scheme: username@example.whatever
    this system could also potentially be used on email instanced that have tags disabled. one downside to this implementation would be that users probably wont be able to use anything like #0000 or #0 as their visible "tag" since that might break things
  • 1 vote
    fair enough, i just think that implementing regex filter configuration would be a more universal solution. like maybe there will be other instances that want usernames to adhere to a certain scheme that doesn't use that standard #xxxx tags. also considering that the tags would most likely just have to be part of the username anyway to avoid complications with the login system and to not have to add more complexity to that, i think it would be best if this was implemented as regex filtering. maybe the standard #xxxx tags could be provided as a possible preset
  • 1 vote
    Fixed for me Canary Web 2026.1010.183920, Linux (x64), Firefox 157.0, Locale en-US
  • 1 vote
    Okay i have a few questions:
    • what is the point of reintroducing tags into a username based system, since usernames are used for login here it there couldn't be duplicate usernames anyway.
    • what is stopping you from just adding a tag (#xxxx) to the end of your username in a username based instance? it it would functionally look the exact same as on a email based instance.
    i just dont see the point of this feature a more functional solution to this problem would be adding an option to force usernames to pass a regex filter on account creation. this way you could just force people to add a tag to their username. Edit: ive noticed that a selfhosted instance blocks you from adding a # to a username. i still think just letting instance admins edit a configuration for username regex requirements and selecting which characters are valid would be the most reasonable solution to this issue
  • 1 vote
    I was just thinking about making this feature request as well! I would love to be able to able to be notified about everything regarding posts i am following. oh hey thats me in the screenhot :3
  • 1 vote
    This Feature makes a lot of sense, especially considering the profile switcher in the mobile beta already does show instance names under the respective profiles. Having an option to have them show under the profile icons would be a great addition.
  • 2 votes
    Have also had this happen when inconsistently on Canary when:
    • Switching to and from a selfhosted instance
    • Enabling and disabling Custom Css
    Channels reapear after reload of the AppCanary Desktop 2026.1009.45608, Web 2026.1009.45608, Linux 7.2.9-100.fc43.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US
  • 1 vote
    This was reported again as #3684. Still happening for me. Version 2026.10.100, Beta 3, Channel Beta, Build 2621, Android 15 (arm64), Device OnePlus HD1901, Locale en-DE, Push unifiedpush, Flutter 3.47.6, Dart 3.13.5
  • 1 vote
    Can second this for trying to connect to my selfhost with Android. Version 2026.10.100, Beta 3, Channel Beta, Build 2621, Android 15 (arm64), Device OnePlus HD1901, Locale en-DE, Push unifiedpush, Flutter 3.47.6, Dart 3.13.5