this post was submitted on 28 Sep 2024
12 points (87.5% liked)
Thunder App
2852 readers
1 users here now
An open-source, cross-platform Lemmy client for iOS and Android.
This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.
Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.
If there are any developers who would like to contribute, feel free to reach out on GitHub!
General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link
Android Releases
IzzyOnDroid: Link
Google Play: Link
iOS Releases
Apple App Store: Link
TestFlight Beta: Link
Related Communities
Nightly Community: Link
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Just wanted to chime in here! I think the implementation of cross-posts is up for interpretation (and can definitely be changed if one is preferred over the other). Generally speaking, there are two types of implementations:
Cross-posts only copy over the title and link of the original post
Cross-posts copy all content of the original post (title, link, body)
From this discussion, I do think that it could be valuable to add an easier way to inject the original body of a post into a cross-post. If you would like this to be a feature, please create a new feature request on GitHub!
A side note on cross-posts:
I believe that Lemmy considers any posts with the same link as a cross-post. There's no distinction (from the API) on which post was the "original" post, or whether a post was crossposted "from a community" vs "to a community". This is also the reason why there is additional metadata for each "cross-post" in Thunder. The additional metadata allows you to figure out when a given post was created to find the "original" post.
If you're curious about specific implementation detail, @[email protected] might be able to answer them!