Understand how to follow mastodon accounts

!Hubzilla Support Forum
I am really interested in how to create interactions between mastodon and hubzilla account. Is that possible?
From mastodon I am able to follow specific users from a hubzilla hub but I cannot see their posts.
From here, I don't know ho to follow/include in my channels a mastodon account.
Any help would be much appreciated :)
I think that information should be displayed much more visible than /siteinfo/json
The Federation Expectation (TM) is in need of some expectation management, i.e. education. To use an image: you can expect a bike to transport a pizza across town, but you should expect to use an armoured car to transport many different and larger items you cannot see without permission rather than a bike. The same is true of clients in the federation space, and - more importantly - the underlying protocols used.

This is not new, people only need a reminder. There is a difference between a mail only client and a personal information manager like Microsoft Outlook. A PIM like Outlook can do mail, contacts, tasks, calendar and meeting invitations, instant messages, etc..

PIMs support a number of protocols to send and receive different kinds of items, either using open protocols, proprietary extensions to open protocols, or just using a proprietary protocol. A simple mail client may support only one protocol to receive email, e.g. POP3 or IMAP, and perhaps only SMTP to send email. Outlook also has MAPI, since there is little need to transfer mail when you can just move or copy it from the sender's folder to the receiver's folder on the same server at an office.

In the federation space, Hubzilla is more like a PIM or a content management system, given it provides both social, wikis, chats, forums, games, etc, etc in a decentralized manner, while for example Mastodon is more like a mail client. I do not use Mastodon, apologies if this image is wrong, but as far as I know it does one thing - send messages between hubs.

Underneath the Hubzilla client with all its many publishing solutions is the protocol Zot. Mike is nearing completion of version 6 of this Web Message Transfer Agent. Zot is different from other WebMTA services. How? Zot is architecturally different from other HTTPS-based "social communications" protocols such as OStatus, ActivityPub, and Diaspora. The primary differences are:

  • Support for nomadic identity where an identity is not permanently bound to a DNS server.
  • MUAs built on top of Zot are able to use and express detailed cross-domain permissions.
  • Encryption negotation for additional message protection in addition to HTTPS
  • Zot does not define an absolute payload format for content. Implementations MUST support ActivityStreams. Additional message types and serialisation formats MAY provide vendor specific enhancements.
  • Federation between other WebMTA protocols is not hampered by unnecessary restrictions on 3rd party communications.
  • Messages from incompatible systems may be relayed to other sites which do not support the 3rd party protocol.
  • Detailed delivery reporting is provided for auditing and troubleshooting; which is critical in a distributed communications service.

You can read about Zot and Zot 6 at https://macgirvin.com/wiki/mike/Zot%2BVI/Home
unfortunately those who come to use alternative networks, ie those foss, and not those of corporations, are still few.
And these few, almost all ( not all) unfortunately, come in these networks with the same or similar mentality, and the same desires, and very often these desires are quite incomprehensible, dictated by other desires, but here we should look at the psychological aspect and social unease. .. but I do not want to go into certain complicated topics.

In any case, most people who use these networks have the desire to create communication between the 4 or 5 "famous" foss networks, and this is a fact that we can not ignore.
This is a test