Now, they charge by a new metric: audiences. And your audiences also include unsubscribed emails! So, even if someone in your list has unsubscribed, they are still counted in your audience.

That's going to be extremely ugly. Nothing about this makes sense. Your JSON schema should just have one object that has {"is_enabled":true}, or something like this {"name":"change","is_enable":true}.

these events can break the flow of the game and force the player to repeat sections until they master the event, adding false difficulty to the game.

This approach is preferable to overriding authenticate_user! in your controller because it won't clobber a lot of "behind the scenes" stuff Devise does (such as storing the attempted URL so the user can be redirected after successful sign in).

Yes, you are right. That was a very bad workaround. Stubbing methods on NilClass can be compared to switching to dark side of force. Powerful but comes with a huge price. I highly don't recommend using my workaround from 1 year ago.

When the computer created such amazing potential, humans decided that their human genius machines could be handy if they implemented all the pre-existing genius practices.

can you break this, thouugh? like can you override kind_of? but not is_a?

You can override an alias without overriding the aliased function. So yes, you can override kind_of? without overriding is_a?