from curious@feddit.online to fediverse@lemmy.world on 12 Dec 23:11
https://feddit.online/post/165747
I’m discovering the threadiverse through a new account and software.
I wanted to crosspost a Lemmy post into another Lemmy community. Can I do this from a Piefed instance?
EDIT : No, you can’t. You can only reference another post using a link.
Here is an example of a crosspost btw two Lemmy instances. Piefed only allow to access the link btw them
feddit.online/post/165743
Here is an example of copy-pasting a link to a Lemmy post into a new Piefed post. There is only the link but no proper crosspost
feddit.online/post/165808
Here is an example of copy-pasting a link to a Piefed post into a new Piefed post. There is only the link but no proper crosspost
feddit.online/post/165842
Note that I attached in my test the post to the software of the poster not of the community.
Right now Piefed voluntarily allow crosspost for bot only as stated by @Rimu here
codeberg.org/rimu/pyfedi/issues/206
I’ve added a feature for a limited form of cross-posting - on any bot-created post, if it hasn’t been posted elsewhere yet, there is a cross-posting button. This is most obvious at piefed.social/c/propublica@rss.ponder.cat where a large percentage of the links have already been posted in ‘real’ communities.
Long-term we will want to have cross-posting on all post types but I don’t really want to encourage cross-posting until we handle duplicate posts better, like Mbin does.
Thank you all for helping me figure this out
2nd EDIT: We figure out in the comments a way to get the crosspost pick up by Lemmy but it is only for post having an external reference and it is not picked up by Piefed.
threaded - newest
Cross-posts are not fully implemented on Piefed: codeberg.org/rimu/pyfedi/issues/206
Too bad
I would say you can
Unfortunatly, no :-(
A cross-post is just a post that links to the same URL as another post. The codeberg Issue that Blaze linked to mentions an exception, but other than that, there's not a convenient button that copy-pastes a post's title, body, and URL into a new 'Create Post' form. You can do it manually though, and everything that receives it will detect it as a cross-post, because everything is just looking for matching URLs.
I have to disagree with you. When I crosspost properly, I got the list of each community in which the post is found. I can also open the post in each community in my instance with a simple click.
I vaguely remember reading that PieFed promised that cross-posts will have a single comment space but it seems we are not there yet. I tried what you told me but I could get crosspost. I just have posts referencing one another with a hyperlink.
The post you mentioned ('melting is tough') isn't picked up as a cross-post on PieFed instances because the dates are too far apart. A restriction that Rimu wanted was that they should only be detected if they were within 7 days of one another.
However, if you take that URL (https://lemmy.world/pictrs/image/91f96cc8-a194-4cb8-abc6-505261e65420.jpeg), and make a new post with it, then the post you mentioned now shows that it has a cross-post.
Interesting. Let me try again with posts with closer dates.
Do I need to use the URL of the picture or of the post itself to crosspost it successfully on Piefed?
The picture (or whatever external resource a post is pointing to, like
https://bbc.com/news/article.html)Here is a 4-days old post that I just crosspost from and to Lemmy
https://feddit.online/post/165936
It is not pickup as crosspost either.
Then I tried to crosspost it from Lemmy to Piefed using the link of the image and got an error. But many parameter could be the cause. I'll try again.
It's doesn't seem like feddit.online is aware of the other community (
forumlibre@jlai.lu), so it doesn't have a copy of both posts, so it doesn't know that they are cross-posts.If you bring that community into feddit.online, then create a post with the same URL as a recent post (e.g. https://files.catbox.moe/pebvir.jpeg), then they'll show up.
Beginner mistake. Always make sure to follow a remote community before using it in test 🤦 Thanks!
So... I made sure to federate !forumlibre@jlai.lu to feddit.online. I joined it then done the same test : A crosspost from Lemmy to Lemmy with no external reference but a text body and still no crosspost is picked up by Piefed
https://feddit.online/post/166043
Hey, it’s me.
How can Piefed know it’s a crosspost if there’s no common link between the two posts (usually the link to the article in most posts, or the picture for some others) ?
If I remember correctly, Lemmy matches two posts with the exact same title. I think I don't it by mistake once. Maybe Piefed do the same, maybe it is implemented differently.
Let me check.
As pointed out in another comment
That’s how Lemmy works too. Trust me, I crosspost quite a lot, as you know
Maybe that's how Lemmy detects crossposting but there is a visual mark of the crosspost in the interface and I have access to a link to the post in the other community that opens in my instance rather than in another instance. That is something very practical that make Lemmy crossposts more than posts with similar content. And that is something I didn't find in Piefed.
Yes, as mentioned in the other comment with the GitHub ticket, it’s not implemented yet
I was mistaken. Lemmy only detected automatically the link when title, body and external reference where the same. It did not do it when the title and body was the same on posts without external references.
First case
https://jlai.lu/post/13228928
https://jlai.lu/post/13228821
Second case
https://jlai.lu/post/13228938
https://jlai.lu/post/13228935
Indeed, that makes sense as the title can be edited, while the URL to the external resource can’t
Here is another 4-days old post, this time with an external ressource crossposted from Lemmy to Piefed.
It gets picked up as crosspost by Lemmy but unfortunatly not by Piefed
https://feddit.online/post/165962
Watching it from Piefed, I have no way to see that it match a post in another community as it doesn't even refer to the original post using hyperlink.