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
0
0
0
9
0
1
0
0
1
0
0
0
0
0
0
0
0

🍏튜링의 사과 AI 커뮤니티 밋업[AI로 넌 뭘하니?]🤖

🍏튜링의 사과 AI 커뮤니티 밋업[AI로 넌 뭘하니?]🤖

튜링의 사과에서 AI 토론 & 공유 모임을 엽니다.
요즘 다들 AI 자동화, 에이전트 만들고, 서비스도 만들고 있는데
다른 사람들은 AI로 뭘 하고 있을까?그래서 만들어봤습니다.
첫 회는 자유로운 토론의 자리로 진행하고, 의견을 나누어 정기적인 모임을 만들어 보고자 준비했습니다.

📅 2026.03.28
⏰ 14:00 ~ 16:30
👥 선착순 30명 / 노쇼방지를 위해 참여금 5,000원
(튜사 이용권, 음료, 다과 제공)

장소
📍 성수 튜링의사과
서울 성동구 상원길 26 MILK빌딩 B1층 튜링의사과
(2호선 뚝섬역 5번출고 50M 내)

참여 👉
DM 또는 디스코드 티켓or DM문의

AI로 무엇갈 하고 있거나, 새로운 인사이트를 얻거나 공유하고싶다면 편하게 놀러오세요~!

📅 2026-03-28 14:00 — 16:30 (GMT+9)

Organized by: @TuringAppleDev@mastodon.social

View event details

1
1
0
0
1
0
0
1
Guild Board: Rails 8.1 기반 AI 협업 칸반 보드 프로젝트 상세 분석 Rails 8.1의 최신 기능을 극대화하여 외부 의존성을 최소화하고 PostgreSQL 기반의 Solid Stack을 활용한 고성능 칸반 보드 아키텍처를 구현했습니다. https://ruby-news.kr/articles/github-luisjang1206-guild-board-project-manangement-kanban-board-with-mcp-github
0
Basecamp API를 위한 완전한 기능의 Ruby 기반 MCP 서버: MFP-Basecamp 프로젝트 분석 MFP-Basecamp는 기존의 불완전한 구현체들을 뛰어넘어 Basecamp 3/4 API의 모든 기능을 지원하는 146개의 도구를 제공하는 Ruby 기반 MCP 서버입니다. https://ruby-news.kr/articles/github-merovex-mfp-basecamp-full-coverage-ruby-mcp-server-for-the-basecamp-3-4-api-146-tools-covering-the-entire-api-surface-with-auto-pagination-rate-limiting-and-token-refresh-works-with-claude-desktop-claude-code-and-any-mcp-client-github
0
0
0
0
AI 업스케일링을 활용한 예술 작품의 물리적 캔버스 프린트 제작 파이프라인 구축 사례 아티스트의 신뢰를 얻기 위해 명시적 동의와 공정한 수익 배분, 그리고 저작권 통제권을 보장하는 윤리적 가이드라인을 최우선으로 설정했습니다. https://ruby-news.kr/articles/rubyconfth-2026-alex-timofeev-making-canvas-prints-from-artwork-photos
0
0
0
0
0
0
1
0
0
2
1
0

Article about Asus' CEO talking about how the MacBook Neo is a "shock to the PC industry", and a comment about how PC manufacturers should have put some effort into developing a Linux alternative.

As if Asus didn't launch an ENTIRELY NEW CATEGORY OF COMPUTER BASED ON LINUX back in 2007.

Product shot of an Asus Eee-PC netbook running a version of Linux.
0
1
0
0
0
0
9
0
0

Buckle your seat belts. Someone just tried to pull one hell of a scam on me.

It began with an email I received on March 2nd. The email was from RB (name withheld), an editor at Pan MacMillan in the UK. She began by referencing a specific and somewhat obscure story thread from my one year run on writing Birds of Prey for DC Comics.

She went on to sing my praises, talk about interest in the Jem memoir, and mentioned many other highly specific works and aspects of my career. She talked about how my work might align with Pan MacMillan’s graphic novel and non-fiction catalogues. The final kicker was when she ended the email with a friendly quip about the number of my cats, something I’d just written about on my MoggyBlog FB page.

I was fairly stunned, not by the praise, but the extreme detail and specificity of the approach. I’ve seen plenty of samples of scams sent to authors that are always a bit vague and might mention one book title at most. This went way beyond that.

Which is why I failed to do the absolute number one smart thing I would normally have done – I didn’t look closely at her email address. I saw that it said macmillan and left it at that. I did look her up on the Pan MacMillan website and saw that she was a real person.

We exchanged a couple of emails and she strongly wanted me to have a literary agent. I’ve never needed one in the past and have always operated with only my entertainment agent. She was quite insistent that I needed one and recommended an agent named CD (name withheld) as someone she had worked with closely and had the right sensibility for my background. She gave me a personal email address for him, to “ensure he prioritizes your message”.

I checked out this agent and saw, once again, that he existed and was with a reputable UK agency. I found that the agency had a couple of co-agent associations with agencies in the US, including one I knew, the Howard Morhaim Agency. He looked legit.

