Thanks for the mention as talented developers.
Like @khrom I am not at all familiar with this application not using it so I took a quick look.
Technically, for a third party application to connect to Blurt, Hive or Steem, it just needs to integrate a library of the same language as the one used by the application.
The mastodon frontend uses React (Javascript) like Condenser (blurt.blog, blurtlatam...) so it can use BlurtJS or dBlurt (the one I did) libraries to create a bridge with the Blurt blockchain.
As said the problem here is rather time-consuming and especially cooperation of other entities. Because I did not see a system of management of plugins as we can have on Wordpress to do something like SteemPress I see only 2 possibilities remaining, to get the mastodon team to accept the change of the code so that every owner of an instance can use it, the second possibility is to fork mastodon and then convince every instance owner to use our version of mastodon instead of the official one.
Of all of us the one who knows mastodon best is I guess @fervi since he seems to start a crosspost project from Blurt to mastodon (Integrating Mastodon ...) so I guess he will have a more complete answer than mine.
What can be also interesting is to have a presence on mastodon, that each Blurt user having a mastodon account promote Blurt with mastodon posts and specific hashtags, maybe by organizing regular contests like what I try to do on twitter with [@]randula througth the BPUD-TWITTER Event with a result at the performance of the tweet.
I think this is the way we should go. We wouldn't even have to convince anyone because many admins and users would be interested in our solution themselves. Even if it didn't happen, we would gain a modern frontend.
If you are interested, organize a group of 3 or 4 programmers and write a proposal. We pay more than 2M BLURT per year for block explorer, so there should be no problems with spending another 2M on a modern, revolutionary application that has a chance of attracting new users and investors.
The question is whether we want to integrate Blurt directly into Mastodon or as an add-on to Mastodon. An add-on can be trustless under certain conditions and executed on the user side, where in the case of Mastodon if we do not have our own instance - this is risky.
On the other hand, I was thinking of doing it so that the script would read the posts on Mastodon and transfer them to Blurt. The data structure of Fediverse and Blurt (and other blockchains) is quite similar. Things like tags or post can be easily transferred.
@mariuszkarowski
Pytanie czy chcemy integrować Blurt bezpośrednio w Mastodon, czy jako dodatek do Mastodona. Dodatek może być trustless w niektórych warunkach i wykonywany po stronie użytkownika, gdy w przypadku Mastodona jeśli nie mamy własnej instancji - jest to ryzykowne.
Natomiast myślałem o zrobieniu tego tak, iż skrypt by odczytywał posty na Mastodon i przenosił je na Blurt. Struktura danych Fediverse i Blurt (i innych blockchainów) jest dość podobna. Takie rzeczy jak tagi czy wpis można w łatwy sposób przenieść.