I love spam. casly1981@gustr.com

As a postmaster, Gmail remains the most irritating domain to send to. Soooo many false spam hits, such little information provided, so many hoops to jump through.

@lyse@lyse.isobeef.org Me when I find myself crossing an international border, close to midnight, using free bus WiFi, spammed by messages from people, telling me that the server hosting my web-apps is down. 😂
*Only happened once so far

@movq@www.uninformativ.de LOL. As someone with OCD, I can relate completely. When I set to do “slight” modifications to a stylesheet, boy… often a start over is best, to eliminate commit spam.

Based on spam logs, I am (again) considering banning a bunch of TLDs at the server level. Has anyone ever gotten legitimate email from a .work, .casa, or .today domain, for example?

It did! And I fixed the bug last night. And now I’m curious how your pod deals with spam. 👆🏼

fighting spam and illegal/unethical content is much easier if you have explicit control over who you accept messages from.

the spam problem can’t be solved efficiently by maintaining extensive deny lists. the only scalable way to handle spam is with allow lists and trust networks.

I wonder if email would be a reasonable way to enable interaction on twtxt… something like publishing an email address for replies in the preamble of your feed, then like twtxt the rest is up to you, but I could imagine a simple moderation queue that could be checked periodically allowing the admin to move approved comments into some public space… I keep thinking I’ll add activitypub comments to my site but it seems more complex than I care for. Ironically because of available tooling email actually feels simpler for this… of course, there is spam…

@prologic@twtxt.net lol.. sorry about the spam

Съчетаване на полезното с приятното: счетоводство style #spam http://t.co/CIFjgA4n