# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 7
# self = https://watcher.sour.is/conv/j75ihta
prologic
twtxt.net
View Thread
How fucking dumb as these spammer little assholes?! 🤦‍♂️ Not only does the domain in the Fron: have a bad TLS certificate, the domain in the Reply-To is a blank page. Wut dua fuw?! 🤣 And seriously, how du fuq did this even get through my Mail proxies? 🤔 @xuu 😅
prologic
twtxt.net
View Thread
How fucking dumb as these spammer little assholes?! 🤦‍♂️ Not only does the domain in the Fron: have a bad TLS certificate, the domain in the Reply-To is a blank page. Wut dua fuw?! 🤣 And seriously, how du fuq did this even get through my Mail proxies? 🤔 @xuu 😅
prologic
twtxt.net
View Thread
Check this out 😅😅


Authentication-Results: mail.mills.io;
\tspf=temperror (mail.mills.io: error in processing during lookup of msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com: responses is not iterable) smtp.mailfrom="msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com" smtp.helo=us.proxy.mills.io;
\tdkim=neutral (invalid public key) header.i=@irp.stuartkenzie.com header.s=scph1124 header.a=rsa-sha256 header.b=BOHvtOsv;
\tdmarc=none header.from=stuartkenzie.com
Received-SPF: temperror (mail.mills.io: error in processing during lookup of msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com: responses is not
 iterable) client-ip=172.30.0.5;
Received: from us.proxy.mills.io ([172.30.0.5])
\tby mail.mills.io (Haraka) with ESMTP id 3CD19639-8117-48DB-8137-5B29E3732B5E.1
\tenvelope-from <msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com>;
\tSun, 26 Jan 2025 22:23:33 +0000
Received: from mta-174-87-76.smtp-out.sparkpostmail.com
 (mta-174-87-76.smtp-out.sparkpostmail.com [192.174.87.76]) by
 us.proxy.mills.io (envelope-sender
 <msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com>) with ESMTPS id
 74a301f9; Sun, 26 Jan 2025 22:23:33 +0000
prologic
twtxt.net
View Thread
Check this out 😅😅


Authentication-Results: mail.mills.io;
	spf=temperror (mail.mills.io: error in processing during lookup of msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com: responses is not iterable) smtp.mailfrom="msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com" smtp.helo=us.proxy.mills.io;
	dkim=neutral (invalid public key) header.i=@irp.stuartkenzie.com header.s=scph1124 header.a=rsa-sha256 header.b=BOHvtOsv;
	dmarc=none header.from=stuartkenzie.com
Received-SPF: temperror (mail.mills.io: error in processing during lookup of msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com: responses is not
 iterable) client-ip=172.30.0.5;
Received: from us.proxy.mills.io ([172.30.0.5])
	by mail.mills.io (Haraka) with ESMTP id 3CD19639-8117-48DB-8137-5B29E3732B5E.1
	envelope-from <msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com>;
	Sun, 26 Jan 2025 22:23:33 +0000
Received: from mta-174-87-76.smtp-out.sparkpostmail.com
 (mta-174-87-76.smtp-out.sparkpostmail.com [192.174.87.76]) by
 us.proxy.mills.io (envelope-sender
 <msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com>) with ESMTPS id
 74a301f9; Sun, 26 Jan 2025 22:23:33 +0000
prologic
twtxt.net
View Thread
Check this out 😅😅


Authentication-Results: mail.mills.io;
	spf=temperror (mail.mills.io: error in processing during lookup of msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com: responses is not iterable) smtp.mailfrom="msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com" smtp.helo=us.proxy.mills.io;
	dkim=neutral (invalid public key) header.i=@irp.stuartkenzie.com header.s=scph1124 header.a=rsa-sha256 header.b=BOHvtOsv;
	dmarc=none header.from=stuartkenzie.com
Received-SPF: temperror (mail.mills.io: error in processing during lookup of msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com: responses is not
 iterable) client-ip=172.30.0.5;
Received: from us.proxy.mills.io ([172.30.0.5])
	by mail.mills.io (Haraka) with ESMTP id 3CD19639-8117-48DB-8137-5B29E3732B5E.1
	envelope-from <msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com>;
	Sun, 26 Jan 2025 22:23:33 +0000
Received: from mta-174-87-76.smtp-out.sparkpostmail.com
 (mta-174-87-76.smtp-out.sparkpostmail.com [192.174.87.76]) by
 us.proxy.mills.io (envelope-sender
 <msprvs1=20121HZ44a1Eg=bounces-367050@irp.stuartkenzie.com>) with ESMTPS id
 74a301f9; Sun, 26 Jan 2025 22:23:33 +0000
prologic
twtxt.net
View Thread
@xuu I _think_ it's about time we start blocking invalid SPF and DMARC 🤣
prologic
twtxt.net
View Thread
@xuu I _think_ it's about time we start blocking invalid SPF and DMARC 🤣