Coming from Lemmy I remember there was a relatively simple way to view moderation actions, incl. possible comments a mod might have left.

Is it possible to view such things - and all things moderation - on piefed, too?

And, going beyond piefed_help, what is the canonical way of reaching out to mods resp. reacting to an action taken against me?

Can instance bans be queried in a similar way?

I see him me every day on my way to work. And he sees me. Standing by the side of the road, watching. He's not trying to be inconspicuous but he's a Mr Smith.

This has aged well. Replace "Reagan" with...

They tell us a story of lying
Of lying & of murder too
To whom is this tale mystifying
Not'me boys perhaps 'tis to you

They're telling us a story of Reagan, boys
Our President so bold & so true
How can he be a false killer--
When he's wrapped in the red, white & blue?

Rapped in the red, white & blue, boys
Rapt in the red, white & blue
A man of the movies, a starlet
He's just an asshole like you

Yes, he's just an asshole likе you boys
Yes, he's just an asshole likе you
You 'lected him in 1980
And dunce more in '84 too

O my, O my he's a liar
As if you didn' even know
He's killed many people off welfare
Nicaragua, Grenada, much mo'

He smiles when he gives you the shaft, lad
He smiles when he gives ya the shaft (ha-ha)
If you think he cares about poor folks
Well then I surmise that you're daft

He always finds money for war, girls
He always finds money for death
He'll fight for the rights of the rich, boys
He'll fight for them 'til your last breath

So here's to President Reagan, boys
To Ollie, to Dick & to Cap
To some they're All American Heroes
To me they're just murderous crap

So here's to Dumbo Ron Reagan, boys
To Ollie, to Fawn & to Cap
To some they're All American Heroes
To us they're American crap

This has aged well. Replace "Reagan" with...

They tell us a story of lying
Of lying & of murder too
To whom is this tale mystifying
Not'me boys perhaps 'tis to you

They're telling us a story of Reagan, boys
Our President so bold & so true
How can he be a false killer--
When he's wrapped in the red, white & blue?

Rapped in the red, white & blue, boys
Rapt in the red, white & blue
A man of the movies, a starlet
He's just an asshole like you

Yes, he's just an asshole likе you boys
Yes, he's just an asshole likе you
You 'lected him in 1980
And dunce more in '84 too

O my, O my he's a liar
As if you didn' even know
He's killed many people off welfare
Nicaragua, Grenada, much mo'

He smiles when he gives you the shaft, lad
He smiles when he gives ya the shaft (ha-ha)
If you think he cares about poor folks
Well then I surmise that you're daft

He always finds money for war, girls
He always finds money for death
He'll fight for the rights of the rich, boys
He'll fight for them 'til your last breath

So here's to President Reagan, boys
To Ollie, to Dick & to Cap
To some they're All American Heroes
To me they're just murderous crap

So here's to Dumbo Ron Reagan, boys
To Ollie, to Fawn & to Cap
To some they're All American Heroes
To us they're American crap

Our band was going to do a concert. Decent punk. It was in my first love's mom's appartment, so not much space. I lived just down the hall, but somebody told me to not bring my bass amp because they already have one. I decided to bring a distortion pedal which I hadn't ever used with a bass. Feeling frisky.

Arriving, there was no bass amp. Instead I was allowed to plug the bass into the washing machine, which had minor amplifying capabilities. the sound was laughably low and tinny. I said "really, my totally adequate bass amp is just down the hall", but the mom did not budge. Not enough space. Already cramped, she said.

Some dude showed up and attached a small monitor speaker to the washing machine which maxed out at a volume that was still way too low.

This was not going to be a good gig for me.

After that the dream went meandering into what could've been touring with the band...

US-Vizepräsident Vance: Keine Einigung mit Iran erzielt

Bei den Verhandlungen zwischen den USA und Iran unter Vermittlung Pakistans ist nach den Worten von US-Vizepräsident JD Vance keine Einigung erzielt worden. Irans Regierung bestätigt das Ende der Gespräche.

Wenn das kein Tja ist...

This time of the year, when all the snow is gone but just before the fresh green comes out, lichen & moss become extremely visible to my eye.

Southern Finland.

Around January 11, 2026, archive.today (aka archive.is, archive.md, etc) started using its users as proxies to conduct a distributed denial of service (DDOS) attack against Gyrovague, my personal blog. All users encountering archive.today's CAPTCHA page currently load and execute the following Javascript: setInterval(function() { fetch("https://gyrovague.com/?s" + Math.random().toString(36).substring(2, 3 + Math.random() * 8), { referrerPolicy: "no-referrer",…

