Hampus
Hampus#0000Staff
Joined Oct 4, 2026 @hampus-fluxer on GitHub
Sign in to search- On Remove the "Transfer Ownership" button from the user context menuThis has already shipped.
- It already doesn't. There is a tombstones table that retains it for 30 days after deletion for abuse investigation, but that's the only post-deletion retention of session info.
- It is deleted if your account is inactive for 2 years, but a system with automatically expiring sessions that require you to sign in again if your device isn't active enough to receive the instruction to rotate the token is something I would like to look into in the future. It just doesn't exist right now because it's more complicated to implement, and people don't like if they're randomly signed out every month because of bugs.
- I believe those who uses those microarchitectures can PR anything extra.
- completely wrong ticket, ignore my actions
- I will see what I can do to offer proper injection-based game capture, but so far we've been flagged as malware and gotten 1,000 support tickets and Reddit posts claiming that Fluxer is spyware because of it. I still need to look into a safe way to do this, and might offer it as a companion application that you can install, quite possibly, to isolate it from the main Fluxer application.
- note: very likely flatpak specific
- This is not a bug, but working as intended. It is intended that you are able to share attachment links in one place to another, that's a feature. However, this is a feature request for self-hosted instances to be able to configure requiring authorization for file access, if they want things to work more like Slack. This was a feature request I received by email yesterday and will be implemented today. As such, I'm converting this to a feature request and marking it as shipping soon.
- will be doing a mass-sweep soon before patch notes
- On Windows 10 version 1809, the passkey check that runs when a sign-in screen opens used a Windows feature your version of Windows doesn't have, and that closed the app. The "+" button in the account switcher opens a sign-in screen, and so does the welcome screen after a reinstall, which is why the app now closes at launch. The fix is merged and will be in the next desktop update. Passkeys will show as unavailable on 1809, and every other way to sign in will work.
- I'm looking at this now, sorry for the delay!
- Is this the macOS desktop app or in Safari?
- Thanks! will look into it soon
- "Stable Desktop 2026.1026.24218" you probably want to update your desktop client – https://fluxer.com/download or via your package manager
- ah wait that release happened prematurely, I haven't pushed up my changes yet
- This is fixed now. When you sign in from the feedback site, the sign-in page on web.fluxer.app now sends you on to fluxer.com if you're signed out there or your browser has already moved to fluxer.com. Your fluxer.com passkey is offered there, and you come back to the feedback site afterwarads. If you're still signed in on web.fluxer.app, the sign-in stays there with your existing session. As for having to close the empty passkey prompt once before the old passkey works: I agree that it's not obvious, and I'm looking at making that more obvious. I use a bridge like this instead of WebAuthn Related Origins because password managers like Bitwarden and Proton Pass don't support Related Origins yet, so it wouldn't help most people.
- This is now fully answered here: https://fluxer.com/help/why-does-fluxer-sell-the-operator-pass
- you're right that a mark next to an instance's name in an official list would look like Fluxer checked or vouches for that instance. so it won't be a badge or a check mark. when the list is out, an instance run by someone with an Operator Pass gets a line of text in its listing instead, something like "The admin of this instance has an Operator Pass. Thank you for supporting Fluxer!" because the line says "Operator Pass" in full, it can't be confused with someone who just operates an instance. every listed instance follows the same listing rules, and a pass never changes where an instance shows up on the list or how big its listing is. we also won't call it "donator", because the pass is a purchase, not a donation. I've written this up in the help center and clarified this everywhere now: https://fluxer.com/help/operator-mark-on-instance-listings
- Will be fixed when this is live: https://github.com/fluxerapp/fluxer/commit/c80aab7e9f11
- Yeah, that will be fixed in a future update
- To be clear it should still say status.fluxerstatic.com for now. But now it at least redirects to fluxerstatus.com. We had to do this temporarily for now because Instatus didn't like that we were sending them so much traffic.
- I'll sleep soon, but the Operator Pass will open tomorrow, and before then I'll have clarified quite a few things. I already started working on those explanations some time ago because I know some people are highly skeptical of the concept, but I've already swayed one such skeptic, and I hope my improved explanations will make it clear how this is actually a good thing, that you absolutely do not need to buy the pass, and that you shouldn't feel like you need to buy it! A lot of time and thought has gone into how the Operator Pass is designed, and the way it works has been thoroughly considered from many different perspectives and I've accepted a lot of feedback during that process. There is a logical and reasonable explanation for why it's structured the way it is. I've already shared a summary of some of this reasoning in Fluxer Developers, which you can read in these two messages: first message and second message.NoteThis is now fully answered here: https://fluxer.com/help/why-does-fluxer-sell-the-operator-pass
- Found the root cause, will be fixed in the next release.
- I should add that I haven't changed anything in either of the last updates to address your bug, so it is not me fixing it and unfixing it :P It is likely a result of restarting your client.