New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sharing on the Fediverse #4
Comments
custom or remove private network social |
@tiotrom Mastodon support is planned for the next release, do you have the URL sharer scheme for Friendica and Plerom ? |
Let me ping the Friendica developers and ask them to maybe help with this. |
Thanks ! |
@kimsible how is the Mastodon support working? If we don't already support it, then we can just add it this way if possible. |
@annando like this :
|
Friendica is using this format: The There is also the possibility of using the centralized services https://sharetodiaspora.github.io/ or https://share.diasporafoundation.org Example: This method will also work with Diaspora servers. |
Thanks you so much @annando ! @tiotrom I also found that : https://gitlab.com/Makhi/sharer/blob/master/assets/js/sharer.js Are Gnusocial, Movim and Hubzilla relevant ? |
I would say that GNU-Social is in decline. For Movim I don't know their relevance. Hubzilla is used as well. |
Even though gnu social is in decline they just announced a big redesign and recently added ActuvityPub support so if it’s not too much extra work why not ad a share to GNU social endpoint as well. Also adding a share to Lemmy button makes sense as well as it’s one of the more active fediverse spaces. |
Please add Lemmy (https://join-lemmy.org/docs/en/about/about.html) { |
Thanks for the suggestion, you can propose a PR with it, I'll review it asap. |
I don't know, if the json extended with this line is enough? |
I tried to add lemmy on my peertube-instance. so i added the lines and svg-image from the PR and run what's wrong? |
How about adding buttons for sharing on Friendica, Mastodon, Pleroma and the like? I think it would make more sense. Cheers!
The text was updated successfully, but these errors were encountered: