Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
One problem is that the API call that returns the feed doesn't provide crosspost information (unless that's changed in 0.19.4+ since i'm still developing against 0.19.3).
Crossposts in the feed have to be done client side, and you can only "roll up" ones that have the same URL (Tesseract can optionally roll up on identical titles if there's no URL). However, that's limited to just the ones that come through in the same fetch (unless you store all posts locally, which is something I'm considering in the future for offline support; most apps don't).
The API call that populates the
/postpage does provide that crosspost data, and I've thought about making an option to combine the comments from each into one "megapost". But there are a few problems with that:Officially, crossposts are only compared against the URL. The crossposts may have different titles, and one or both may have different text in the post bodies. Which do you display?
Culture clashes. Let's say there's an article posted called "Ford Releases Their New Monstrosity 5000". It gets posted to
c/carsandc/fuckcarsby different people with different intentions.The tone of the comments would be wildly different since the two communities are basically ideologically opposites. The replies to comments that came in from
c/fuckcarswould be responding to car enthusiasts fromc/carsand vice-versa. It would basically be a form of soft brigading.I've wanted to do a feature like that for a while now, but every time I've tried to plan it out, it always seems like it would just make things worse. Even with indicators as to which community the comment came from, it's still not ideal.