So I did the thing -- wrote him an introductory email, and we’ve been exchanging a daily email every day for the past week, including on weekends. He was all about my “legacy”. We discussed specific projects, and he relentlessly pushed me to get something called a Dynamic QR code to create a Digital Author’s Bridge. I had never heard of such a thing, was only familiar with regular old static QR codes. We went back and forth on it a lot until I finally understood what he was talking about. It sounded like a good idea, but when I researched them, I found they were rather pricey to obtain and maintain.

I wanted more info on what his agency contract would include, what his commissions were, how he handled ancillary rights, the usual business items I would naturally want to know. He kept on about the QR code. His relentless push on the QR code is when I began to suspect something was off about this whole situation.

I pushed back harder and he finally gave a minimal amount of info on commissions, and kept pushing about the QR code. He insisted that we had to put that in place BEFORE signing a contract, or as he called it, a Letter of Engagement.

By now, the many little red flags grew into a Big Red Flag. Had I paid more attention to the fake email address in the very first message, that would have been a Big Red Flag right there, but I missed it. Mucho stupid on my part.

The red flags piled up:
• RED FLAG: insistence on doing this QR code before signing a contract.
• RED FLAG: not providing standard agent information about a contract or even wanting to discuss it.
• RED FLAG: the fact that the layout, structure, and phrasing of his emails were extremely similar to the RB emails, right down to the constant use of 3-bullet points as selling points.
• RED FLAG: a total lack of feedback to a creative project I proposed and instead simply accepting it without comment. No agent worth his salt is going to accept a quarter-page pitch without having feedback, opinions, wanting to know more, etc.
• RED FLAG: the constant push-push-push to get this blasted QR code before anything else.
• RED FLAG: ending nearly every email with the promise of a “global roll-out”. Of what? I had yet to write any of the things we were discussing.

When I began looking over the exchanges from the beginning, it seemed unlikely to me that “RB” would have done such a deep, deep dive into my work and background to include the specifics she did, not to mention reading my MoggyBlog. I mean, sure, it’s flattering, and it massages my ego, but I’m realistic.

Which left the notion that all or much of this was created using an LLM. If so, it’s the most nuanced one I’ve seen. It would have had to scour the internet for references to my work, such as articles, reviews, interviews, my amazon author page, and so on, then compiled it into a convincing email without including hallucinations or false references. If so, it represents a huge advance in the ability to scam authors and is therefore a significant threat.

If not, if it done by a person(s), they sure put one hell of a lot of effort into it.

During this process, I consulted with Victoria Strauss of Writer Beware. She gave me the official email for CD. I sent him an email in which I forwarded one of the last messages from “him” with a query. I received an automated reply that he was at London Book Fair and out of touch for email. The reply included the name of a colleague, so I sent the same email to her. She confirmed that the messages did not come from CD and appreciated that I brought it to their attention.

I’m trying to get a valid contact for RB, so I can warn her as well.

Meanwhile, fake CD’s next message went on about how his QR code set-up was so much better than other sites because it was free and permanent. RED FLAG. And it would integrate straight into my Amazon store to my author’s page. RED FLAG. And for the umpteenth time, he ended with a variation of “Once we have this simple link live, we can sign the formal agreement and get the global rollout moving immediately.” RED FLAG.

I played this out a bit longer, very carefully, because I couldn’t figure out what the ultimate scam was here. However, the mention of amazon store integration made me wonder whether I even had an amazon store.

I have a page that lists all my books. I don’t know whether that’s actually a store. I certainly don’t make any money off it, but I guess it’s meant to be my “store”.

Looking at my author’s bio on the amazon store, I suddenly realized that the reference to the number of cats was actually pulled from there, NOT from my MoggyBlog. By a bizarre coincidence, at the time I wrote that bio I mentioned a sixth cat possibly joining the horde. And very recently, I wrote almost exactly the same thing in the present. Different cats, different places, but so alike that it’s no wonder I assumed RB was speaking of my present situation, not the past.

I wrote that bio in 2018 shortly before the fire. After the fire and losing everything, being homeless and whatnot, I completely forgot this page and bio even existed. I haven’t looked at it since then.

I see where much of what was referenced came from there, including an off-hand comment about a ridge from RB that had puzzled me. In the bio I mentioned we lived on a volcanic ridge. That clinched that the material in RB’s emails was drawn from this seven-year-old bio on amazon, treating it as current.

The last email from the hoaxer is again about tying a QR code to my amazon store. All this effort is to gain control of my amazon store? To do what, create a horde of fake AI books with my name on them? To steal digital assets from me? Those are the best guesses I can make.

I sent an email today that will show the hoaxer I’m aware of the scam. We’ll see whether they bother to respond.

I’m posting this in detail to alert other authors and to lay out how the scam has proceeded. I would love to hear from anyone that has had a similar scam run on them. Take care out there.

Please spread this far and wide.

0
14
0
0
0

After trying a few different LLMs, I'm starting to think that letting them directly modify your project's code leads to non-deterministic output and knowledge that’s hard to reuse.

A better pattern might be using LLMs to build tools that then apply those changes in a deterministic way.

The knowledge stays in the tool instead of disappearing when the session ends.

Next thing I'll try to share these tools with others, or maybe letting an agent run them at scale.

Beach after a storm with calm, lightly rippled sea and a clear horizon under a blue sky with thin white clouds.
0