spam

<p>PSA for people with <a href="/tags/wordpress/" rel="tag">#Wordpress</a> blogs: do you know that you can turn off comments on old posts?<br><br>In the last few months I have noticed a significant uptick in spammy comments on my Wordpress blogs (I have 4).<br><br>Well there is a way to remedy all that: you can simply turn off comments on old blog posts by going to:<br><br>Settings -&gt; Discussion -&gt; and checking &quot;Automatically close comments on old posts&quot;<br><br>(You can even determine the &quot;oldness&quot; of posts, for example, older than 7 days, 14 days... anything you&#x27;d like)<br><br>Enabling this made all the difference for me. I could not recommend it more.<br><br>End of my PSA 🤗<br><br>Have a great day everyone!<br><br><a href="/tags/blog/" rel="tag">#blog</a> <a href="/tags/blogging/" rel="tag">#blogging</a> <a href="/tags/selfhosting/" rel="tag">#selfhosting</a> <a href="/tags/spam/" rel="tag">#spam</a><br></p>

<p><a href="/tags/psa/" rel="tag">#PSA</a> <br><a href="/tags/mastodon/" rel="tag">#Mastodon</a>, nor the <a href="/tags/fediverse/" rel="tag">#Fediverse</a> in general will never ask you to &quot;verify&quot; with payment details, especially not from a non-moderator account. If you get a message asking you to verify, it is a <a href="/tags/scam/" rel="tag">#Scam</a> <a href="/tags/bot/" rel="tag">#Bot</a>, and you should block and <a href="/tags/report/" rel="tag">#report</a> it to <a href="/tags/moderation/" rel="tag">#moderation</a>.</p><p>We are currently getting a wave of <a href="/tags/spam/" rel="tag">#spam</a> from bots like this. Again, do not even click the link, just block and report.</p><p>- TechHub Moderation</p>

<p>Please note: Until Mastodon&#x27;s bugged notification filters are fixed, I redirect all mentions to /dev/null.</p><p>Sorry for the inconvenience, but I can not tolerate the current amount of <a href="/tags/spam/" rel="tag">#SPAM</a>.</p>

<p>Codeberg: Spam and DoS attacks on non-commercial development platform</p><p>Masses of spam messages, overflowing email inboxes and clogged internet lines: Anonymous attacks plague the non-profit Github alternative.</p><p><a href="https://www.heise.de/en/news/Codeberg-Spam-and-DoS-attacks-on-non-commercial-development-platform-10281505.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon" rel="nofollow" class="ellipsis" title="www.heise.de/en/news/Codeberg-Spam-and-DoS-attacks-on-non-commercial-development-platform-10281505.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon"><span class="invisible">https://</span><span class="ellipsis">www.heise.de/en/news/Codeberg-</span><span class="invisible">Spam-and-DoS-attacks-on-non-commercial-development-platform-10281505.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon</span></a></p><p><a href="/tags/cybercrime/" rel="tag">#Cybercrime</a> <a href="/tags/dosschwachstelle/" rel="tag">#DoSSchwachstelle</a> <a href="/tags/git/" rel="tag">#Git</a> <a href="/tags/github/" rel="tag">#GitHub</a> <a href="/tags/opensource/" rel="tag">#OpenSource</a> <a href="/tags/softwareentwicklung/" rel="tag">#Softwareentwicklung</a> <a href="/tags/spam/" rel="tag">#Spam</a> <a href="/tags/news/" rel="tag">#news</a></p>

I am using Google Classroom, and Gmail is marking all email notifications from my Google classroom as spam. It&#x27;s email generated by one Google product going into another Google product. What on earth is happening to flag the notification as spam?<br><br><a href="/tags/google/" rel="tag">#Google</a> <a href="/tags/googleclassroom/" rel="tag">#GoogleClassroom</a> <a href="/tags/gmail/" rel="tag">#Gmail</a> <a href="/tags/spam/" rel="tag">#spam</a> <a href="/tags/monopolistsdontinnovate/" rel="tag">#MonopolistsDontInnovate</a><br><br>This post is not an invitation to scold me for using Google products or to suggest alternatives. It is also not a request for technical support.<br>

