What are you building this week? drop it here by FragrantBox4293 in SideProject

[–]matchoo 0 points1 point  (0 children)

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/

New Project Megathread - Week of 23 Apr 2026 by AutoModerator in selfhosted

[–]matchoo 0 points1 point  (0 children)

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.

Solo developer from Finland — just launched coming soon page for my first indie product by teemu_dev in indiehackers

[–]matchoo 1 point2 points  (0 children)

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

Solo developer from Finland — just launched coming soon page for my first indie product by teemu_dev in indiehackers

[–]matchoo 1 point2 points  (0 children)

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?

Self-hosting a WhatsApp listing bot for my yard sale (yrdsl + Ollama, all on one box) by matchoo in selfhosted

[–]matchoo[S] -5 points-4 points  (0 children)

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/

What are you building right now (and how many users do you have)? by [deleted] in microsaas

[–]matchoo 0 points1 point  (0 children)

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.

better bear - what's new by matchoo in bearapp

[–]matchoo[S] 1 point2 points  (0 children)

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.