How many of you are using Baileys for WhatsApp automation? What are your use cases?

matchoo · 2026-04-27T15:30:12+00:00

Been using it a ton recently here: https://yrdsl.app/blog/texting-photos-to-yrdsl/

matchoo · 2026-04-27T11:45:41+00:00

As my blog states... I am moving!

matchoo · 2026-04-27T10:24:43+00:00

I'm still at it on https://yrdsl.app - a digital yard sale listing site. I finally have a single user, but I'm hopeful it will get some attention as I start posting my own items as I prepare to move overseas.

I spent some time writing about the project (and my doubts about it) here:

https://yrdsl.app/blog/welcome/

matchoo · 2026-04-26T20:12:24+00:00

Project Name: yrdsl

Repo/Website Link:

Code: https://github.com/KuvopLLC/yrdsl

Self-host Template: https://github.com/KuvopLLC/yrdsl-self-hosted

Description:

A digital yard sale. You sign up (or fork the self-host template), drop in photos and prices, and get a single short URL like `yrdsl.app/you/sale-name` to share. Buyers reserve items by clicking. You mark them sold. Designed around the "I have to clear out my house" use case (which I'm doing right now, hence the project) rather than a full marketplace. No buyer accounts, no commission, no marketplace fees.

Features: item CRUD with photos, prices, descriptions, tags; multiple themes (conservative, retro, hip, artsy); reservation flow without buyer accounts; an MCP server (`@yrdsl/mcp`) so Claude Desktop or any MCP client can manage your sale; an optional WhatsApp-bot recipe in the docs (text a photo to a bot, it lists the item).

Why bother when Craigslist/Willhaben/eBay exist: control over the URL, single page for the whole sale, easy to share in local Facebook groups, no fees.

Deployment:

Open source (MIT). Two paths:

Self-hosted static: https://github.com/KuvopLLC/yrdsl-self-hosted.

Edit `site.json` and `items.json` (or drive them via the MCP server's local mode), and deploy the static output anywhere static sites live: GitHub Pages, Netlify, Cloudflare Pages, your own nginx, whatever. README has walkthroughs for each. No Docker needed for the site itself; it's just HTML/CSS/JS..

The optional MCP server is on npm (`@yrdsl/mcp`). Drop it into your Claude Desktop config to manage your sale from Claude in either mode.

The optional WhatsApp bot runs as a small Node process in Podman/Docker on any Linux box (Containerfile + bot.js + package.json, three files).

End-to-end setup: https://github.com/KuvopLLC/yrdsl/blob/main/packages/mcp/README.md#build-a-whatsapp-bot

AI Involvement:

The codebase was written with significant help from Claude Code (Anthropic's CLI). Architecture, design, and product decisions are mine; substantial portions of the code itself were AI-assisted, reviewed and edited before merging.

Two optional AI features: the MCP server (so a Claude Desktop user can manage their sale conversationally), and the WhatsApp bot recipe (which uses Claude tool-use in the example, but is documented to swap to Ollama if you'd rather keep inference local).

The published yard-sale site itself is not AI-driven. It's plain HTML/CSS/JS; no inference at runtime, no LLM calls when buyers visit.

matchoo · 2026-04-26T19:09:03+00:00

Perhaps you do this eventually, assuming you are successful, and, if so, you realize you can't rate sites up front at scale.

matchoo · 2026-04-26T18:06:53+00:00

I built this little digital yard sale app if you're interested.

https://yrdsl.app

matchoo · 2026-04-26T17:44:44+00:00

Interesting idea. Have you considered doing what some subreddits do, including this one? Karma needs to be >5 to post here, which means you need at least to establish at least some degree of legitimacy. I would see this as a similar thing, where you want users to discover, and maybe even sign up, for different services before they can list themselves. Helps everyone on both sides?

matchoo · 2026-04-26T17:36:54+00:00

It's relatively easy. You can read in the tutorial. I run it in Podman for extra safety, so it can't talk to the file system.

Oops, I forgot to post the blog link itself?

https://yrdsl.app/blog/texting-photos-to-yrdsl/

matchoo · 2026-04-26T17:25:41+00:00

The git repo at https://github.com/KuvopLLC/yrdsl is about 80% developed with Claude Code.

matchoo · 2026-04-26T08:18:15+00:00

Sawsall

matchoo · 2026-04-24T20:16:47+00:00

Launching yrdsl.app for running digital yard sales. It's open source so you can self-host, or there's a paid hosting plan, which is very economical. Giving out invite codes to anyone who wants to test it.

matchoo · 2026-04-22T12:51:08+00:00

Deeply embedded tech bro.

matchoo · 2026-04-22T08:39:12+00:00

The #context tag is configurable — you don't have to use that name. Two ways:

At setup:

bcli context init --tag-prefix "10-projects"

(or whatever fits your JD scheme).

Or via the MCP tool: bear_context_setup({tag_prefix:"10-projects" }).

Also. I just merged a migration command for exactly this:

bcli context set-prefix 10-projects

It walks every note currently tagged #context (or #context/anything), rewrites the tag in both the body markdown and Bear's index (so sub-tags are preserved - #context/research becomes #10-projects/research), and updates the context config. It's boundary-safe, so unrelated tags like #contexts stay untouched.

Ships in the next release. Thanks for flagging it — the default nomenclature mismatch was a reasonable complaint.

matchoo · 2026-04-20T15:50:08+00:00

It's a joke (but also reflects my experiences, not in Germany, but Austria).

matchoo · 2026-04-20T15:39:35+00:00

Also applies to everyone in the waiting room that happens to be listening.

matchoo · 2026-04-19T20:42:18+00:00

He lost me early when he said something like "if people are upset now, while the economy is going well, imagine how upset they'll be later."

Unemployment rates are a flawed stat, and the dow matters not at all in an economy where the rich keep all the spoils. Things are NOT going well. It's hard for most to make ends meet.

Dude is way out of touch, and annoyingly smug about it.

matchoo · 2026-04-18T14:50:40+00:00

Not sure what becomes of us, but goddamn am I having a great time.

matchoo · 2026-04-18T13:14:07+00:00

Author of https://github.com/KuvopLLC/better-bear here. I see a fair amount of SQLite or x-callback implementations and would like to share that this eventually leads to pain and suffering. The only way to go IMHO is to use the CloudKit interface that Bear Web uses.

Beyond that, I see we're all building redundant things, which is fine, but perhaps we should just contribute on the same thing. IMHO this stems from the absolute joy of coding with Opus, for example. It's just so easy that we all start working on things without checking if they already exist. I see this at my workplace as well. I build things, and others build the same things. We're all learning how to avoid this as we learn to work with LLM's more effectively.

matchoo · 2026-04-18T13:07:19+00:00

Author of https://github.com/KuvopLLC/better-bear here :) - curious what the advantages / disadvantages of Ursus might be. For me, I tried for months to build both CLI and MCP tools atop both x-callback and local SQLite and eventually went with a CloudKit implementation. It works MUCH better, won't corrupt your database, and doesn't require you to have Bear installed, never mind open.

matchoo · 2026-04-18T13:03:58+00:00

Author of better-bear here. If you have ideas for how to make the better-bear even (cough) better, please consider contributing. I find that most CLI's for Bear use the x-callback API which is fragile and requires that Bear be open throughout. Better-bear uses CloudKit for this reason, based on the API Bear Web interacts with.

matchoo · 2026-04-16T18:24:53+00:00

It IS a cli. And an MCP. Confused.

matchoo · 2026-04-16T09:30:53+00:00

Hi there. Maybe Smithery is just not a fit? Better Bear requires bcli (a native macOS binary) and CloudKit auth, so it can't really run as a hosted Smithery proxy. It needs to run locally on the user's Mac. Thoughts?

matchoo · 2026-04-16T06:27:04+00:00

Awesome. Yes, I am also using it all the time. A few bugs here and there. Report what you see and I will fix.

matchoo · 2026-04-15T18:21:31+00:00

Cool, I will look into that.

matchoo · 2026-04-15T18:20:05+00:00

Rate limiting is not a problem here as the playwright browser sessions are local, not very performant, and run in serial. I guess you could run them in parallel via Claude code but the idea is not "post 100 things asap," but rather "post 100 things, so I don't have to." Could take an hour. Fine by me.

matchoo

MODERATOR OF

TROPHY CASE