lemm.ee has shut down at 00:14 UTC.

unfortunately I realized too late that I have had hundreds of saved links to posts and comments from there, so I did not have enough time to save them, but anyways it is interesting that maybe a third of the post links I could try were dead. I think linkrot is happening much faster here than on reddit, even if just counting deleted posts.

  • WhyJiffie@sh.itjust.worksOPEnglish
    5·
    13 hours ago

    speaking of that, there was a userscript that is able to find the same post on other instances. I should look it up, in case it can also work with posts of offline instances

      • ramble81@lemmy.zip
        1·
        8 hours ago

        Awesome. Zip managed to cache my ee account so I can at least refer back to any place I posted or commented off of ee. Wonder how long it’ll keep it for

      • WhyJiffie@sh.itjust.worksOPEnglish
        3·
        12 hours ago

        hmm that’s interesting because I did not have a lemm.ee account! :D just 3 tons of links to it.

        edit: I misunderstood it, no I didn’t have an account there

        also in the meantime I did some research. it turns out I was probably remembering the Lemmy Universal Link Switcher userscript: https://greasyfork.org/en/scripts/469273-lemmy-universal-link-switcher

        it can look up posts by their activitypub id, which is the de-facto ID of a post, that is same across all instances. this ID is the url of the content on the original instance. so, the following could be an activitypub id, if the post was actually created on lemm.ee: https://lemm.ee/post/64477597

        to look up a post by this, the userscript uses the /api/v3/resolve_object API endpoint.
        it searches your local instance, and if you are authenticated it also queries the host in the url, lemm.ee in this example. but of course this remote query does not work anymore.

        now here comes the twist. I know I always read lemmy through sh.itjust.works, so whatever I saved should be known by this server. and the link that I save, often does not point to the origin instance, because clients work that way.
        so it seems 2 lemm.ee links that I tried to look up were not actually posted there, because bmy server does not know a post that has this ap id, I just somehow got a link that points to the lemm.ee version of that post or comment…

        Fortunately the messaging app I misuse for link collection always loads the title and image of the webpage, so by some manual work I should be able to find the actual links to each of them.

        • davel [he/him]@lemmy.mlEnglish
          2·
          6 hours ago
          $ curl -sw'\n' \
     https://lemmy.ml/api/v3/resolve_object?q=https%3A%2F%2Fsh.itjust.works%2Fcomment%2F19488525 \
     | jq -r '.comment.comment.content' | head -n 1
~~hmm that's interesting because I did not have a lemm.ee account! :D~~ just 3 tons of links to it.
$

          Edit to add: Lemmy seems to URL-encode ‘:’ and ‘/’ sometimes :/