Fluxer: A chat app that puts you first
fluxer.app
Fluxer is an open-source, independent instant messaging and VoIP platform. Built for friends, groups, and communities.

Several years ago I had a Discord community with hundreds of users. This was an IRL community, so it was very difficult to abandon but I did anyway. Tried to get people to leave but they were unwilling. So I handed it off to another member and deleted my account. Now that admin has contacted me again and let me know everyone is ready to leave. I found Fluxer yesterday while poking around #Discord on Mastodon and I think we’re going to end up there.

Fluxer is still very early in development and they have plans for many advanced features in the roadmap but it’s very feature-rich today. Current monetization plan is freemium + Patreon-like monetization. I understand that may be a dealbreaker for some but there aren’t a ton of other great options, and everything is open source, and self-hostable, and if you do, you get all of the premium features for free, while still communicating with the main instance over federation (in roadmap). That still leaves it susceptible to Mattermost-style enshittification but honestly rolling back updates solves most of those style of problems.

  • tb_@lemmy.worldEnglish
    122·
    13 hours ago

    I do have to wonder, given the age of the app and the seeming lack of contributors on GitHub, how vibe-coded is this app?

    • Stefen Auris@pawb.socialEnglish
      11·
      13 hours ago

      If you check the dev’s blog you’ll find they’ve been working on it for 5 years and published a squashed version of the history on GitHub when they cleaned up the code for public release

      • tb_@lemmy.worldEnglish
        21·
        6 hours ago

        Welp, that blog wasn’t linked anywhere on the main page.
        Reading through it, it actually makes it all seem a lot more reasonable, that’s good. It’s just difficult not to be skeptical in <current year>.

        Link for the interested.

        Edit:

        Fluxer was largely built before LLMs became a normal part of day-to-day development. I do use them now, but in a limited way: as a rubber duck and for mechanical implementation work when I already have a detailed spec. I treat the code it outputs like I would any external contribution.
        No LLM designed the system, wrote the specs, or made architectural decisions. That was all me. I only use LLMs when I already know the platform well enough to review the result properly.

        That seems fairly okay.

        Further edit: wording.

        • Stefen Auris@pawb.socialEnglish
          2·
          12 hours ago

          Now that you mention it, I couldn’t find the blog when I checked. I thought it was just me not being able to find a lit candle in a dark room lol