bleeptrackWe should stick stamps on emails just because it's cute.
Do we need more stamps when the attachments are larger? And/or is it more about the distance (hops) of travel?
The stamps on a received mail should get semi-transparant post marks for each hop from the respective server. Could be generated from the mail header info.
Can't wait for bouncing mails because there weren't enough stamps on it :D
But serious question: where would I "inject" my stamp generation on the mail process? Would need to be a client plugin or something like that, I guess?
🌈☔🌦️🍄🌱🍉@bleeptrack client seems like a good place, maybe mailservers can be allowed to add to the stamp. Would this be a generative thing based on string(s) in the header? That would be cool, like the 'received' header, it can be multiple and each adds to it. Hmm, could also use the 'received' header as a stamp modifier.
sending client inserts initial stamp string, receiving client generates stamp based on initial stamp string + all 'received' headers.
@bleeptrack Maybe each 'received' header adds a unique 'stain' or 'stamp' (as in like the ink stamp that goes on top of the paper stamp).
@wmd yeah I'd love that! 🤩 https://vis.social/@bleeptrack/116232498266479572
bleeptrack (@[email protected])
The stamps on a received mail should get semi-transparant post marks for each hop from the respective server. Could be generated from the mail header info.