8
Is zerowaste at odds with nutrition? (slrpnk.net)
submitted 3 months ago by to c/nutrition@mander.xyz
11 comments fedilink hide all child comments
 

cross-posted from: https://slrpnk.net/post/40923742

I always eat whatever thing in the fridge is closest to spoiled to ensure I waste nothing. And it’s a race because food is often already on the edge when I bring it home, to prevent waste and also save money (as it gets marked down because of the age).

I found out a friend does the opposite. She eats the freshest veg she has because she says vitimins deplete as the veg ages. She wants to maximise her nutrition.

Is freshness really significant for vitamins? Someone in my family does the same thing. Always eats the freshest food. And as a consequence she is frequently tossing food that lost the competition to be eaten early.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 2 points 3 months ago* (last edited 3 months ago) (6 children)

I have multiple Lemmy accounts on different instances, some of which default to the stock Lemmy client. The accounts that use the stock Lemmy client create the same kind of links to parents of crossposts as Alexandrite. From there, I’m not even aware of a way to link to a post or comment in a generic or indirect way that can be done without knowing the host of the reader who will visit it. I’ve only noticed that links to communties can have a host-neutral syntax. Perhaps the nodes I use that run stock clients are out of date. The latest version I’ve checked this on is 0.19.20.

Worth noting that the smarter behaviour you have experienced may not be related to the OP’s client, but rather your own server or client, and perhaps the software on your side of this does not recognise !zerowaste@slrpnk.net as a subscribed community by which there exists a local copy of posts to replace the link with.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 1 point 3 months ago* (5 children)

    In my experience, when I cross-post using the built-in Lemmy cross-post function (the two little squares between the star and dots menu below the post header), it shows up like what is in this example post. In other words, it shows a relative link to the cross-post on both the original article and the cross-post. The cross-post link on this article where we are currently discussing this shows me "cross-posted from: [a hard-coded link to original post on solarpnk.net]", and the original post doesn't mention that it's been cross-posted elsewhere.

    I'm not complaining, by the way, I'm just curious what causes this because I have seen both styles for a while now. I had previously assumed that people were manually cross-posting and adding a link to the original, but then I just realized that that's probably not the case because those types of cross-post look very consistent.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] [S] 2 points 3 months ago* (last edited 3 months ago) (4 children)

    I can’t reach your example link because lemmy.zip is a tor-hostile node in Cloudflare’s walled-garden. So I am blocked. But what you’re saying suggests you may be experiencing a feature of the server. Sometimes I post a thread that uses the URL field, and the URL I am sharing was already shared by someone else earlier (often unwitting to me). In that case, some clients (or servers) automatically see that multiple threads reference the same URL. In that case, the list of all threads referencing the same URL is presented but it has nothing to do with anything the author posted in the msg body. I wonder if that’s what you are seeing.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 3 months ago (3 children)

    I see. Perhaps it's what you mentioned about Lemmy handling cross-posts of different types of posts a little differently. I seem to recall someone else mentioning that before.

    If you wanted to see the post I'm referring to, here's a link to the native URL of my cross-post: https://lemmy.ca/post/68531648

    If that still doesn't work, you can also search for that lemmy.ca URL above in your own instance (slrpnk.net) and the search should show you the local copy of that post on your instance.

    Thanks!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 3 months ago (2 children)

    Huh, weird. I just happened to run into another post with weird cross-post links. This one happens to have both styles of cross-post links: https://sh.itjust.works/post/64304718

    I have no idea what's going on here. I'll ask this question in the appropriate community for Lemmy questions to see if anyone knows.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 2 points 3 months ago* (last edited 3 months ago) (1 child)

    Notice there is a “crosspost to” and a “crosspost from”. When users of Alexandrite or Lemmy clients initiate a crosspost, a link to the parent post is auto-generated and dumped in the body of the text tagged as “crosspost from”. We can edit that, and sometimes I do. AFAIK, there is no way to form that link to refer to the copy on the reader’s instance. The best we can do on that is to add the !<community>@<node> reference to the community, along with a title to search for.

    The “crosspost to” line is not supplied or controlled by the author. It must be added by the reader’s server. In your case, lemmy.zip editorializes by adding that line when possible. The lemmy.ca and sh.itjust.works examples show that the url points to locally hosted posts. Only lemmy.ca can know about the lemmy.ca link. Lemmy servers are not sophisticated enough to find matching posts based on the body, and the title would not be reliable. So I believe the “crosspost to” line is only generated when a post makes use of the URL field. Since I referenced no URL in my post, there was nothing to compare for generating a “crosspost to” line.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •