Better way of handling server-side errors?

I see that #52 gives an example of adding server errors to the changeset so they are visible to the user but this strikes me as somewhat verbose, especially if it is required on many models/`save()` actions.

Is there a better way to approach this, perhaps by building it into the library? Or could something be accomplished with a service of some sort?