Mikael Korpela

> opinionated way. We tended towards tools that take this approach (e.g. prettier), so maybe it's a good fit. Choice to use Angular.js was partly due to this too, since...

[Convo from Slack](https://trustroots.slack.com/archives/C0A3Q15SS/p1589728385042000) about Recoil: > This went out: https://recoiljs.org/ Facebook's answer to state management > one part sigh (yet another new thing...), and https://github.com/facebookexperimental/Recoil says it's experimental. they have...

A couple more lightweight solutions that might be more fitting for us compared to full blown Redux setup: https://github.com/tannerlinsley/react-query https://github.com/pmndrs/zustand

I've recently done more work with [React Query](https://react-query.tanstack.com/) and pretty convinced it's best solution for us. It can be much like what we have now with simple Fetch/Axios, but with...

Thanks for summarizing and collecting links to convos! You are right, I think message deliverability is most important to solve at the moment. Just nobody has had time or needed...

Looking closer into [stats](https://grafana.trustroots.org/d/000000005/transactional-emails?orgId=1&from=now-6M&to=now), I think this issue indeed is around spam & deliverability. I just made a new graph that highlights this well: These are from our email gateway,...

Next steps, in my opinion: - [ ] Dig through data to see if there are active spammers on TR right now. - [x] Work on adding message limitations, started...

Thanks for ideas! Adding that signup spam is actually another significant problem in addition to message spam. Anatomy of the latest spam attack was: - Create a TON (hundreds of...

Good finding with message length graph 👍 I deployed the limit today, as well basic spam detection which doesn't block anything but can help us see if something like that...

> the signup route could be rate-limited pretty aggressively to prevent spam account creation in the first place... if the invite itself is spam, that's the begging of reputation harm...