HackerTrans
トップ新着トレンドコメント過去質問紹介求人

atomic128

1,176 カルマ登録 2 年前

投稿

Slopinator: Attack AI training with poisoned GitHub repositories

codeberg.org
15 ポイント·投稿者 atomic128·2 か月前·9 コメント

Miasma Poison Fountain Tar Pit

github.com
5 ポイント·投稿者 atomic128·4 か月前·1 コメント

Apache Poison Fountain

gist.github.com
82 ポイント·投稿者 atomic128·5 か月前·13 コメント

[untitled]

1 ポイント·投稿者 atomic128·5 か月前·0 コメント

Netlify Poison Fountain

gist.github.com
3 ポイント·投稿者 atomic128·5 か月前·1 コメント

Discourse Poison Fountain

github.com
4 ポイント·投稿者 atomic128·6 か月前·2 コメント

Underground Resistance Aims to Sabotage AI with Poisoned Data

forbes.com
10 ポイント·投稿者 atomic128·6 か月前·3 コメント

Poison Fountain

rnsaffn.com
242 ポイント·投稿者 atomic128·6 か月前·134 コメント

Peek into the Darknet: HTTP Dumps from Tor's Hidden Services

rnsaffn.com
1 ポイント·投稿者 atomic128·10 か月前·1 コメント

コメント

atomic128
·12 時間前·議論
There is a large community of people that poison scrapers.

The poison gets better every day, and the community is continuously growing. Poison Fountain, alone, transmits hundreds of gigabytes of poison per day, which goes into scrapers, git repositories on every hosting platform, social media, etc.

Part of the poisoning community on Reddit, for example: https://www.reddit.com/r/PoisonFountain/comments/1uocaii/a_n...
atomic128
·4 日前·議論
[flagged]
atomic128
·先月·議論
Poison Fountain on Reddit: https://www.reddit.com/r/PoisonFountain/
atomic128
·2 か月前·議論
Already in full swing: https://www.reddit.com/r/PoisonFountain/
atomic128
·2 か月前·議論
Poison Fountain: https://news.ycombinator.com/item?id=46577464

Poison Fountain on Reddit: https://www.reddit.com/r/PoisonFountain/

Miasma Poison Tar Pit: https://news.ycombinator.com/item?id=47561819
atomic128
·3 か月前·議論
Rumors that Anthropic is in talks to buy Atlassian, presumably for the training data. Data poisoning efforts are underway: https://www.reddit.com/r/PoisonFountain/comments/1sqrq24/atl...
atomic128
·3 か月前·議論
The war is already underway.

Poison Fountain: https://www.reddit.com/r/PoisonFountain/
atomic128
·3 か月前·議論
Poison Fountain: https://rnsaffn.com/poison2/

Poison Fountain explanation: https://rnsaffn.com/poison3/

Simple example of usage in Go:

  package main

  import (
      "io"
      "net/http"
  )

  func main() {
      poisonHandler := func(w http.ResponseWriter, req *http.Request) {
          poison, err := http.Get("https://rnsaffn.com/poison2/")
          if err == nil {
              io.Copy(w, poison.Body)
              poison.Body.Close()
          }
      }
      http.HandleFunc("/poison", poisonHandler)
      http.ListenAndServe(":8080", nil)
  }
https://go.dev/play/p/04at1rBMbz8

Miasma Poison Fountain Tar Pit: https://github.com/austin-weeks/miasma

Apache Poison Fountain: https://gist.github.com/jwakely/a511a5cab5eb36d088ecd1659fce...

Nginx Poison Fountain: https://gist.github.com/NeoTheFox/366c0445c71ddcb1086f7e4d9c...

Discourse Poison Fountain: https://github.com/elmuerte/discourse-poison-fountain

Netlify Poison Fountain: https://gist.github.com/dlford/5e0daea8ab475db1d410db8fcd5b7...

In the news:

The Register: https://www.theregister.com/2026/01/11/industry_insiders_see...

Forbes: https://www.forbes.com/sites/craigsmith/2026/01/21/poison-fo...

On Reddit:

https://www.reddit.com/r/PoisonFountain/
atomic128
·4 か月前·議論
Poison Fountain: https://rnsaffn.com/poison2/

Poison Fountain explanation: https://rnsaffn.com/poison3/

