Falco
Falco#1001
Joined Oct 8, 2026 @xfalc0 on GitHub
Sign in to search- On Messages From Webhook in Announcement Channels Do Not PublishMy post has been updated. Thank you for your insight @Fullest
- I can confirm your findings. Because of this, this post would be better classified as a feature rather than a bug. There's an opportunity here to make it more clear that webhook messages need to be manually published. But also for ease of use, I think it would be even better for webhook messages to auto-publish.
You described what is included in the pass in you own question. And you are saying that you don't think that what you get is worth the asking price.
Yes, because given the length of the operator terms, I felt it was important to directly point out what I'm specifically providing feedback on. After all, this is a feedback post where I requested that either the price be brought down to manage the expectations people would have purchasing the pass at that price, or to provide reasoning as to why it is priced where it is.If you don't like the price. Don't buy it.
I am buying it once further clarification on why explicitly purchasing the pass outside of making a donation of $200 is a good thing. Hampus has informed me today that he's working on better explaining the purpose of the pass and its pricing, which was a desired effect of making this feedback post. And as I mentioned in my feedback, I am going to purchase the pass (and to be abundantly clear, I will pay $200 if the price stays at that point). Which leads me to the next point I want to address:Some would argue that keeping venture capital out the project alone would justify the price.
Yes, this is a valid argument. My counterargument is that they can simply make a donation as well in addition to paying for a cheaper Operator Pass should they be so inclined.- This feature appears to have been implemented. If I may provide additional feedback, I think it would be nice if there was a way for operators to organize the order by which badges are displayed. Currently, they appear to be displayed by oldest created to newest created, left to right.
- Fix confirmed using: rexctl 2026.1025.191336 Fluxer 2026.1025.191336
- As a hobby musician and music producer, I like where this is going. This is what I'm thinking:
- I think the delay is nice to have, but there's too much of it. I'd recommend maintaining the delay BPM, but reducing how many times it tails off. Additionally, seeing that a lot of people are mentioning the delay, you may also want to pull back the wet signal on the delay. If you want to automate the wet signal, use a compressor and side chain it to the delay so that the delay is compressed appropriately.
- I really like the melody for
incoming-call.wavwith how it's harmonically structured. The chord changes are simple and it doesn't resolve to home until the very end, which feels intentional considering that receiving a notification from a user standpoint is an unresolved notification until the user acknowledges it. I'd recommend keeping the melody and most of the changes; maybe consider not doing vi-I towards the end, and keep the vibe in a major key.
- The mute sounds don't feel intentional in that given the note register, it makes the sound feel too bright, which is the opposite of feeling muted. By contrast, the deafen sounds feel intentional. I'd recommend changing the approach for the mute sounds.
- Confirmed to be fixed, tested against multiple instance switches. Stable Desktop 2026.1013.15209, Web 2026.1013.135431, Linux 7.2.9-arch1-1 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US
- I like this idea as someone who uses forums to list off threads as a to-do checklist.
- This is confirmed to be fixed on Fluxer API 2026.1011.125745 Enabling media expiry applies an expiration date for all media based upon the date of upload. Disabling media expiry removes expiration dates for all uploaded media on the server.
- I want to add onto this feature discussion. When the instance quick switcher update was released to Canary recently, the log-in screen for Fluxer changed. The login screen is now quite bare, showing only the Fluxer space background and the log in panel, with the only customizable thing being the UI buttons which only recently started respecting the theme color set in the admin panel, thanks to this PR: https://github.com/fluxerapp/fluxer/pull/3355 The current login screen is opposite to the spirit that this discussion was made for. Now that self-hosting is in a very viable and stable state, I'd like to see customization options available to make this screen different, as it is a user's first impression when registering an account on a Fluxer instance. Customization of this screen would allow instances to standout from each other. I don't think complicated options need to be available, but rather the ability to show the instance's logo, wordmark, and a customizable background would be very good things to start with. I've provided images of what the login screen currently looks like, and what I think it can look like for a self-hosed instance like mine if more customization options were given.
- For reproduction step 1, I indicated that you have to switch into a community with threads. But after further use, it doesn't matter if the community you switch into has threads or not. If you switch onto a different instance and the community you land on has no threads, going to a different community with threads will not display them until after a reload.
- This is not a bug. I forgot to check the "Admin Registration URLs enabled" option. Closing ticket.
- I'm personally a fan of Mockup 5, as it brings continuity between the desktop app and the mobile app. I strongly support the idea to bring back loading splash screens and loading screen quotes back to the desktop client. While it may certainly not contribute to optimizing the app per say, adding personality to the app adds to its general user experience. The Fluxer project is open source and is heavily backed by its active community. I think adding back quotes is a great way to recognize the people who have contributed to the project's success. Furthermore, considering that Fluxer is self-hostable, giving instance operators the ability to add quotes by the communities that they serve helps personalize those instances to their communities. Should instance operators not care to show loading screen quotes for moderation reasons or other, then it should be toggle-able from the admin panel. Looking further ahead and down the line towards federation, should quotes be re-implemented, the instance that the user account originates from should be the instance that dictates the behavior of the feature.
- Maybe instead of a global toggle, a toggle setting within a user's profile is what would display their pronouns within user messages, like a checkbox labelled "check to display your pronouns in messages". That way, individual users who want their pronouns shown can enforce it, and others who don't really care for it won't have their pronouns shown.
- To add onto this issue, the limit is also held when attempting to pick KLIPY gifs for pfps and profile banners, which ultimately defeats the purpose of having that selection option available because most, if not all, gifs from KLIPY are larger than 512kb.