3 ms·

Congrats for open sourcing it, looks interesting! How does this compare to fluxer.gg though? The part that I really liked about chatto is that it seems to be

Congrats for open sourcing it, looks interesting! How does this compare to fluxer.gg though? The part that I really liked about chatto is that it seems to be made very easily to self host which is something that I really appreciate actually.

roshannarma 3mo ago
I have been patiently waiting for fluxer, but honestly I just want to self host and have it available and fluxer has been sitting on that for a while
- hampus 3mo ago
  I'm the developer behind Fluxer – self-hosting is ready to use already [1][2][3], people are using it actively currently, and I'm currently working to make account switching across instances in the desktop app a reality. This, with a big voice update around the corner, will let us move much faster moving forward! [1]: https://fluxer.app/blog/mobile-clients-and-fluxer-v2 https://fluxer.app/blog/mobile-clients-and-fluxer-v2 [2]: https://docs.fluxer.app/operator/get-started/ https://docs.fluxer.app/operator/get-started/ [3]: https://github.com/fluxerapp/fluxer https://github.com/fluxerapp/fluxer
  - lrae 3mo ago
    Great work! Imo the most promising Discord alternative so far. But I have a question, and maybe it is answered somewhere and I just couldn't find it, but is there currently a way to move a created community from e.g. the official hosting to self-hosted? I saw the mention about possible federation in the future, which would solve that (kind of), but currently it's not possible, I guess?
    - hampus 3mo ago
      Thanks! And you're right, the future federation work is what will make it possible to implement support for transferring communities across instances natively.
hendrikmans 3mo ago
I love Fluxer! Hampus is cool and what he's built is super impressive. I would say the primary difference is that Chatto doesn't squarely aim for being a _Discord_ alternative. There are no plans for providing a Discord-compatible API (which I think Fluxer does.) The other main difference is that Chatto is designed, on purpose, to serve individual communities from tiny deployments, instead of large mega-instances that power many communities. Chatto deliberately avoids content federation to remain compatible with business use cases, and also to stay simple enough so it can run from a single binary.

roshannarma 3mo ago

I have been patiently waiting for fluxer, but honestly I just want to self host and have it available and fluxer has been sitting on that for a while

hampus 3mo ago
I'm the developer behind Fluxer – self-hosting is ready to use already [1][2][3], people are using it actively currently, and I'm currently working to make account switching across instances in the desktop app a reality. This, with a big voice update around the corner, will let us move much faster moving forward! [1]: https://fluxer.app/blog/mobile-clients-and-fluxer-v2 https://fluxer.app/blog/mobile-clients-and-fluxer-v2 [2]: https://docs.fluxer.app/operator/get-started/ https://docs.fluxer.app/operator/get-started/ [3]: https://github.com/fluxerapp/fluxer https://github.com/fluxerapp/fluxer
- lrae 3mo ago
  Great work! Imo the most promising Discord alternative so far. But I have a question, and maybe it is answered somewhere and I just couldn't find it, but is there currently a way to move a created community from e.g. the official hosting to self-hosted? I saw the mention about possible federation in the future, which would solve that (kind of), but currently it's not possible, I guess?
  - hampus 3mo ago
    Thanks! And you're right, the future federation work is what will make it possible to implement support for transferring communities across instances natively.

hendrikmans 3mo ago

I love Fluxer! Hampus is cool and what he's built is super impressive. I would say the primary difference is that Chatto doesn't squarely aim for being a _Discord_ alternative. There are no plans for providing a Discord-compatible API (which I think Fluxer does.) The other main difference is that Chatto is designed, on purpose, to serve individual communities from tiny deployments, instead of large mega-instances that power many communities. Chatto deliberately avoids content federation to remain compatible with business use cases, and also to stay simple enough so it can run from a single binary.