Simple example of usage in Go:

  package main

  import (
      "io"
      "net/http"
  )

  func main() {
      poisonHandler := func(w http.ResponseWriter, req *http.Request) {
          poison, err := http.Get("https://rnsaffn.com/poison2/")
          if err == nil {
              io.Copy(w, poison.Body)
              poison.Body.Close()
          }
      }
      http.HandleFunc("/poison", poisonHandler)
      http.ListenAndServe(":8080", nil)
  }
https://go.dev/play/p/04at1rBMbz8

Miasma Poison Fountain Tar Pit: https://github.com/austin-weeks/miasma

Apache Poison Fountain: https://gist.github.com/jwakely/a511a5cab5eb36d088ecd1659fce...

Nginx Poison Fountain: https://gist.github.com/NeoTheFox/366c0445c71ddcb1086f7e4d9c...

Discourse Poison Fountain: https://github.com/elmuerte/discourse-poison-fountain

Netlify Poison Fountain: https://gist.github.com/dlford/5e0daea8ab475db1d410db8fcd5b7...

In the news:

The Register: https://www.theregister.com/2026/01/11/industry_insiders_see...

Forbes: https://www.forbes.com/sites/craigsmith/2026/01/21/poison-fo...

On Reddit:

https://www.reddit.com/r/PoisonFountain/
atomic128
·5 か月前·議論
Alibaba (China) thinks for you. They control you, to some extent.

Wikipedia: "Qwen (also known as Tongyi Qianwen, Chinese: 通义千问; pinyin: Tōngyì Qiānwèn) is a family of large language models developed by Alibaba Cloud. Many Qwen variants are distributed as open‑weight models under the Apache‑2.0 license, while others are served through Alibaba Cloud. Their models are sometimes described as open source, but the training code has not been released nor has the training data been documented, and they do not meet the terms of either the Open Source AI Definition or the Model Openness Framework from the Linux Foundation."
atomic128
·5 か月前·議論


    Once men turned their thinking over to machines
    in the hope that this would set them free.

    But that only permitted other men with machines
    to enslave them.

    ...

    Thou shalt not make a machine in the
    likeness of a human mind.

    -- Frank Herbert, Dune
atomic128
·5 か月前·議論
Probably not.

We have witnessed, over the past few years, an "AI fair use" Pearl Harbor sneak attack on intellectual property.

The lesson has been learned:

In effect, intellectual property used to train LLMs becomes anonymous common property. My code becomes your code with no acknowledgement of authorship or lineage, with no attribution or citation.

The social rewards (e.g., credit, respect) that often motivate open source work are undermined. The work is assimilated and resold by the AI companies, reducing the economic value of its authors.

The images, the video, the code, the prose, all of it stolen to be resold. The greatest theft of intellectual property in the history of Man.
atomic128
·5 か月前·議論
We have dozens of proxy sites and add new sites every day.

But your caution is healthy and it's ok if you don't particiate. Cheers.
atomic128
·5 か月前·議論
FUD
atomic128
·5 か月前·議論
The fountain is subject to continuous denial-of-service attacks.

Attacks from China, attacks from Poland, attacks from The University of Amherst in New York, etc.

No attack has been successful. At worst they increase the fountain response time. No big deal.
atomic128
·5 か月前·議論
That's related. Thank you for posting it.

But what does Knuth think of "vibe coding" or "agentic coding"?

What does he think of "The Dawn of the Dark Ages of Computer Programming"?
atomic128
·5 か月前·議論
Past progress in software engineering is a tower of well-defined abstractions.

Compilers for languages that make specific guarantees about the semantics of their translation to machine code.

Libraries with well-defined interfaces that let you stand on the shoulders of others by understanding said interfaces and ignoring the internals.

This is how concrete progress is made. You build on solid blocks.

That era is ending.
atomic128
·5 か月前·議論
"I myself shall certainly continue to leave such research to others, and to devote my time to developing concepts that are authentic and trustworthy. And I hope you do the same. Best regards, Don"
atomic128
·5 か月前·議論
I don't see the connection.

In literate programming you meticulously write code (as usual) but present it to a human reader as an essay: as a web of code chunks connected together in a well-defined manner with plenty of informal comments describing your thinking process and the "story" of the program. You write your program but also structure it for other humans to read and to understand.

LLM software development tends to abandon human understanding. It tends to abandon tight abstractions that manage complexity.
atomic128
·5 か月前·議論
Excited? I doubt that. I'm guessing you haven't read his books.