Like how in Devise we can have our own RegistrationsController that subclasses Devise::RegistrationsController, then in the routes we tell devise to use that controller instead (i.e. devise_for :users, path: 'auth', controllers: { registrations: 'registrations' }), we should have a way to subclass notifun's MessagesController, PreferencesController, etc, and route to ours.
Like how in Devise we can have our own RegistrationsController that subclasses Devise::RegistrationsController, then in the routes we tell devise to use that controller instead (i.e.
devise_for :users, path: 'auth', controllers: { registrations: 'registrations' }), we should have a way to subclass notifun's MessagesController, PreferencesController, etc, and route to ours.