I don't entirely hate toasts, I don't think your example is good, either. A toast is best for asynchronous, high priority, fleeting information. You don't want

I don't entirely hate toasts, I don't think your example is good, either. A toast is best for asynchronous, high priority, fleeting information. You don't want to stack them, or if you do you need some sort of inbox for them. You don't want to be spammed by them, you don't want them used as a stand-in for representing object state. For a checkbox, I'd rather the info be communicated "inline" maybe by color/shape/shading. A toast could be used like an info popup, perhaps i.e. "why did my checkbox get reverted". Or it could be for a high priority event, that just doesn't fit (well) in the current screen. But, again, care should be taken. If you communicate with your user, don't spam them - provide them with prompts and visually appealing methods to obtain their data. Toasts can be a part of that but shouldn't be the first tool reached for (ideally). I think the reason they are so dangerous is because they are outside the main UI flow, its technically and visually "easy" to use them.