There is nothing wrong in itself with keeping up-to-date with master by rebasing. That's not the issue which is described by the link. The main problem is that

There is nothing wrong in itself with keeping up-to-date with master by rebasing. That's not the issue which is described by the link. The main problem is that the feature branch is being actively developed on by multiple persons. The problem arises when, you rebase commits which have already been shared. The smoking gun is that you need to force-push, i.e., rewriting someone else's history (in other words "messing" up someone's chain of commits.)