> In addition, since [opaque] tokens are stored on the server, they can carry more data than JWTs, and you can easily revoke them if necessary.
Opaque tokens don't carry _anything_. THey're just an identifier used to query a database inside your application. The article repeatedly implies there is meaningful content inside an opaque token.
More messiness:
> Opaque tokens cannot be read by people that hold them since they are undecodable strings. A client cannot read the contents of the token
Sure they can be read. It's just that the totality of the content _is_ the token itself.