Far too many netizens still try to ignore this or even come up with reasons why gyrovague is the bad guy here.

Alternative archive pages:

archive.org
ghostarchive.org
archivebox.io (self-hosted)

But how else to bypass a paywall?

I've read relevant articles and clicked old links - they all seem to be history. The only ones that still work just look for the article in various archives - the subject of this post always amongst them. The same applies to this article, but there's still some good tips.

Here is the original article from 2023: https://gyrovague.com/2023/08/05/archive-today-on-the-trail-of-the-mysterious-guerrilla-archivist-of-the-internet/ and what Patakallio has to say about it today:

The post mentions three names/aliases linked to the site, but all of them had been dug up by previous sleuths and the blog post also concludes that they are all most likely aliases, so as far as “doxxing” goes, this wasn’t terribly effective.

Here is a relevant ArsTechnica article: https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-archive-today-after-site-executed-ddos-and-altered-web-captures/

Wikipedia editors discovered that the archive site altered snapshots of webpages to insert the name of the blogger who was targeted by the DDoS.

archive.today (.ph, .is, .md, .fo, .li, .vn) also loads a pixel and javascript from mail.ru. The script mentions lamoda.ru, kommersant.ru, dzen.ru, ad.mail.ru, vk.com, vkontakte.ru, ok.ru, odnoklasseniki.ru. I haven't researched this further, but I think one can assume that your IP address will be spread across all relevant Russian websites. 10 years ago I would have said "so what? The Russians have social media too" but today you can safely assume that all this data is available to the government itself and is actively contributing to the hybrid war.

All in all, archive.today has always been in the "too good to be true" category. Call me suspicious.

And once again because it's important:

The Wikipedia guidance points out that the Internet Archive and its website, Archive.org, are “uninvolved with and entirely separate from archive.today.”

Around January 11, 2026, archive.today (aka archive.is, archive.md, etc) started using its users as proxies to conduct a distributed denial of service (DDOS) attack against Gyrovague, my personal blog. All users encountering archive.today's CAPTCHA page currently load and execute the following Javascript: setInterval(function() { fetch("https://gyrovague.com/?s" + Math.random().toString(36).substring(2, 3 + Math.random() * 8), { referrerPolicy: "no-referrer",…

Viel zu viele Internetbürger versuchen das nach wie vor zu ignorieren oder denken sich sogar Gründe aus warum gyrovague hier der Böse ist.

Alternative Archivseiten:

archive.org
ghostarchive.org
archivebox.io (selfhosted)

Paywall umgehen:

Ich habe einschlägige Artikel gelesen und alte Links geklickt - die scheinen Geschichte zu sein. Die einzigen die überhaupt noch funktionieren suchen den Artikel lediglich in versch. Archiven - den Gegenstand dieses Artikels immer mit dabei. Das gleiche gilt für diesen Artikel der trotzdem gute Tipps nennt!

Hier der Originale Artikel von 2023: https://gyrovague.com/2023/08/05/archive-today-on-the-trail-of-the-mysterious-guerrilla-archivist-of-the-internet/ und was Patakallio heute dazu zu sagen hat:

The post mentions three names/aliases linked to the site, but all of them had been dug up by previous sleuths and the blog post also concludes that they are all most likely aliases, so as far as “doxxing” goes, this wasn’t terribly effective.

Hier ein relevanter ArsTechnica-Artikel: https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-archive-today-after-site-executed-ddos-and-altered-web-captures/

Wikipedia editors discovered that the archive site altered snapshots of webpages to insert the name of the blogger who was targeted by the DDoS.

Dann möchte ich noch hinzufügen dass archive.today (.ph, .is, .md, .fo, .li, .vn) schon immer (?) ein Pixel und auch javascript von mail.ru lädt. Das Skript benennt lamoda.ru, kommersant.ru, dzen.ru, ad.mail.ru, vk.com, vkontakte.ru, ok.ru, odnoklassniki.ru. Ich hab das nicht weiter erforscht, aber ich denke es ist realistisch dass dein IP-Addresse über alle einschlägigen russischen Webseiten verteilt wird. Vor 10 Jahren hätte ich gesagt "na und? Die Russen haben halt auch soziale Medien" aber heutzutage kann man getrost davon ausgehen dass all diese Daten der regierung selbst zur Verfügung stehen und aktiv zum hybriden Krieg beitragen.

