Here is the article in The New Stack:
https://thenewstack.io/ai-is-spamming-open-source-repos-with-fake-issues/
On Fri, Jan 31, 2025 at 12:39 PM Jarek Potiuk wrote:
> Hey,
>
> I am at FOSDEM now but I have some progress and more information about the
> whole stuf:
>
> Some fa
sing moving forward:
>
> Hello,
> >
> > This Issue appears to be AI-generated spam. If this is a mistake, please
> > let us know—otherwise, any further spam Issues may lead us to report your
> > account to GitHub.
> >
>
> On Mon, Jan 27, 2025 at 10:16 AM Jar
FYI. My friend - who is an engineering manager at GitHub in the "AI" space
- saw my post and reached out to their internal team fighting with Spam. I
hope they will be able to do something about it as well.
On Mon, Jan 27, 2025 at 8:21 AM Jarek Potiuk wrote:
> > Given what
> Given what I read about the company, they will most likely ignore you.
Some people think the company is a scam, and they seem to engage in
unethical business practices.
Yeah, but it absolutely does not mean we should give up and do nothing.
Hopefully that will give at least some people a pause
, 2025 at 2:53 PM Jarek Potiuk wrote:
> Starting at Linkedin. They don't seem to be on Mastodon or Bluesky, I quit
> X and don't care any more for content there.
>
> -> if you would like to share it, feel free:
>
>
> https://www.linkedin.com/posts/jarekpotiuk_out
J.
On Sun, Jan 26, 2025 at 2:43 PM Jarek Potiuk wrote:
> Ok. The issue continues. I am raising to a bit higher level and start to
> complain on https://outlier.ai/ in social media - they are driving those
> issues.
>
> On Thu, Jan 23, 2025 at 7:59 PM Russell Spitzer
> wrote:
ors & maintainers.
> > Either indirectly -- by extending high quality projects, or directly --
> by
> > observing how project maintainers react to these issues.
> > Since the maintainers' time is a 'free resource' for them, it
> economically
> > makes s
n 23, 2025 at 7:54 PM Jarek Potiuk wrote:
>
> This ultimately means they train AI on the contributors & maintainers.
>> Either indirectly -- by extending high quality projects, or directly -- by
>> observing how project maintainers react to these issues.
>> Since the m
> This ultimately means they train AI on the contributors & maintainers.
> Either indirectly -- by extending high quality projects, or directly -- by
> observing how project maintainers react to these issues.
> Since the maintainers' time is a 'free resource' for them, it economically
> makes sense
ot; that we are going to get. But I
am already suggesting to some of the friends working with AI that having
OSS-friendly AI services to filter out such "AI slop" is a very good
business to have.
J.
On Thu, Jan 23, 2025 at 9:20 AM Jarek Potiuk wrote:
> Just as a little follow up - I
omated tools to submit issues is just adding noise to the
> project
> > which makes it very hard for real issues to be addressed.
> >
> > On Wed, Jan 22, 2025 at 6:58 AM Jarek Potiuk wrote:
> >
> >> - Iceberg dev to not flood them :) (in bcc:)
> >>
>
arts testing those AI agents.
>
> Regards,
> Pavan Kumar
>
> On Wed, Jan 22, 2025, 10:27 Jarek Potiuk wrote:
>
> > We continue getting new issues - and more of them are by "new users" -
> > created just an hour or so ago.
> >
> > Apparently Github has
ell :)
J.
On Wed, Jan 22, 2025 at 10:36 AM Jarek Potiuk wrote:
> Yeah. just closed this one. The pattern where those are coming at the same
> time as two unrelated issues to both iceberg and airflow are very.
> strange
>
> On Wed, Jan 22, 2025 at 10:35 AM Elad Kalif wrot
apache/iceberg/issues/12034
> https://github.com/apache/airflow/issues/45920
>
> Same "mistake" with the # Title.
> All of these seem to come with accounts opened months ago, with some minor
> traffic to their own forks so they would appear legit to Github
>
> On Wed,
at's probably the case, still going through my mailbox.
>
>
> Op wo 22 jan 2025 om 09:49 schreef Jarek Potiuk :
>
> > Example case:
> >
> > * https://github.com/apache/airflow/issues/45904 - airflow
> > * https://github.com/apache/iceberg/issues/12034 - i
number of issues in iceberg and airflow about the same
time. So you might have more such issues now than you think.
J.
On Wed, Jan 22, 2025 at 9:41 AM Jarek Potiuk wrote:
> I have not counted all of them. there are quite a bit too many - and
> other people closed some of them as well.
r to the project.
>
> Kind regards,
> Fokko
>
> Op wo 22 jan 2025 om 09:00 schreef Jarek Potiuk :
>
> > Hey Iceberg community, And Airflow community too.
> >
> > As of yesterday Airflow repo is literally flooded with a number of issues
> > that look almost
g it to Github - and
hopefully they will find a way to battle those without involving
maintainers.
I hope it will not last too long.
J.
-- Forwarded message -
From: Jarek Potiuk
Date: Wed, Jan 22, 2025 at 8:12 AM
Subject: Re: Very strange (AI generated) issues
To:
You can al
I also forwarded it to `users@infra` - so that the infra people are aware
of it.
On Wed, Jan 22, 2025 at 9:00 AM Jarek Potiuk wrote:
> Hey Iceberg community, And Airflow community too.
>
> As of yesterday Airflow repo is literally flooded with a number of issues
> that look almost
Hello Iceberg community,
Just a reminder, that there are just 6 days left to submit your proposal
for The Community Over Code NA (former ApacheCon) conference.
This is the flagship event for the ASF in Halifax, Nova Scotia, Canada,
October 7-10, 2023 and together with Ismael, we want to encourage
Hello Iceberg community members !
TL;DR: Call For Papers for Community Over Code NA conference in Halifax in
October *ends in 4 weeks (13th of July!)* and this is about the last moment
to prepare and submit your proposals:
https://communityovercode.org/call-for-presentations/
*Community Over Code
21 matches
Mail list logo
