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
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
How is the instance of that community located on web.archive.org?
Anyway, the answer the OOP was looking for is sugar.
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 (saylemmy.nz) on the original page butweb.archive.orgon the snapshot.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.