It doesn’t seem to be working
The search only finds my mastodon.social account
Dispatching a message from mastodon.social doesn’t seem to reach Friendica (no notification or way to see the message) and previous attempt from Friendica to mastodon.social ends up the same (don’t receive a notification on mastodon.social or see the message)
It works now for some reason
Still can’t see it from 3 other Mastodon servers I tried🤔.(Friendica works)
But nice to see some progress🎉
But then now when people from other mastodon instances engage with mastodon.social, I can’t see it on my friendica instance.
mmmmmmh very weird behavior
Best way to get something federated to another server is following that account from one on the other.
How are people supposed to discover you from the Fediverse if they must follow you to see your messages in the first place?
Just a single follow would make your posts visible to all users on the instance.
That is also why I sometimes look up a post by url, to then follow a user from that instance.
But I cant follow his test account from Mastodon.
Try opening Emerodh's Friendica | emerodh @ Emerodh's Friendica from any other Mastodon server, it doesnt work, nor does any other interaction work.
I’m also experiencing that issue. Did @Emerodh set up forwarding from Friendica to Mastodon?
The Mastodon app does allow me to see their profile, Ivory is having an issue.
I haven’t any forwarding setup but the visibility of my friendica profile is set to public
Just to go back on topic:
There is nothing prohibiting creating/hosting an instance, that is what federation accomplishes.
So I would support creating/adopting one as service to operate, if only because it may provide refuge for people.
I would advise against creating alt’s for roles in the organization, just real people with their own opinions.
I would not support an organization account. (Weirdly enough, I don’t like the idea)
So, a multi-user instance?
I would like to suggest PeerTube. It is a multi-user ActivityPub enabled platform. Audio/Video is kind of in the Pirate spirit right? Doing the different thing is kind of our thing.
So strict rules, moderation. Original content under CC-BY? Or the Pirate License?
There already is https://peertube.european-pirates.eu and the German PirateParty also has like at least 2-3 different PeerTube instances (although most, including the PPEU one run outdated software).
Thinking about it, a more obvious solution would be equipping the website with the WP ActivityPub plugin and using that.
Is it possible to integrate Friendica with social media managers ? Like Mixpost for example ?
Some I believe, yes.
More do support Mastodon, however Friendica might still work if Friendica supports the Mastodon-API(which AFAIK can be achieved/improved with certain Friendica Plugins).
So I guess it depends, but Mastodon in any case is more supported.
I opened an issue for Friendica on Postiz-apps GitHub.
@Emerodh @Nick @Mab Good morning everyone!
I don’t know if you’ve managed to make any progress with creating profiles or creating actual instances, but I’d like to add an idea.
As you know, I already manage several instances (Friendica, Mastodon, Lemmy), and since this summer, I’ve also been managing a NodeBB instance called citiverse.it, created primarily to provide a potential alternative to local Facebook groups.
NodeBB is a “Forum” platform that does exactly the same things as Discourse, with the ability to create categories reserved for certain user groups and public categories. The most interesting thing, however, is that it offers the ability to “federate” certain Forum categories, making them visible and interoperable with the entire Fediverse.
Discourse has never gotten this far, and the federation implementation in Discourse is primitive, insufficient, and confusing (Discourse apparently only federates categories without federating profiles), not to mention the fact that it likely won’t be improved in the future.
I don’t know if this would interest you, but instead of creating an instance, you might consider porting Discourse to NodeBB.
Now that I’ve had the chance to try it out for a few months now, I can assure you that it’s a lean, powerful, feature-rich, stable, well-maintained platform that doesn’t require a lot of resources. And so I can really recommend it.
Let me know if you need any further information; I’m available. The lead developer of NodeBB is Julian: julian | NodeBB Community , and this is the NodeBB website: https://nodebb.org/
Hi @macfranc,
Thank you for this suggestion. These days it is the Outreach team of the Secretariat that is in charge of our Discourse, so if they would see a need to change the tool we use we could look into options. They are still in the transition to get used to being responsible for the forum we have, so right now I don’t think we have the capacity or need to change it.
What are the problems with the current tool you think would be solved by porting our current forum to a new tool?
Of course!
What are the problems with the current tool you think would be solved by porting our current forum to a new tool?
What problems with the current tool do you think could be solved by migrating our forum to a new tool?
Adopting NodeBB over Discourse certainly has many advantages, but it’s impossible for me to answer your question because I don’t know what problems the PPEU staff identified in managing the Discourse-based forum, and I’m not even aware that there are any problems.
My observation was simply that migrating the forum from Discourse to NodeBB simultaneously opens an instance of the PPEU Fediverse, since a federated forum is effectively an instance of the Fediverse. Naturally, depending on the modders’ choices, some categories may be excluded from the federation or even reserved.
Discourse, on the other hand, doesn’t really allow federation: that development has stopped and remained at a primitive level, with an objectively unusable user experience.
But this is the usual problem with all market leaders: once they reach leadership, they stop improving…
What I can say is that NodeBB is a bit faster and less bloated than Discourse; the architecture used favors a near-real-time experience.
Installation and management would seem simpler, but this also depends on how familiar you are with the Node.js ecosystem.
NodeBB is closer to the experience of contemporary web applications than Discourse’s more traditional layout and offers an impressive number of plugins and greater freedom of customization. Finally, the web app also works very well.
The only problem I’ve seen is low activity from our members. And one instance of spam accounts vandalizing the forum. But that we handled fairly quickly.
Our forum is primarily meant as a place where people from our Member parties can stay in touch with us and each other. From what I have seen I think what we have is sufficient for that.
But at the end of the day, that is a decision for the Outreach team to make.