Noah
SteveLinkNoah#5052
Joined Oct 4, 2026 @SteveLinkNoah on GitHub
Sign in to search- On [a11y] tab doesn't work in channels without message send permissionNot fixed for me. Compare the regular channels to these to see the issue. In a regular channel the first "tab" press always focuses on the message bar. This isn't the case in channels without message send permission. Depending on some factors that i haven't 100% figured out yet it either: Focuses on....
- "skip to content"
- "new messages" in the channel list
- the username of the first loaded message in the channel
- notification settings bell
- sometimes actually the message bar
- You can already do this yourself in the settings: settings > advanced > desktop > disable automatic updates then you can update whenever you want by clicking the update icon in the client link to the settings page: fluxer://settings/user?tab=advanced_settings§ion=advanced-settings-desktop
- Fixed for me.
- Fixed for me.
- I have an even better idea. The ability to disable it only as the uploader by adding an option in the attachment edit dialog. This would allow you to upload file with metadata anywhere but still protects users privacy in all channels. (There could even be a warning before fluxer lets you switch this toggle)
- Personally i don't like this idea for this type of chat app. Signal etc are also chat apps yes, but they serve a different use case. Mostly being focused on friends and family instead of large communites like fluxer is. If it would still be implemented it would have to be limited to DMs and maybe GCs, since there is no reason to have read indicators in a public channel with thousands of members. Or maybe a user count limit since GCs can already get larger than what read indicators are built for and it would allow small communites to have them as well. Besides that i would also like this to be opt-in rather than opt-out like u/93 already said.
- Can't you already do this by joining the VC and then first deafening and then unmuting? Bandwidth would still be wasted though.
- Fixed for me.
- On Tossable Catenable this setting: Settings -> Advanced -> Appearance -> Show Neko fluxer://settings/user?tab=advanced_settings§ion=advanced-settings-appearance
- On "Show non-video participants" should be disabled by default or it should remember your preferenceWell I want to know who I am talking to for example. When I don't know the people well enough to recognize their voice, I can see with the green outline who is talking. But I agree that it should remember your last choice, the default probably shouldn't change though, since it would confuse discord refugees who are used to it working this way.
- This report is really old, but I can still repro in Canary Desktop 2026.1018.223341, Web 2026.1018.223341, Windows 11 10.0.26200 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US. The language seems fixed but it still ignores my 24h clock setting
- I didn't know this existed, but since one of the languages symbols is very similar to the fluxer logo it has to be added just for that alone. upvote from me
- Fixed for me.
- Fixed for me.
- For federation it is important to remember that there are also restrictions from polyproto that need to be considered (so more restrictive than polyproto would be fine, but more permissive could cause issues later): https://polyproto.org/docs/protocols/core#5-federation-ids-fids
- There is, in my opinion, only one valid use case for this, that being the business use case. But for those cases i'd actually leave the ACL as is and instead allow message logging in the background. A business chat platform will probably want to keep message deletion for usablity reasons and have their compliance handled in the background. As for "granularizing ACLs on existing actions": I think this has the potential to do more harm than good, at least on regular instances. I think users should fundamentally have the right to view/edit/delete their messages for any reason at any time. Fluxer is still not completely where i want it to be for this (i would like a "inaccessible messages viewer" in the settings to allow viewing and deleting of messages that you can no longer access). If you want to preserve messages as evidence in a community you can use a bot to archive messages (allows deniability since bots can manipulate messages). As for the implications on federation: Federated instances can act in malicious ways no matter the outcome of this feature request. That said i think instances blocking message deletion should be labeled malicious and defederated from the fluxer.app instance since it fundamentally opposes the "right to be forgotten" (even if only blocked for individual messages). To address issues with my message logging idea: I am aware that this can be misused as well, however this is an unavoidable side effect of having a non encrypted chat platform. If i were a malicious instance i could enable some message logging right now, by simply having up-to-date backups of the database (this wouldn't be enough for the business use case, since there could be messages that are sent and deleted between backups). I currently do not see how this would be useful in any way (with the exception of the business use case, which i addressed already).
- It is true https://help.steampowered.com/en/faqs/view/6089-6768-F7FB-C46F There seem to be tutorials either way (no idea why, but i recently installed steam on a new device so i am quite sure the default is opt-out).
- The comparrison with Steam is actually helpful, since the Steam client itself is by default set to auto start as well, with an opt-out option for those that don't want it. This is done for the same reason that Fluxer also has auto start enabled by default. (There is also a huge differnce between a game, something you usually don't keep open in the backround, and a chat platform, something you do usually keep open in the backround to get notifications.) Default behaviour should in most cases be set to what most people want. In this case it most likely is opt-out although that isn't certain unless Fluxer starts doing A/B-Testing (which i hope doesn't happen). That said, putting this option in the setup wizard for the desktop app wouldn't hurt imo.
- duplicate of #2219 Version 2026.09.100, Beta 3, Channel Beta, Build 2530, Android 15 (arm64), Device samsung SM-X710, Locale de-DE, Push fcm, Flutter 3.47.5, Dart 3.13.4
- Can no longer reproduce Version 2026.09.100, Beta 2, Channel Beta, Build 2528, Android 16 (arm64), Device samsung SM-S936B, Locale en-DE, Push unifiedpush, Flutter 3.47.5, Dart 3.13.4
- Can no longer reproduce Version 2026.09.100, Beta 2, Channel Beta, Build 2528, Android 16 (arm64), Device samsung SM-S936B, Locale en-DE, Push unifiedpush, Flutter 3.47.5, Dart 3.13.4
- Can no longer reproduce Version 2026.09.100, Beta 2, Channel Beta, Build 2528, Android 16 (arm64), Device samsung SM-S936B, Locale en-DE, Push unifiedpush, Flutter 3.47.5, Dart 3.13.4
- Can reproduce
Version 2026.09.100, Beta 1, Channel Beta, Build 2498, Android 16 (arm64), Device samsung SM-S936B, Locale en-DE, Push unifiedpush, Flutter 3.47.5, Dart 3.13.4 - Can reproduce
Version 1.0.0, Beta 68, Channel Beta, Build 2490, Android 16 (arm64), Device samsung SM-S936B, Locale en-DE, Push unifiedpush, Flutter 3.47.5, Dart 3.13.4 - duplicate of #2225 (method for reproduction is different but the bug seems to be the same) Version 2026.09.100, Beta 1, Channel Beta, Build 2497, Android 15 (arm64), Device samsung SM-X710, Locale de-DE, Push fcm, Flutter 3.47.5, Dart 3.13.4