<p>Got spam emails this morning by someone who opened an issue on GitHub with what was probably a very unsafe link and then just tagged dozens of users over and over and over. Why we needed 50 copies in a row of the same notification, IDK. Thankfully, the account is terminated already, but if this starts to be a regular thing, I might have to abandon GitHub altogether.</p><p><a href="/tags/github/" rel="tag">#GitHub</a><br><a href="/tags/spam/" rel="tag">#Spam</a><br><a href="/tags/spammers/" rel="tag">#Spammers</a><br><a href="/tags/scammers/" rel="tag">#Scammers</a></p>

<p>If you get a DM saying &quot;call me the Fediverse chick&quot;, it&#x27;s a spam. Don&#x27;t click the links, but DO report it!</p><p>Reports from users are really important, especially if they are about spam DMs because no one else can see the spam except the user.</p><p>You can report posts by clicking ⋯ on the post and selecting &quot;Report&quot;. When you report it, make sure to select the option to forward the report to the server it came from so that the admin there can delete the spammer&#x27;s account.</p><p><a href="/tags/feditips/" rel="tag">#FediTips</a> <a href="/tags/spam/" rel="tag">#Spam</a></p>

<p>Just got push notification on my <a href="/tags/gnome/" rel="tag">#Gnome</a> desktop to donate to the project..... Very (NOT!) user friendly <span class="h-card"><a href="https://floss.social/@gnome" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>gnome</span></a></span> , I do wonder what is next... Ads? AI? 💔 </p><p><a href="/tags/gnome/" rel="tag">#gnome</a> <a href="/tags/spam/" rel="tag">#spam</a> <a href="/tags/notification/" rel="tag">#notification</a></p>

Since November 28th of this year I&#x27;ve received 22 spam emails with the same title &quot;Let&#x27;s start getting to know each other.&quot; (with the period at the end) from senders with names like Ellie, Emily, Harper, Olivia, and Aria. I haven&#x27;t been able to find information about an ongoing scam like this. Has anyone else been seeing this one?<br><br>(I&#x27;m not asking for advice about dealing with spam. SpamAssassin has this one well in hand. I&#x27;m just curious if anyone else has been seeing spam like this).<br><br><a href="/tags/spam/" rel="tag">#spam</a> <a href="/tags/email/" rel="tag">#email</a> <a href="/tags/askfedi/" rel="tag">#AskFedi</a><br>

<p>告知：垃圾消息攻击<br>最近有人在滥用开放注册的实例发送垃圾消息，来给一个游艇交易网站打广告。<br>你可以使用站内搜索功能搜索yachttrading并拉黑绝大多数帐号，管理员可以进一步封禁本站的帐号。垃圾消息通常包含一小段文字和一个到游艇交易网站的链接，文字使用的语言不定，但都非常生硬地试图把回复帖子的主题转到游艇上。<br><br><a href="/tags/垃圾消息/" rel="tag">#垃圾消息</a> <a href="/tags/什么值得b/" rel="tag">#什么值得B</a> <a href="/tags/spam/" rel="tag">#Spam</a><br><br>已经发现的垃圾消息帐号：<br><a href="https://dvd.chat/@lijh" rel="nofollow"><span class="invisible">https://</span>dvd.chat/@lijh</a><br><a href="https://dvd.chat/@jonnyking11" rel="nofollow"><span class="invisible">https://</span>dvd.chat/@jonnyking11</a><br><a href="https://dvd.chat/@kew11" rel="nofollow"><span class="invisible">https://</span>dvd.chat/@kew11</a><br><a href="https://dvd.chat/@keke" rel="nofollow"><span class="invisible">https://</span>dvd.chat/@keke</a><br><a href="https://dvd.chat/@kliu" rel="nofollow"><span class="invisible">https://</span>dvd.chat/@kliu</a><br><a href="https://dvd.chat/@winnie11" rel="nofollow"><span class="invisible">https://</span>dvd.chat/@winnie11</a><br><a href="https://dvd.chat/@xiaoli" rel="nofollow"><span class="invisible">https://</span>dvd.chat/@xiaoli</a><br><a href="https://dvd.chat/@likeke" rel="nofollow"><span class="invisible">https://</span>dvd.chat/@likeke</a><br><a href="https://dvd.chat/@lidada" rel="nofollow"><span class="invisible">https://</span>dvd.chat/@lidada</a></p>