Vielleicht bin ich misstrauisch, aber archive.today gehört für mich schon lange in die zu-gut-um-wahr-zu-sein-Kategorie.

Und noch einmal weil's wichtig ist:

The Wikipedia guidance points out that the Internet Archive and its website, Archive.org, are “uninvolved with and entirely separate from archive.today.”

Disclaimer: This is not technically a privacy matter for the reader, but I believe it is adjacent and important enough for this community.

Around January 11, 2026, archive.today (aka archive.is, archive.md, etc) started using its users as proxies to conduct a distributed denial of service (DDOS) attack against Gyrovague, my personal blog. All users encountering archive.today's CAPTCHA page currently load and execute the following Javascript: setInterval(function() { fetch("https://gyrovague.com/?s" + Math.random().toString(36).substring(2, 3 + Math.random() * 8), { referrerPolicy: "no-referrer",…

Far too many netizens still try to ignore this or even come up with reasons why gyrovague is the bad guy here.

Alternative archive pages:

archive.org
ghostarchive.org
archivebox.io (self-hosted)

But how else to bypass a paywall?

I've read relevant articles and clicked old links - they all seem to be history. The only ones that still work just look for the article in various archives - the subject of this post always amongst them. The same applies to this article, but there's still some good tips.

Here is the original article from 2023: https://gyrovague.com/2023/08/05/archive-today-on-the-trail-of-the-mysterious-guerrilla-archivist-of-the-internet/ and what Patakallio has to say about it today:

The post mentions three names/aliases linked to the site, but all of them had been dug up by previous sleuths and the blog post also concludes that they are all most likely aliases, so as far as “doxxing” goes, this wasn’t terribly effective.

Here is a relevant ArsTechnica article: https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-archive-today-after-site-executed-ddos-and-altered-web-captures/

Wikipedia editors discovered that the archive site altered snapshots of webpages to insert the name of the blogger who was targeted by the DDoS.

archive.today (.ph, .is, .md, .fo, .li, .vn) also loads a pixel and javascript from mail.ru. The script mentions lamoda.ru, kommersant.ru, dzen.ru, ad.mail.ru, vk.com, vkontakte.ru, ok.ru, odnoklasseniki.ru. I haven't researched this further, but I think one can assume that your IP address will be spread across all relevant Russian websites. 10 years ago I would have said "so what? The Russians have social media too" but today you can safely assume that all this data is available to the government itself and is actively contributing to the hybrid war.

All in all, archive.today has always been in the "too good to be true" category. Call me suspicious.

And once again because it's important:

The Wikipedia guidance points out that the Internet Archive and its website, Archive.org, are “uninvolved with and entirely separate from archive.today.”

Disclaimer: This is not technically a privacy matter for the reader, but I believe it is adjacent and important enough for this community.

Around January 11, 2026, archive.today (aka archive.is, archive.md, etc) started using its users as proxies to conduct a distributed denial of service (DDOS) attack against Gyrovague, my personal blog. All users encountering archive.today's CAPTCHA page currently load and execute the following Javascript: setInterval(function() { fetch("https://gyrovague.com/?s" + Math.random().toString(36).substring(2, 3 + Math.random() * 8), { referrerPolicy: "no-referrer",…

Far too many netizens still try to ignore this or even come up with reasons why gyrovague is the bad guy here.

Alternative archive pages:

archive.org
ghostarchive.org
archivebox.io (self-hosted)

But how else to bypass a paywall?

I've read relevant articles and clicked old links - they all seem to be history. The only ones that still work just look for the article in various archives - the subject of this post always amongst them. The same applies to this article, but there's still some good tips.

Here is the original article from 2023: https://gyrovague.com/2023/08/05/archive-today-on-the-trail-of-the-mysterious-guerrilla-archivist-of-the-internet/ and what Patakallio has to say about it today:

The post mentions three names/aliases linked to the site, but all of them had been dug up by previous sleuths and the blog post also concludes that they are all most likely aliases, so as far as “doxxing” goes, this wasn’t terribly effective.

Here is a relevant ArsTechnica article: https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-archive-today-after-site-executed-ddos-and-altered-web-captures/

Wikipedia editors discovered that the archive site altered snapshots of webpages to insert the name of the blogger who was targeted by the DDoS.

archive.today (.ph, .is, .md, .fo, .li, .vn) also loads a pixel and javascript from mail.ru. The script mentions lamoda.ru, kommersant.ru, dzen.ru, ad.mail.ru, vk.com, vkontakte.ru, ok.ru, odnoklasseniki.ru. I haven't researched this further, but I think one can assume that your IP address will be spread across all relevant Russian websites. 10 years ago I would have said "so what? The Russians have social media too" but today you can safely assume that all this data is available to the government itself and is actively contributing to the hybrid war.

