Many years ago a substantially sized OSS groups' forum software (maybe KDE or Qt? it was a long time ago) was accidentally including user email addresses in the non-user-visible html tags of forum pages.
Web scanners though aren't people, and easily noticed them, thus building up a database of email addresses to spam people.
It was discovered when a friend mentioned that one of their uniquely generated email addresses was being used by spammers. Similar to this post.
So, we got in contact with the forum people to let them know, and they tracked down + fixed the problem.
Perhaps a similar thing is happening to the article author, rather than purposely malicious behaviour?
Yeah. Things like "Complete results, architectural decisions, and runnable code below." is literally how AI outputs stuff, so I'd expect the post was AI written too. :(
By "those applications" I'm talking about other applications affected by this regression. There are several apps in addition to Redis that recommend limiting the transparent huge page configuration. (Some of them recommend using explicit huge pages instead.) But it's quite possible none of them are affected by this regression, as it may be particular to apps using spinlocks. (Certainly the new rseq API mentioned in the thread is targeted at spinlock users.) It seems equally possible to me that some spinlock-using app has a regression irrespective of huge pages.
"In response to an NPR request, a Navy spokesman acknowledged that 1,500 sailors, their families and several hundred pets were relocated back to the U.S. from NSA Bahrain."
Because the US moves civilians out of an active war zone?
Web scanners though aren't people, and easily noticed them, thus building up a database of email addresses to spam people.
It was discovered when a friend mentioned that one of their uniquely generated email addresses was being used by spammers. Similar to this post.
So, we got in contact with the forum people to let them know, and they tracked down + fixed the problem.
Perhaps a similar thing is happening to the article author, rather than purposely malicious behaviour?
reply