Would love to see mobile support, and a way to import/migrate from Slack. If migration is painless, our org would adopt this.
Chatto is now open source
271–280 of 319 posts
Re: Chatto is now open source
#272Congrats 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.
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.
Re: Chatto is now open source
#273> "The fastest way to give it a try is through Homebrew" for the 12 people that own a macbook, perhaps.
You can download the binaries from the GitHub release pages.
Re: Chatto is now open source
#274Couldn't help but smile because "chato" in portuguese means "boring", and this seems very easy to set up and use. Here's to more boring software! :)
Personally I've always found it funny that the widely used work software is called Slack which is very close to slacking (not working hard enough).
Re: Chatto is now open source
#275Earlier quoted context omitted.
[flagged]
You receive permission to use and modify a piece of software under conditions set by the creator. It is a license, not a gift. If you don’t like the conditions, use something else or create your own thing. I will never understand these complaints. Not only do you want stuff for free, you also want to impose your preferred usage conditions on the creator. Where does this entitlement come from?
Presumably people who choose the AGPL choose it because they believe it is a free software license. Either they should use an actual coherent free software license instead of one that is trying (and probably failing) to also be a EULA, or they should stop pretending that they are releasing free software.
Re: Chatto is now open source
#276> It’s designed to be extremely easy to self-host on your own infrastructure. Kudos for this. Per the docs: https://docs.chatto.run/ , > Chatto ships in a compact, self-contained binary > it uses NATS, a compact message broker that also ships with a built-in stream persistence engine [...] NATS is just as easy to provision as Chatto, and most of our examples will show you how. > you can also configure an external S3-…
Wow, it's using NATS! I used NATS extensively 10+ years ago, and I'm happy to hear it's still around. Our infrastructure had hiccups across our fleet of machines, but one part that always remained up and running without complaining on some dinky machine was NATS. Well, that and Redis. No complaints ever.
NATS and its built-in Jetstream stream persistence engine are a miracle. I love them both so much. And if your app is itself written in Go, you can just embed them for simple deployment scenarios (like Chatto does.)
Re: Chatto is now open source
#277Re: Chatto is now open source
#278Earlier quoted context omitted.
>I'm not aware of any models with full training data available, let alone available with full licensing. Check out the OLMo family from the Allen Institute for AI: https://allenai.org/blog/olmo3 Also worth looking at EleutherAI, LLM360, SmolLM, Apertus. Apterus even respects opt-out notices in their collection of the dataset they distribute. KL3M from Kelvin Legal is even trained on a 100% copyright-free legal/govern…
> Needing more electricity in a capitalist country literally causes the energy mix to become more green over time. Perhaps true, but meaningless except as a vanity metric if fossil fuel usage rises as well.
Re: Chatto is now open source
#279> It’s designed to be extremely easy to self-host on your own infrastructure. Kudos for this. Per the docs: https://docs.chatto.run/ , > Chatto ships in a compact, self-contained binary > it uses NATS, a compact message broker that also ships with a built-in stream persistence engine [...] NATS is just as easy to provision as Chatto, and most of our examples will show you how. > you can also configure an external S3-…
Wow, it's using NATS! I used NATS extensively 10+ years ago, and I'm happy to hear it's still around. Our infrastructure had hiccups across our fleet of machines, but one part that always remained up and running without complaining on some dinky machine was NATS. Well, that and Redis. No complaints ever.
Re: Chatto is now open source
#280Earlier quoted context omitted.
It is not looks or performance (I have no idea) I am talking about. It is the shape of the functionality — the intent of it. All these systems end up with far too much furniture on screen, and this appears no exception. I will test it, of course. But the promotional material argues against itself.
Then don't use it? I don't get the hate just because it doesn't fit people's use cases.
Though it does seem to (so far) be easier to host and less complicated than Mattermost, which is not nothing.