[Verifying my OpenPGP key: openpgp4fpr:FED82F1C73FF53FB1EE9926336615E0FD12833CF]
HmâŚ
The workaround sounds good. It will also work for Friendica-Posts, if i forget to set a Title.
I donât think, the Microsoft^WMastodon will move more to fediverseâŚ
So iâm not sure⌠should every other service deploy bad and breaking workarounds, or should we accept, that Micros^WMastodon is giving s fuck, being part of the fediverse?
Your Workaround would be good for Lemmy. For sure. Better would be a configureable subject in Mastodon for those admins, which want to interact also with lemmy.
Gitea itself does not work on federation⌠iâve learned this few weeks ago. Only a fork.
Then github changed its model to a company for profit, or so.
Now codeberg and others are working on another fork https://forgejo.org which is in itâs first release binary-compatible to gitea AND this fork gets federation. Codeberg will run on it.
So i think, leaving github will be a very good idea. But a much better idea is to wait for the working federation in forgejo
đ
As i often say:
Each Node has to bring itâs own xmpp-server. When you log in to your mastodon, friendica or what else, you are instantely logged in in this xmpp-server.
The fediverse-id is also the xmpp-jid.
In the contact you can just click on âchatâ and you will be connected with this xmpp-account.
Conversejs or jsxc bring such small-chat-windows as you know from facebook.
The roster is your contact-list.
AND conversations allows you, to add your fediverse-chat-account as additional account⌠so you can use it on your smartphone without being logged in in the fediservice.
Xmpp has a small footprint. So itâs ideal. Mucs are also possible for groupchats.
If it is preconfigured, and easy to install (look at snikket!), there is instantely a secure chat in the fediverse.
i did this IN the container named lemmy.