• 1 vote
    Awesome, thanks!
  • 1 vote
    Not resolved. Tried going through the latest web client and seeing my bookmarks, only to see "You lost access to this saved message. Remove?" with no message URL or way to know exactly which community/channel/message is gone. Stable Web 2026.1118.81740, macOS 10.15.7 (arm64), Microsoft Edge 151.0.0.0, Locale en-US
  • 1 vote
    On web, I still see this (attached). No reference URL or way to see what the community ID/channel/message ID was that disappeared. Is that expected?
  • 2 votes
    While we're adding support for status pages, can we also get cstate? https://cstate.uncascade.com/ static, light, easy, open source :)
  • 3 votes
    It depends on the federation model, I assume DMs would be a minimum required component for identity-only instances. So, every instance must store a copy of DMs. Although that might change based on federation design
  • 1 vote
    i love fluxer and i love this keep cooking yall can't wait for message packs the OP sounds remind me of the first game i ever made in DOS :)
  • 3 votes
    Please consider this for academic accessibility in the education market. Would help research groups and academics use fluxer
  • 1 vote
    Idea: what if the splash screen was default-off (so the default behavior was the silent start that we currently have) but the splash screen was enable-able by a Settings toggle, for users who want to see it and are confident their computers can handle the extra rendering on stratup?
  • 1 vote
    I think an S3/media URL is already possible? It might just need to be documented.
  • 1 vote
    CDNs are normally placed at the edge of the application, not in the middle -- so after the web server, not between the web server and S3. I won't comment on the social proof of "the internet uses them too much". Everyone can use whatever CDN they choose to, of course.
  • 1 vote
    I think this is already possible - could you alleviate this by placing your own cdn e.g. cloudflare in front of your fluxer service on your home connection?
  • 8 votes
    Modification - not just 1 role, but any combination of roles, to simulate users who have >1 non-overlapping role?
  • 2 votes
    I think this would be a good idea as an ACL customizable per role - "see limited message history" with a textbox for number of days or hours that the role can see rolling message history for
  • 1 vote
    Agreed. Plutonium behavior would have to change, in my opinion, to "no re-roll after expiry" unless the team is willing to maintain the logic behind "did the user change their discriminator via Radium even though they had Plutonium?"
  • 1 vote
    I can see the argument for de-pricing discriminator customization, however I think it's a value proposition of the Plutonium subscription (yes, I know, I'm a Plutonium subscriber, so I am psychologically biased to "protect my purchase", but I can see your perspective). Granted, I'm not an ecommerce wizard or even like thinking about ecommerce topics, so my opinions on value props and subscription allure is limited. I think raising the bar for discriminator customization to "significant in some way for fluxer" is risky - why: it would encourage spam "contributions" just for the purpose of the perk, or the perception that "those who are selected for discriminator selection" are some kind of "sEkRiT cLuB" that are opaquely determined by platform staff or moderation. I wouldn't like to see Fluxer get that kind of perception for having those groups (I know I'm not the Fluxer team, but that's just my wish as an observer and community member).
  • 1 vote
    Agreed that it should not be a subscription. I agree with vicky above.
  • 1 vote
    I have decided that a one-time fee will be my proposal, per customization of discriminator, for non-plutonium users.
  • 2 votes
    Thank you for your detailed reply. For (1): I propose that a one-time purchase of discriminator changing would be "forever". If someone wants to change their discriminator down the line, they would pay again, if they do not have the Plutonium subscription. For (2): I have reconsidered and no longer think discriminator changes without Plutonium should be a recurring subscription. One-time purchases, on the other hand, make more sense since the change is one-at-a-time. I was initially thinking that identity stability would be the allure of a subscription for Radon/Radium, but after your points raised, I think the same stability can be achieved by one-time purchases safely. Thanks again for your thoughtful reply.
  • 2 votes
    I think an instance-wide configuration option only on initial setup makes sense. It defeats the purpose of auditing if a non-audited fluxer instance “becomes” an audited instance (the non-audited history “taints” its absolute auditability) Maybe the option can be turned off if it had been enabled during setup -- essentially, a feature that "goes" only one way. I am aware of a user who wants to host a fluxer instance for business use, and is willing to fund/support the development needed for the usecase.
  • 2 votes
    Yes please That is my comment Yes please
  • 1 vote
    Or, maybe it isn't a subscription. Maybe it's a one-time payment for a non-subscribed user that is cheaper than plutonium to change their discriminator?
  • 1 vote
    Edit history would ideally work like github discussion's edit history - with each revision showing a diff when clicked
  • 1 vote
    I favor the smaller subscription for just the username/tag combination
  • 1 vote
    custom windows in the desktop app. I should have specified. I will edit my post. I can already do this with browser windows, with each window being a different focus
  • 1 vote
    yippee yeehaw thank you chef