this post was submitted on 29 Mar 2026
516 points (99.2% liked)

Lemmy Shitpost

38907 readers
4152 users here now

Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.

Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means:

-No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...

If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.


Also check out:

Partnered Communities:

1.Memes

2.Lemmy Review

3.Mildly Infuriating

4.Lemmy Be Wholesome

5.No Stupid Questions

6.You Should Know

7.Comedy Heaven

8.Credible Defense

9.Ten Forward

10.LinuxMemes (Linux themed memes)


Reach out to

All communities included on the sidebar are to be made in compliance with the instance rules. Striker

founded 2 years ago
MODERATORS
 

The post got deleted later on, and sadly the Wayback machine was unable to capture all the comments:

https://web.archive.org/web/20230629152756/https://lemmy.world/post/440073

you are viewing a single comment's thread
view the rest of the comments
[–] kif@lemmy.nz 6 points 8 hours ago (2 children)

Not certain, but I'm guessing it's something to do with how archive.org archives. I'd say it probably captured some JavaScript which uses window.location.host, which would resolve to the original (say lemmy.nz) on the original page but web.archive.org on the snapshot.

[–] SlurpingPus@lemmy.world 1 points 13 minutes ago* (last edited 12 minutes ago)

You seem to be at least partially correct about JS being involved: the webpage source as downloaded from archive.org has a shitton of data in JS structures, while the actual final HTML of that element is nowhere to be found. Meaning the DOM is assembled from the JS data on the fly. Now, the page url, as I predicted, doesn't seem to figure in this, because the data itself contains numerous instances of 'web.archive.org' in it. I'm guessing that Archive's algorithm replaced the site domain to be prefixed with Archive's domain and went a bit overboard about it, which seems then to have confused Lemmy's JS into using the web.archive.org domain as the instance domain when rendering the page.

For better or worse, I don't use stimulants harder than tea, and amn't so young anymore as to reverse-engineer it further.

[–] SlurpingPus@lemmy.world 1 points 5 hours ago

That's very doubtful, seeing as since the post might belong to any of the multitude of instances, the api must send the instance name in the response to the client. The client's host doesn't figure in that. Additionally, the screenshot looks like the default UI, whatever it's called (at least default for lemmy.world), and it doesn't show the instance domain for communities on the same instance (at least doesn't show currently).

But I'll look into the JS hypothesis later. Weird shit is afoot there.