My spam folder has taken on a special, highly-focused quality.<br><br>I&#x27;m not sure how Layla and May001 snuck past SpamAssassin but the assassin is being re-trained.<br><br><a href="/tags/spam/" rel="tag">#spam</a> <a href="/tags/junkmail/" rel="tag">#JunkMail</a> <a href="/tags/spamassassin/" rel="tag">#SpamAssassin</a> <a href="/tags/email/" rel="tag">#email</a><br>

<p>Marre des appels indésirables ? Un développeur français vous propose de bloquer plus de 16 millions de numéros sur iOS et Android.<br><a href="https://framablog.org/2025/09/23/sarah-qui-ca-raccroche/" rel="nofollow" class="ellipsis" title="framablog.org/2025/09/23/sarah-qui-ca-raccroche/"><span class="invisible">https://</span><span class="ellipsis">framablog.org/2025/09/23/sarah</span><span class="invisible">-qui-ca-raccroche/</span></a><br><a href="/tags/spam/" rel="tag">#spam</a> <a href="/tags/ios/" rel="tag">#ios</a> <a href="/tags/android/" rel="tag">#android</a></p>

This is a long time coming. I&#x27;ve been posting about the decline of arXiv&#x27;s CS category for a long time now, and even had a few conversations with someone I know who works there about it. Personally, I think the slop started in 2018--prior to generative AI slop--when the CS category at arXiv began the unsustainable exponential growth in submissions that has continued till today. An increasing number of what amounted to corporate whitepapers and other marketing materials were being posted on arXiv to give them the appearance of scientific credibility. There was a fairly clear arXiv-to-Nature pipeline. Citation counts were pumped as some of the scientometric services count arXiv &quot;articles&quot; as citations, and some researchers adopted the bad scholarly habit of citing arXiv preprints instead of the final publication. It was and still is a mess. My understanding is that arXiv was meant as a place for people to put high-quality but pre-publication articles, but at least in the CS category it&#x27;s drifted quite far from that.<br><br>I gather they&#x27;ve finally taken this measure because of the preponderance AI-generated slop, but with any luck these other issues will improve too. The arXiv press release states “Review/survey articles or position papers submitted to arXiv without this documentation will be likely to be rejected and not appear on arXiv” so it does sound like they are acknowledging the other problems and intend to enforce their rules more strictly in the future.<br><br>&quot;arXiv says it will no longer accept Computer Science papers that are still under review due to the wave of AI-generated ones it has received.&quot;<br>From <a href="https://infosec.exchange/users/josephcox/statuses/115486903712973154" rel="nofollow" class="ellipsis" title="infosec.exchange/users/josephcox/statuses/115486903712973154"><span class="invisible">https://</span><span class="ellipsis">infosec.exchange/users/josephc</span><span class="invisible">ox/statuses/115486903712973154</span></a><br><br><a href="/tags/arxiv/" rel="tag">#arXiv</a> <a href="/tags/preprint/" rel="tag">#preprint</a> <a href="/tags/cs/" rel="tag">#CS</a> <a href="/tags/spam/" rel="tag">#spam</a> <a href="/tags/aislop/" rel="tag">#AISlop</a> <a href="/tags/ai/" rel="tag">#AI</a> <a href="/tags/genai/" rel="tag">#GenAI</a> <a href="/tags/generativeai/" rel="tag">#GenerativeAI</a><br>

