What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

1. 쿠키런 오븐브레이크 일단 제일 밉고 논란있는 장르부터 청산하고 들어가보도록 하죠.. 워낙에 파생작이 많은 ip인데다 제가 참 오래 몸 담고 있는 장르긴 해서.. 쿠키런 시리즈로만 4번까지 나올거 같음... 일단 가장 오래토록 붙잡고 있긴 해요... 이제 그냥 접고픈데 계정이 아까워서 못 접는 지경이 되어버린게 오래인 게임임.. 근데 논란도 그렇고 하는 운영 꼬라지도 그렇고 여러모로 접고싶은 게임입니다..

0
1
0

It was interesting to read up on the AI assisted code review at lesswrong.com/posts/7aJwgbMEiK

For context: I'm personally responsible for at least 29 curl CVEs. Out of the recent 6 CVEs mentioned in the blog post I found two. This gives me some perspective, I think.

I do not utilise AI tools in my vulnerability research. I am also fiercely critical of harmful proliferation of AI. This is due to the unsustainable way it is currently pushed, and use of as marketing ploy and gimmick rather than producing measurable benefit to users. This leads to negative impacts on economy, education & learning, not to mention impacts to nature due to wasteful use of energy.

This doesn't mean I am against AI. I have written by own AI tooling (fully local RAG with support for arbitrary number of models running on local nodes, implemented in python). I found the usefulness of such tool to be limited at best. It is somewhat useful in mass analysis of large document bases, but the level of analysis is superficial at best. These AI models are after all just language models, and do not have any true understanding or intelligence.

And here is the gist of it: The current tools are not intelligent. Understanding this limitation is the key of successful deployment and utilisation of AI tools. The tools can be useful in certain tasks, but they do not replace true intelligence.

The AI tooling AISLE are developing certainly is one of the better uses of AI, and definitely surpasses all my personal dabbling around it. It is clear that the tool does find vulnerabilities. The key question is how much hallucinations and false positives it produces: If the tool generates thousands of FPs and the true findings are hidden among them this limits the value and usefulness of the tool (of course it doesn't entirely negate it, many tools produce false positives). In short: The quality of the findings is key, and poor signal-to-noise ratio is highly undesirable.

Either way, I think there is a future for AI tools and they definitely will be helpful in vulnerability research.

I personally will keep exercising my wetware for this work, however.

0
0
0
0
0
1
0
1
2
1
0
0
0
0
0
1
0
0
3
1

Never doubt yourself, I'm proof that you can go beyond your wildest expectations and do the unthinkable.

You just need to remember that you can.

Dreams are blueprints. Waiting for you.
Don't forget that ❤️

0
2
2
0
0
1
1
0
0
0
0
0
0
2
0
1
0
0
0
1

32 People Died in ICE Custody in 2025, as Killings Spark Outrage

“Of those who died in custody last year include Geraldo Lunas Campos, whose death in has been ruled a homicide.

Also Wael Tarabishi, who died of a rare genetic disease thirty days after his father, Wael’s primary caregiver, was detained by ICE after a routine check-in at an immigration facility in Dallas.”

people.com/deaths-ice-custody-

0
0
0
1
0
0
0
1

All over the world, politicians are being forced by their communities to address the evils of data centers

Resistance to data centers fuels flood of Georgia bills targeting the industry

Georgia legislators have proposed seven bills regulating data centers by eliminating tax breaks, prohibiting costs from being passed on to residential electricity customers, or temporarily barring their construction entirely.

capitol-beat.org/2026/01/resis

0
1
0
1

I don't keep a full-fidelity list in my mind of which Debian packages contain every executable because it's easier to relegate that info to outboard-brain tools instead.

For tools that I have locally installed, e.g. ls(1), `dpkg --search "$(which ls)"` (or `dpkg -S "$(which ls)"`) looks up which package owns the tool.

For packages not locally installed, visiting e.g. manpages.debian.org/ls#:~:text and then peeking at the "Source file:" page footer shows me the package name.

0