All in all, archive.today has always been in the "too good to be true" category. Call me suspicious.

And once again because it's important:

The Wikipedia guidance points out that the Internet Archive and its website, Archive.org, are “uninvolved with and entirely separate from archive.today.”

Disclaimer: This is not technically a privacy matter for the reader, but I believe it is adjacent and important enough for this community.

Around January 11, 2026, archive.today (aka archive.is, archive.md, etc) started using its users as proxies to conduct a distributed denial of service (DDOS) attack against Gyrovague, my personal blog. All users encountering archive.today's CAPTCHA page currently load and execute the following Javascript: setInterval(function() { fetch("https://gyrovague.com/?s" + Math.random().toString(36).substring(2, 3 + Math.random() * 8), { referrerPolicy: "no-referrer",…

Far too many netizens still try to ignore this or even come up with reasons why gyrovague is the bad guy here.

Alternative archive pages:

archive.org
ghostarchive.org
archivebox.io (self-hosted)

But how else to bypass a paywall?

I've read relevant articles and clicked old links - they all seem to be history. The only ones that still work just look for the article in various archives - the subject of this post always amongst them. The same applies to this article, but there's still some good tips.

Here is the original article from 2023: https://gyrovague.com/2023/08/05/archive-today-on-the-trail-of-the-mysterious-guerrilla-archivist-of-the-internet/ and what Patakallio has to say about it today:

The post mentions three names/aliases linked to the site, but all of them had been dug up by previous sleuths and the blog post also concludes that they are all most likely aliases, so as far as “doxxing” goes, this wasn’t terribly effective.

Here is a relevant ArsTechnica article: https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-archive-today-after-site-executed-ddos-and-altered-web-captures/

Wikipedia editors discovered that the archive site altered snapshots of webpages to insert the name of the blogger who was targeted by the DDoS.

archive.today (.ph, .is, .md, .fo, .li, .vn) also loads a pixel and javascript from mail.ru. The script mentions lamoda.ru, kommersant.ru, dzen.ru, ad.mail.ru, vk.com, vkontakte.ru, ok.ru, odnoklasseniki.ru. I haven't researched this further, but I think one can assume that your IP address will be spread across all relevant Russian websites. 10 years ago I would have said "so what? The Russians have social media too" but today you can safely assume that all this data is available to the government itself and is actively contributing to the hybrid war.

All in all, archive.today has always been in the "too good to be true" category. Call me suspicious.

And once again because it's important:

The Wikipedia guidance points out that the Internet Archive and its website, Archive.org, are “uninvolved with and entirely separate from archive.today.”

Disclaimer: This is not technically a privacy matter for the reader, but I believe it is adjacent and important enough for this community.

Around January 11, 2026, archive.today (aka archive.is, archive.md, etc) started using its users as proxies to conduct a distributed denial of service (DDOS) attack against Gyrovague, my personal blog. All users encountering archive.today's CAPTCHA page currently load and execute the following Javascript: setInterval(function() { fetch("https://gyrovague.com/?s" + Math.random().toString(36).substring(2, 3 + Math.random() * 8), { referrerPolicy: "no-referrer",…

Far too many netizens still try to ignore this or even come up with reasons why gyrovague is the bad guy here.

Alternative archive pages:

archive.org
ghostarchive.org
archivebox.io (self-hosted)

But how else to bypass a paywall?

I've read relevant articles and clicked old links - they all seem to be history. The only ones that still work just look for the article in various archives - the subject of this post always amongst them. The same applies to this article, but there's still some good tips.

Here is the original article from 2023: https://gyrovague.com/2023/08/05/archive-today-on-the-trail-of-the-mysterious-guerrilla-archivist-of-the-internet/ and what Patakallio has to say about it today:

The post mentions three names/aliases linked to the site, but all of them had been dug up by previous sleuths and the blog post also concludes that they are all most likely aliases, so as far as “doxxing” goes, this wasn’t terribly effective.

Here is a relevant ArsTechnica article: https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-archive-today-after-site-executed-ddos-and-altered-web-captures/

Wikipedia editors discovered that the archive site altered snapshots of webpages to insert the name of the blogger who was targeted by the DDoS.

