this is one of the important differences between hubzilla / streams and mastodon. the latter continues twitter's model of following someone or being followed, making it easy to gauge one's popularity and reach. hubzilla / streams on the other hand knows only "contacts," with whom information is exchanged according to a set of detailed permissions that both parties can adjust according to their wishes and needs.
this makes it much easier to prevent spam or unwanted attention. streams comes with a rather narrow set of default permissions that can be relaxed on a contact-to-contact basis, or changed to a more relaxed basis model for those with a thicker skin.
@
phani00 (mastodon) This software evolved outside the influence of Twitter and has a completely different concept of what a connection is. In our universe it doesn't really map to 'follower' or 'following' - it's simply somebody with different permissions than an unknown viewer - or that has given you different permissions than an unknown viewer. It's entirely possible to have a connection that can view your files/photos but that you can't communicate with (and hundreds of other variations).
That said, you can visit
https://8633.pm/followers/axe and
https://8633.pm/following/axeto get the Twitter mappings we assembled. We use these in the 'lockview' tool to expand the list of message recipients but the url's aren't really exposed anywhere that you access them. No reason why we couldn't, except that they don't necessarily reflect the richness and nuances of our relationships.
These endpoints are only visible to those who have 'view_contacts' permission and this is controlled by your privacy settings.