# SPAM Published articles for SPAM. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 10+ best practices to improve your email deliverability DevFeed: [10+ best practices to improve your email deliverability]() Original publisher: [Read original article]() Author: Jesse Sumrak Published: 2026-09-09T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [email](), [SendGrid](), [API]() Tags: [best-practices](), [deliverability](), [domain](), [email](), [industry-insights](), [marketing](), [sendgrid](), [spam](), [spoofing](), [subscriber]() ### AI overview This tutorial explains email deliverability and presents more than ten practices for improving inbox placement, including domain authentication, double opt-in, non-spammy subject lines, list cleaning, and avoiding spam traps. It also distinguishes delivery from deliverability and discusses sender reputation and subscriber engagement. ### Source excerpt Email deliverability determines whether your messages reach inboxes or spam folders. Follow these 10+ best practices to improve your deliverability rates. ## My first spam Webmention DevFeed: [My first spam Webmention]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2026-07-07T10:39:00Z Content type: article Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Website](), [Cloudflare Access](), [Cloudflare](), [dashboards](), [SQL](), [ui](), [web design]() Tags: [bluesky](), [cloudflare](), [cloudflare-access](), [code](), [dashboard](), [spam](), [sql](), [ui](), [web-design](), [webmentions]() ### AI overview The author describes receiving a spam Webmention and building a basic moderation dashboard for a Webmentions server. The dashboard lists pages that received Webmentions and provides links to moderation controls, with access protected by Cloudflare Access rather than application-level authentication. ### Source excerpt Finally being forced to build moderation capabilities into my Webmentions server ## A critique of Google search ads and SEO-focused results for remote-work queries DevFeed: [A critique of Google search ads and SEO-focused results for remote-work queries]() Original publisher: [Read original article]() Author: Michael Dubakov Published: 2022-11-25T15:06:35Z Content type: opinion Language: en Sources: [Stories by Michael Dubakov on Medium]() Topics: [Search engine optimization (SEO)](), [Google]() Tags: [ads](), [advertising](), [google](), [marketing](), [rant](), [search-engine](), [seo](), [spam]() ### AI overview The author criticizes Google search results for a remote-work query, describing prominent ads and generic SEO-focused articles that they found lacking in practical information. They report finding more useful resources through Hacker News and express frustration with the search experience. ### Source excerpt I used to love Google. Now I don't. I used to enjoy search for new information and explore some new topic in Google. Now I don't. I'm on the verge of switching to another search engine. Yesterday I dug into remote work. I searched for various info, primarily I wanted to find exact remote companies practices from real practitioners. This is a typical screen in Google for any relatively generic search request. Screen 1. Ads On the first screen I see only ads and some glimpse of hope in the footer. I have to scroll down. Screen 2. SEO-optimized bullshit No hope. All these articles are not good enough. All are generic, and I have a feeling most of them were written by people with zero experience in remote work. I got very little interesting info from them. I have to scroll down. Screen 3. More SEO-optimized crap More SEO-optimized articles, maybe HBR was relatively OK. I have to scroll down. Screen 4. More Ads Final screen has more ads. Is it me? Maybe in some poor country with GDP < 1K per person I will see less ads? Not sure there is VPN for South Sudan... Next page... It appeared to be very hard to find good resources about remote work. Google is filled with generic, non-concrete, SEO-oriented bullshit. I had to dig this piece of crap for an hour to find some rare gems. Most gems I found on HN. My rant is over. Hug me, please. P.S. HN discussion thread ## PSA: Vulnerability Disclosure 2020/09/17 DevFeed: [PSA: Vulnerability Disclosure 2020/09/17]() Original publisher: [Read original article]() Published: 2020-09-17T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [vulnerability](), [WordPress Plugins](), [Exploit](), [Website](), [servers]() Tags: [automated](), [bots](), [exploit](), [plugins](), [spam](), [vulnerability](), [vulnerability-disclosure](), [wordpress-plugins]() ### AI overview PINE64 disclosed an intrusion into its Pine Store web instance on September 17, 2020. Spam and scam pages were hidden on the server and configured to appear only to crawler bots. The company attributed the incident to an exploit in a WordPress plugin, shut down the server, investigated, and reported no evidence that customer or financial information was exposed. ### Source excerpt PINE64 (both the business and the community around it) prides itself on transparency. Often, this transparency is used to give you a behind the scenes look into our operations. But today, we're afraid we must be transparent about something else. As of approximately 4:30am GMT on 2020/09/17, we discovered an intrusion to our Pine Store web instance. This took on the form of spam/scam pages hidden on our web server, with scripting to only be visible to crawler bots. After discovering this, we immediately shutdown the web server and began investigation. To our knowledge, this happened via an exploit in one of the Wordpress plugins on the Pine Store, with initial attempts logged as early as 2020/09/05. It appears this was not an active malicious attack on our server, but merely automated bots tasked with placing scam store pages. Needless to say, we remedied the situation and took extensive steps to prevent similar incidents from occurring in the future. Due to the nature of the attacks we've reviewed, we do not suspect that customer information was a target, nor we expect any was exfiltrated. We can guarantee that, without a doubt, no credit card or other financial information was placed at any risk of being exposed. We hope that this event does not damage your trust in us beyond repair, as we work to recover from this event. -- Lukasz Erecinski, Community Manager ## Why is 'Reply' Not the Strongest Signal? DevFeed: [Why is 'Reply' Not the Strongest Signal?]() Original publisher: [Read original article]() Author: Adam Published: 2017-11-02T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [email]() Tags: [email](), [filter](), [signal](), [spam]() ### AI overview The author says Outlook.com is marking emails from long-term correspondents as junk and questions why spam filters do not treat repeated conversational exchanges as a stronger signal of user engagement. ### Source excerpt [no description provided] ## Commenting powered by Discourse DevFeed: [Commenting powered by Discourse]() Original publisher: [Read original article]() Author: Sam Saffron Published: 2013-12-04T03:12:48Z Content type: opinion Language: en Sources: [Sam Saffron]() Topics: [web applications](), [Software](), [Markdown](), [notifications](), [email](), [Crawler]() Tags: [blog](), [email](), [markdown](), [notifications](), [robots-txt](), [spam]() ### AI overview The author explains why Discourse powers comments on the blog. Although using it adds friction because readers must log in on another site, the author values its support for thoughtful discussions, email follow-up, Markdown editing, moderation, and spam prevention. The author reports receiving no spam over the previous 55 days. ### Source excerpt Leaving comments on this blog requires a certain amount of commitment. You have to jump to another site to log in. ac12507b13e4685b.png765x428 13.4 KB Compare this to the "least amount of friction possible". A lot of work. When I made the move to Discourse I thought of this state-of-affairs as a temporary situation. I would add the "traditional" comment box at the bottom and make it super easy to add comments, I would transparently create accounts and all that jazz. A couple of months in, I am not so sure. When I think about comments on my blog these are my priorities. Give users room to type in interesting and insightful comments. Provide great support for followup (reply by email, email notifications) Rich markdown editor with edit and preview support. Comment format must be markdown, anything else and I am risking complex conversion later on. Zero spam Comments / emails / content are unconditionally hosted on my server and under my control. Not hosted by some third party under their rules with their advertising injected and my readers tracked. Trivial for me to moderate. You may notice that, "Make it super easy for anybody on the Internet to contribute a random unfiltered opinion" is surprisingly missing from this list. What does Discourse score in my 7 point dream list? A solid 7 out of 7. The extra friction completely eradicated spam and enables me to have rich conversations with my readers. I have their emails, I can communicate with them. ###About Spam twitter.com Kelly Sommers @kellabyte Trying out disqus cuz I just got 600 more spam comments on my blog since earlier. Gotta end this madness. 12:19 AM - 1 Dec 2013 1 I eliminated the vast majority of spam on this blog a while back. I blogged about it 2 years ago. Critics claimed that this approach was doomed to fail if it ever got popular. Discourse is popular. Yet I get zero spam. By zero I mean that in the last 55 days I got no spam on this blog, nor did I have to delete any spam from this blog. http://discu ## A spam comment template exposes repetitive promotion tactics DevFeed: [A spam comment template exposes repetitive promotion tactics]() Original publisher: [Read original article]() Author: Tom Published: 2013-09-15T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [Website](), [Web](), [RSS Feed]() Tags: [blog](), [opinion](), [spam]() ### AI overview The author shares a spam comment received on their blog and reproduces its heavily varied template text. They suggest the template could help create banning rules and mock the spammer's repetitive promotional language. ### Source excerpt I've just received a comment on my blog with text attached below. It looks like spam message template. I think it could be easily used for creation of banning rules, etc. Use it in a way that will make this dumbass spammer look even more stupid ;-) { {I have|I've} been {surfing|browsing} online more than {three|3|2|4} hours today, yet I never found any interesting article like yours. {It's|It is} pretty worth enough for me. {In my opinion|Personally|In my view}, if all {webmasters|site owners|website owners|web owners} and bloggers made good content as you did, the {internet|net|web} will be {much more|a lot more} useful than ever before.| I {couldn't|could not} {resist|refrain from} commenting. {Very well|Perfectly|Well|Exceptionally well} written!| {I will|I'll} {right away|immediately} {take hold of|grab|clutch|grasp|seize|snatch} your {rss|rss feed} as I {can not|can't} {in finding|find|to find} your {email|e-mail} subscription {link|hyperlink} or {newsletter|e-newsletter} service. Do {you have|you've} any? {Please|Kindly} {allow|permit|let} me {realize|recognize|understand|recognise|know} {so that|in order that} I {may just|may|could} subscribe. Thanks.| {It is|It's} {appropriate|perfect|the best} time to make some plans for the future and {it is|it's} time to be happy. {I have|I've} read this post and if I could I {want to|wish to|desire to} suggest you {few|some} interesting things or {advice|suggestions|tips}. {Perhaps|Maybe} you {could|can} write next articles referring to this article. I {want to|wish to|desire to} read {more|even more} things about it!| {It is|It's} {appropriate|perfect|the best} time to make {a few|some} plans for {the future|the longer term|the long run} and {it is|it's} time to be happy. {I have|I've} {read|learn} this {post|submit|publish|put up} and if I {may just|may|could} I {want to|wish to|desire to} {suggest|recommend|counsel} you {few|some} {interesting|fascinating|attention-grabbing} {things|issues} or {advice|suggestions|tips ## Jak dokuczać spamerom DevFeed: [Jak dokuczać spamerom]() Original publisher: [Read original article]() Author: Tom Published: 2012-12-18T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [WordPress](), [Crawler](), [Template](), [DDoS]() Tags: [ddos](), [php](), [robots](), [spam](), [wordpress]() ### AI overview The article describes a technique for generating large numbers of fake email addresses on a WordPress page to trap spam crawlers. It recommends excluding the path in robots.txt and discusses precautions to avoid causing mail-related denial-of-service problems for one's own or third-party domains. ### Source excerpt Dawno, dawno temu... Za górami, za lasami... czytałem sobie tekst Lemat'a o dokuczaniu spamerom i pomyślałem że sam też tak mogę i nawet chcę więc popełniłem skrypcik, który dla losowych słów generował maile. Skrypcik działał z dwa lata na mojej poprzedniej stronie i nie raz zdarzyło się tam jakiejś mendzie zapętlić. Jakoś nie miałem czasu od razu, a później zapomniałem wrzucić go na nową stronie i tak zostało - na pewien czas. ## Ochrona usług przed atakami brute force z fail2ban'em DevFeed: [Ochrona usług przed atakami brute force z fail2ban'em]() Original publisher: [Read original article]() Author: Tom Published: 2011-10-03T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Fail2ban](), [Logging](), [ssh]() Tags: [admin](), [apache](), [debian](), [fail2ban](), [linux](), [postfix](), [sasl](), [security](), [spam](), [ssh](), [syslog]() ### AI overview This Polish article explains how Fail2ban can monitor authentication failures in syslog and protect publicly accessible services from brute-force attacks and other abusive activity. It discusses basic configuration, supported services, modular filters and actions, performance considerations, and installation on Debian. ### Source excerpt Bardzo często konfigurując usługi dostępne publicznie poświęca się sporo czasu na maksymalne zwiększenie bezpieczeństwa przez "dopieszczanie" konfiguracji (certyfikaty z mocnym szyfrowaniem, ochronę pewnych stron hasłem, dostęp do SSH tylko kluczami, itd.) ale całkowicie pomija się przygotowanie systemu aktywnie monitorującego błędne próby autoryzacji. Oczywiście nie można umniejszać wagi pierwszego z wymienionych etapów ale zdecydowanie nie powinno pomijać się też tego drugiego. Przecież każdy admin chciałby wiedzieć gdy ktoś próbuje włamać się na jego serwer (FTP, HTTP, SSH, itp.) - tylko ilu z Nas zadaje sobie trud by uruchomić taki system? ## The Cuckoo's Egg DevFeed: [The Cuckoo's Egg]() Original publisher: [Read original article]() Author: Tom Published: 2000-02-09T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [IT\_Security](), [Unix](), [Security](), [Networks](), [Internet]() Tags: [hacking](), [internet](), [it-security](), [networks](), [security](), [server](), [services](), [spam](), [systems](), [technology](), [terminal](), [unix]() ### AI overview A personal review of Clifford Stoll's The Cuckoo's Egg, describing its portrayal of a system administrator tracking a hacker and its depiction of early Unix, networked computing, and IT security. The author says the book influenced their interest in Unix systems and security. ### Source excerpt Kukułcze jajo Ekscytujące łowy na nieuchwytnego hackera Author: Clifford Stoll I've read it in Polish, so I kept polish picture. This book had a huge impact on how I perceive IT security. It was the way that shaped my fascination by Unix systems and probably impacted some of my decisions about my future 😉 It's a fascinating lecture on the battle between "sys admin" (actually an astronomer external link and kinda random guy, but with a skill) and a hacker. Cold war times. Quite "analog" IT systems, printers as terminals, etc. A time machine to the beginnings of networks and Internet. It was at a time when there was no encryption on services. Computers were powerful machines taking whole rooms and you could work with them only via terminal. A different world, but that's how it all started.