The companies that redirect me to their home page after I unsubscribe from their mailing list mystify me. Obviously I do not want to have you in my life any more so what are you even doing?<br><br><a href="/tags/spam/" rel="tag">#spam</a><br>

<p><a href="/tags/实例公告/" rel="tag">#实例公告</a> 封禁协同潜在的僵尸账户网络</p><p><p>今日检测并封禁了 5 个协同运作的僵尸账户</p></p><p>行为特征：</p><p>内容为 LLM 生成的无语义英文词句（虽然目前未做出实质性的危害，但是可能是为了养号，规避审查）<br>五个账户全部于2026年3月18日 17:52 — 2026年3月19日 23:50注册<br>账户Profile基本为：一段英文+emoji或者几段无意义英文句子<br>所有连接 IP 均属 Cloudflare 代理段<br>注册域名含一次性邮箱服务及高风险域名</p><p>已采取的措施：<br>封禁账户（经核查IP均为Cloudflare IP，未泄露任何用户隐私）：<br>@iwutyp 162.159.XXX.XX<br>@PhyllisReynolds 172.70.XXX.XXX<br>@ezob 104.23.XXX.XX<br>@uhux_xudym 104.23.XXX.XX<br>@Ethel_Robinson 172.68.XXX.XXX<br>封禁邮箱：<br>tmail.lt、maxseeding.vn、dqsbf.blema.io.vn、sphinx.launders.money、kimora.space</p><p>总结：<br>由于前段时间为了简化注册流程，关闭了人工审核<br>将开启“注册时需要批准”+“注册时需要提供理由”<br>如果大家有发现类似行为特征的新账户，相同邮箱域名/IP请谨慎辨别<br>本实例不欢迎任何恶意/不受管制的机器人注册</p><p><a href="/tags/mastodon/" rel="tag">#mastodon</a> <a href="/tags/fediverse/" rel="tag">#fediverse</a> <a href="/tags/antispam/" rel="tag">#antispam</a> <a href="/tags/spam/" rel="tag">#spam</a> <a href="/tags/实例管理/" rel="tag">#实例管理</a> <a href="/tags/moderation/" rel="tag">#moderation</a></p>

<p>Github的Microsoft/WSL仓库的issue区遭到中文博彩平台SPAM攻击</p><p>PR区未遭SPAM攻击，成为新的issue区（<br>WSL&#x27;s issues has been attacked for Chinese betting platforms：<a href="https://github.com/microsoft/WSL/pull/20669" rel="nofollow" class="ellipsis" title="github.com/microsoft/WSL/pull/20669"><span class="invisible">https://</span><span class="ellipsis">github.com/microsoft/WSL/pull/</span><span class="invisible">20669</span></a></p><p>遭到大量SPAM攻击的issue区和action区：<br><a href="https://github.com/microsoft/WSL/issues" rel="nofollow" class="ellipsis" title="github.com/microsoft/WSL/issues"><span class="invisible">https://</span><span class="ellipsis">github.com/microsoft/WSL/issue</span><span class="invisible">s</span></a><br><a href="https://github.com/microsoft/WSL/actions" rel="nofollow" class="ellipsis" title="github.com/microsoft/WSL/actions"><span class="invisible">https://</span><span class="ellipsis">github.com/microsoft/WSL/actio</span><span class="invisible">ns</span></a></p><p>看样子，官方机器人已经开始管理，比如加上tag:needs-author-feedback<br>目前SPAM issues仍在源源不断产生</p><p><a href="/tags/github/" rel="tag">#GitHub</a> <a href="/tags/spam/" rel="tag">#SPAM</a> <a href="/tags/issue/" rel="tag">#Issue</a></p>