fix(outreach): koniec z martwymi watkami, wlasnymi odpowiedziami i narzedziami do naduzyc - #169
Merged
Merged
Conversation
… tools
The queue of eight leads reviewed on 2026-08-17 contained no actionable
work at all. Five threads were closed and resolved, the oldest since
August 2024. Two were open but untouched since 2022. The eighth was
genuinely live and a genuine fit - and the owner had already answered it
six days earlier.
Two of those eight were worse than useless: an email bomber and a
phishing-simulation framework. Recommending a shared-domain relay as
either one's sending path puts @msgwing.com behind their traffic, and
every other user of that domain pays for it.
Three gates the bot never had:
* `is:open` on every GitHub query. Two of the three carried only
`is:issue`.
* A 120-day recency limit on GitHub results. Stack Exchange stays
exempt - an answer there earns from search for years, so an old
unanswered question is still worth answering.
* `-commenter:<owner>`, so the bot stops re-queueing threads we have
already replied to. That is the difference between a queue of work
and a queue of things already done.
Plus abuse tooling on the skip list: bomber, phishing, spammer, mail
flood, brute force.
The whole queue was closed with a reason each, so none of it returns.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Przejrzałem całą kolejkę ośmiu leadów. Nie było w niej ani jednej okazji do działania.
prometheus/alertmanager#3244nodemailer#1726freescout#4930azure-devops-engineering-extensions#111gophish#3220email-bomber-v2.0#1mailR#107gpslogger#1302Dwa z nich były gorsze niż bezużyteczne. Podanie ścieżki wysyłkowej bomberowi albo frameworkowi phishingowemu stawia współdzieloną domenę
@msgwing.comza ich ruchem, a płacą za to wszyscy inni użytkownicy tej domeny.Trzy bramki, których bot nie miał
is:openw każdym zapytaniu. Dwa z trzech miały tylkois:issue.-commenter:<owner>— bot przestaje kolejkować wątki, na których już odpowiedzieliśmy. To jest różnica między kolejką pracy a kolejką rzeczy już zrobionych.Plus narzędzia do nadużyć na liście odrzuceń:
bomber,phishing,spammer,mail flood,brute force.Cała kolejka zamknięta z osobnym uzasadnieniem dla każdego wpisu, więc żaden nie wróci.