moeffju

Maybe one caveat: his wasn't a trial of healthy people trying to optimize their cholesterol. It was secondary prevention, i.e. people with previous cardiovascular events. Looks like a solid study though.

Why would I trust them after the Framework laptop debacle?

I realize this is off topic, but why do people use Claude of all models to write these, when its style is so obvious and so grating? I just immediately hit Back on the first Claudism.

It has audio and video call support in any room, so like huddle.

Tauri is like a nicer Electron, instead of shipping a full Chrome with the app it uses the platform's browser libraries. So the app looks almost exactly like the mobile web version, which looks like the desktop version that you can see in the screenshots on Chatto.run

Inspired by Chatto, I also built some prototypes on the NATS (+Go) stack and it's been a dream. Feels like a severely under-hyped technology :D

What would you expect that to do beyond a "here's a link to the instance, sign up there"? You can combine it with Discord-like roles and gate channel visibility and rights on that, so even if someone else would sign up you just wouldn't give them the "in-group" role for example. Are you thinking of an "invitation" type link with a one time token or something?

I've been trying to use Matrix for years and I still hate it at least half the time, it feels clunky, slow, cumbersome to use, the clients are hit and miss quality, and people (including myself) keep losing keys or identities for random silly reasons.

Compared to that, Chatto is just easy, nice, and FAST. It's a chat that I actually do like to use - I don't think the landing page is over promising there :)

I would guess that in these cases you would just not allow users to self-delete their accounts? But for most users and providers of Chatto I think automatic right-to-deletion compliance sounds nice :)

Whimsy? ^^

Oh, and the protobuf based realtime endpoint should make it very easy to build bridges, too.

I think time will tell, but one of the main things I like about Chatto is just how fast everything feels, and the protocol design is a good part of that I think. Data on the wire is just very small and optimized (last I checked, I didn't look at the latest protocol iteration yet). It was already very fast with the older GraphQL based API but now it's even quicker. With Slack and Discord, every channel switch and scrolls take visible time.

For now it's just a Tauri wrapper, so it looks more or less like the mobile web / PWA except it might be easier to handle notifications and share intents etc. compared to a pure PWA play. Now that the API is settled, it might make sense to go pure native.

The Tauri wrapper was originally just for desktop convenience and the Android target was more of a proof of concept initially.

For me, primarily the performance tbh. Chatto just flies and Slack feels incredibly sluggish. And from the "vibes" it just feels better designed, I like the overall user experience, it feels technologically solid but also looks nice and works how I feel it should. Hard to put my finger on it exactly.