Lucas and I decided to stall this ticket until we discussed this with whole team, since this gets a certain complexity with the injection and rendering of links. Lucas already left 2 options on story how to achieve this.
However we also agreed, that this would be a significant change on our current architecture, which should be discussed in advance and not in the review.

@LucasWerkmeister Do you have the rights to do that or do we have to make the way around by wikidata beta?

Just a question regarding 3rd parties, which are not using Graphite. Do we make Graphite as a dependency now, or we wanna try to make this feature some how not effective if it's (Graphite) not enabled/available?

As mention in T235054 we are actually using deep compare instead a json based compare, therefore the relating patch save now a clone of the actual object instead of the json string.

@Lucas_Werkmeister_WMDE figured out that the order of the index is not preserved, therefore the patch using now a deep compare.

We actually used: https://en.wikipedia.beta.wmflabs.org/wiki/Wikidata (the twitter hashtag)

Maybe the other way around this is to have explicit type safety on the methods itself: https://github.com/ktsn/vuex-smart-module

I have a couple questions regarding this:
-> Do we make central auth as a dependency of DataBridge (especially regarding 3rd parties)? If yes we should somewhere doc (as well as ULS), or?
-> What kind of behavior we consider as a bug of central auth? (like if I am logged in on desktop and change to mobile, my status is gone, or the described behavior of Michaels investigation)
-> I think the bullets 3 and 4 can be reconsidered in T231209 as well, right? (iff we touching the API for userinfos)
-> Do we need more then one option? (I am also okay with the passive approach)