Mostly just used for moderation.
Main account is https://piefed.social/u/andrew_s

  • 62 Posts
  • 185 Comments
Joined 1 year ago
cake
Cake day: July 24th, 2023

help-circle



  • Not sure where to post this. Sometimes (in ways that are difficult to replicate), I get a JSON response for a reddthat post in my browser instead of an HTML one. It’s happened before on mobile (Chrome) and today also desktop (MS Edge), so I was able to make a screenshot:

    I’m assuming it’s related to 0.19.4, but maybe others have seen this behaviour before the upgrade. Apologies if you’re already aware - I had a quick look for other mentions but didn’t find any.











  • Well, there’s good news and bad news.

    The good news is that Lemmy is now surrounding your spoilers with the expected Details and Summary tags, and moving the HR means PieFed is able to interpret the Markdown for both spoilers.

    The bad news:
    It turns out KBIN doesn’t understand Details/Summary tags (even though a browser on it own does, so that’s KBIN’s problem).
    Neither PieFed, or KBIN, or MS Edge looking at raw HTML can properly deal with a list that starts at ‘0’.
    Lemmy is no longer putting List tags around anything inside the spoilers. (so this post now looks worse on KBIN. Sorry about that KBIN users)


  • Firstly, sorry for any potential derailment. This is a comment about the Markdown used in your post (I wouldn’t normally mention it, but consider it fair game since this is a ‘Fediverse’ community).
    The spec for lemmy’s spoiler format is colon-colon-colon-space-spoiler. If you miss out the space, then whilst other Lemmy instances can reconstitute the Markdown to see this post as intended, Lemmy itself doesn’t generate the correct HTML when sending it out over ActivityPub. This means that other Fediverse apps that just look at the HTML (e.g. Mastodon, KBIN) can’t render it properly.
    Screenshot from kbin:

    Also, if you add a horizontal rule without a blank line above it, Markdown generally interprets this as meaning that you want the text above it to be a heading. So anything that doesn’t have the full force of Lemmy’s Markdown processor that is currently trying to re-make the HTML from Markdown now has to deal with the ending triple colons having ‘h2’ tags around it.
    Screenshot from piefed:

    (apologies again for being off-topic)










  • A bug report for software I don’t run, and so can’t reproduce would be closed anyway. I think ‘steps to reproduce’ is pretty much the first line in a bug report.

    If I ran a server that used someone else’s software to allow users to download a file, and someone told me that every 2nd byte needed to be discarded, I like to think I’d investigate and contact the software vendors if required. I wouldn’t tell the user that it’s something they should be doing. I feel like I’m the user in this scenario.