archive.today (.ph, .is, .md, .fo, .li, .vn) also loads a pixel and javascript from mail.ru. The script mentions lamoda.ru, kommersant.ru, dzen.ru, ad.mail.ru, vk.com, vkontakte.ru, ok.ru, odnoklasseniki.ru. I haven't researched this further, but I think one can assume that your IP address will be spread across all relevant Russian websites. 10 years ago I would have said "so what? The Russians have social media too" but today you can safely assume that all this data is available to the government itself and is actively contributing to the hybrid war.

All in all, archive.today has always been in the "too good to be true" category. Call me suspicious.

And once again because it's important:

The Wikipedia guidance points out that the Internet Archive and its website, Archive.org, are “uninvolved with and entirely separate from archive.today.”

Around January 11, 2026, archive.today (aka archive.is, archive.md, etc) started using its users as proxies to conduct a distributed denial of service (DDOS) attack against Gyrovague, my personal blog. All users encountering archive.today's CAPTCHA page currently load and execute the following Javascript: setInterval(function() { fetch("https://gyrovague.com/?s" + Math.random().toString(36).substring(2, 3 + Math.random() * 8), { referrerPolicy: "no-referrer",…

Viel zu viele Internetbürger versuchen das nach wie vor zu ignorieren oder denken sich sogar Gründe aus warum gyrovague hier der Böse ist.

Alternative Archivseiten:

archive.org
ghostarchive.org
archivebox.io (selfhosted)

Paywall umgehen:

Ich habe einschlägige Artikel gelesen und alte Links geklickt - die scheinen Geschichte zu sein. Die einzigen die überhaupt noch funktionieren suchen den Artikel lediglich in versch. Archiven - den Gegenstand dieses Artikels immer mit dabei. Das gleiche gilt für diesen Artikel der trotzdem gute Tipps nennt!

Hier der Originale Artikel von 2023: https://gyrovague.com/2023/08/05/archive-today-on-the-trail-of-the-mysterious-guerrilla-archivist-of-the-internet/ und was Patakallio heute dazu zu sagen hat:

The post mentions three names/aliases linked to the site, but all of them had been dug up by previous sleuths and the blog post also concludes that they are all most likely aliases, so as far as “doxxing” goes, this wasn’t terribly effective.

Hier ein relevanter ArsTechnica-Artikel: https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-archive-today-after-site-executed-ddos-and-altered-web-captures/

Wikipedia editors discovered that the archive site altered snapshots of webpages to insert the name of the blogger who was targeted by the DDoS.

Dann möchte ich noch hinzufügen dass archive.today (.ph, .is, .md, .fo, .li, .vn) schon immer (?) ein Pixel und auch javascript von mail.ru lädt. Das Skript benennt lamoda.ru, kommersant.ru, dzen.ru, ad.mail.ru, vk.com, vkontakte.ru, ok.ru, odnoklassniki.ru. Ich hab das nicht weiter erforscht, aber ich denke es ist realistisch dass dein IP-Addresse über alle einschlägigen russischen Webseiten verteilt wird. Vor 10 Jahren hätte ich gesagt "na und? Die Russen haben halt auch soziale Medien" aber heutzutage kann man getrost davon ausgehen dass all diese Daten der regierung selbst zur Verfügung stehen und aktiv zum hybriden Krieg beitragen.

Und noch einmal weil's wichtig ist:

The Wikipedia guidance points out that the Internet Archive and its website, Archive.org, are “uninvolved with and entirely separate from archive.today.”

Usually refering to works of fiction, movies, TV etc.

But I think it's a much larger phenomenon. It has esaped fiction, entered real life and politics. It drives a lot of people these days to stick with bad narratives instead of facts and, yes, truth.

Meaning: they're willing to swallow tons of contradictions, plot holes etc. because they want to be convinced by what they're seeing or being told. That enables certain public people to tell them very flimsy stories.

This is not purely about people choosing bad input because it suits them. It's not only about being lied to and believing those lies. It's about being lied to badly and still not letting go of the narrative. Wanting to take it for real so badly.

edit: I'm beginning to realize that people who don't know or haven't known suspension of disbelief will try to explain it with something similar that they're more familiar with.
And it is very similar to things we see happening in so-called political discourse these days, esp. in the USA.
But many have known this since before Trump1.0, see e.g. TVTropes and Wikipedia.

I tested on two browsers, the latter without any “protection” or addons, and I tried the same post on a Lemmy instance, where it’s fine. It’s clearly not happening on my side, and OP didn’t do anything wrong either.

Here’s the short dialog we just had.