Support my open-source work

Help me keep shipping backend, systems, and agent-ops work.

I'm Shirong Lu. I build practical public assets around Go, Java, distributed systems, RPC, infrastructure-oriented engineering, and reusable backend tooling. Popular public assets like Resume (160+★) and CSAPPLabsAndNotes (70+★) bring many people here; recent OSS code work spans HashiCorp go-retryablehttp, Prometheus client_golang / procfs, golang-jwt, chi, urfave, pflag, and OpenTelemetry. If one repo, checklist, contribution, or engineering note saved you time, the fastest way to support more work like this is to scan the QR codes below or book a lightweight async review. If a GitHub repo page shows a Sponsor button, it routes to this same support page. If github-profile-checklist or the Resume template helped you, a small tip or a ¥99 async review is the cleanest way to keep these public backend assets improving.

Shameless version: I'm trying to get the first sustainable ¥100 / month from practical OSS. If one repo saved you ten minutes, a direct ¥9.9 / ¥19.9 tip is already the fastest way to help.

Current offer: the first paid request in July gets one extra public page / README in the same async pass at no extra charge.

Best conversion path: if you came from qq-ai-bot, RDLeader, Resume, or github-profile-checklist, don't overthink it—either tip ¥9.9 / ¥19.9 right now or buy the ¥29.9 quick read and send one public link.

If you need a sponsor-ready summary first: open the sponsor one-pager for concrete payment notes, proof links, and current targets. If you want the audit trail, see the support surface coverage.

Best for job seekers Best for indie devs Best for OSS maintainers
Go Java RPC Distributed systems Backend engineering Infra tooling Reusable repos
Tip in 10 seconds Pick support path Buy ¥29.9 quick read Book ¥99 async review Email quick-read template Email async-review template View GitHub profile Sponsor one-pager Share kit Sponsor prospect pipeline Sponsor conversion scorecard Support coverage Proof before payment Productized offer cards Intake guardrails See qq-ai-bot See Resume template See github-profile-checklist See sample audit See go-service-starter See review details

Productized offer cards

Use these if you want support to map to a visible public outcome or a concrete paid review instead of a vague donation.

Fund a real host report Best fit — homelab / CasaOS / NAS / SBC users who can run a real device report for qq-ai-bot. Note — qq-ai-bot #26 arm64 Outcome — one real physical ARM / CasaOS / NAS / SBC report added to the public tracker.

Open tester pack · Track qq-ai-bot #26

Fund curator follow-up Best fit — people who want RDLeader reviewed in agent / coding-agent lists. Note — RDLeader #27 Outcome — one scheduled-review update or maintainer reply follow-up, logged publicly.

Open submission tracker · Track RDLeader #27

Buy a deploy read Best fit — bot / agent / infra repos that run but still look toy-like. Note — Deploy read or Quick read Outcome — one blunt first-impression pass with top 3 fixes and the first deploy / README / landing-page wording to rewrite.

Preview deploy-read sample · Order quick read

Tip with attribution Best fit — readers helped by a repo, checklist, or OSS fix. Note — repo name, for example happydb, go-service-starter, or go-http-middleware-kit Outcome — maintenance credit can be summarized in the operations log when material.

Tip now · Open source offer cards

Guardrails: do not say physical ARM / CasaOS validation is complete before a real report lands; keep the RDLeader license caveat visible because RDLeader #27 is not a license grant; only send public links for paid reads and keep payment evidence private by email.

Sponsor / paid-support intake replies

If someone asks how to pay, sponsor, or buy a review, start with the proof-safe intake replies before sharing payment screenshots or private context.

Use the intake kit Copy the before-payment, paid-review intake, or sponsor receipt reply so the public thread stays on proof links, current asks, and public repo/profile/landing-page material.

Open sponsor / paid-support intake replies · Open full share kit

Route by audience Use the sponsor prospect pipeline to choose the right proof, CTA, support note, and guardrail for homelab testers, bot builders, curators, sponsors, RDLeader evaluators, and paid-review customers.

Open sponsor prospect pipeline · Current asks

Qualify before asking Use the sponsor conversion scorecard to classify an ask as Hot / Warm / Nurture / No-send before posting. No-send means improve proof or wait instead of creating a generic donation bump.

Open sponsor conversion scorecard · Support router

Public privacy guardrail Do not paste private logs, credentials, QR codes, payment screenshots, internal URLs, or raw live integration output in public issues. Move payment evidence and private context to email / private chat.

Email private payment evidence · Quick read

Proof before payment

If you are deciding whether to tip, sponsor, or buy a review, start here: this is the shortest source-linked proof path before money changes hands.

Map Technical proof — the flagship map shows architecture boundaries, operator proof, maintenance proof, external proof, support notes, and caveats for qq-ai-bot and RDLeader.

Open technical map · Open status snapshot · Open share kit · Profile CI workflow · Profile CodeQL workflow

0 Configured open alerts — current configured CodeQL / Dependabot / secret-scanning counts are tracked for profile, qq-ai-bot, and RDLeader. Older repos without CodeQL are not over-claimed.

Read maintenance proof · Read support coverage

Share Copy-ready snippets — use the share kit for X, LinkedIn, WeChat, curator context, sponsor CTA, and paid-review copy that keeps caveats intact.

Open share kit · Open prospect pipeline · Check follow-up queue

Pay Concrete notes — use qq-ai-bot #26 arm64 for real physical ARM / CasaOS validation, RDLeader #27 for external review follow-up, or Quick read for a paid first pass on your own public link.

See current asks · Buy ¥29.9 quick read · Tip now

Caveat: qq-ai-bot has green QEMU / workflow arm64 smoke, but the real physical ARM / CasaOS / NAS / SBC report is still the open support target. RDLeader's license posture is still tracked separately, so support does not imply a reuse grant.

Current concrete asks

Pick one of these if you want your support to map to a visible public outcome instead of a vague donation.

Test qq-ai-bot #26 arm64 — run the real ARM / CasaOS / NAS / SBC validation path and submit a redacted report. QEMU arm64 smoke is green; physical-host proof is still missing.

Open tester pack · Open project page · Track #26

Fund RDLeader #27 — support external submission review follow-up, public-safe proof packaging, and curator responses for the agent-ops control-plane project.

Open project page · Track #27 · Sponsor proof

Buy ¥29.9 quick read — send one public repo/profile/page link and get one blunt first-impression paragraph plus top 3 fixes.

Read offer · Email quick-read template

Best payment notes: qq-ai-bot #26 arm64, RDLeader #27, Quick read, or the repo name that helped you.

Came from a specific repo? Use the shortest support path

If one repo already saved you time, do not overthink it. Use the matching note below so the payment feels tied to a real public asset, not a generic donation.

qq-ai-bot Flagship repo — current operator-facing bot / agent integration asset Best note — qq-ai-bot, qq-ai-bot setup, or qq-ai-bot #26 arm64 Best fit — tip ¥9.9 / ¥19.9 if it saved you OneBot / ACP wiring time; use ¥29.9 if you want a blunt first pass on your own bot / agent repo; use ¥99 if you want the fuller packaging pass. It is now also visible from the public OneBot ecosystem page, the official OneBot “应用 / SDK” discussions, a live Docker Compose sample PR, a public CasaOS app-store PR, and a pending Umbrel App Store PR, and stable + multi-arch public image paths (v0.1.7 + latest, amd64 + arm64), so this note is easier to tie to a real public project.

Highest-conversion paid ask from this repo: “my bot technically runs, but the deploy / README / landing-page story still looks janky.”

Tip now · Buy ¥29.9 quick read · Send deploy-read email · See sample deliverable

RDLeader Agent-ops repo — local-first control plane for AI R&D workers, with public-safe proof ladder and fake-data demos Best note — RDLeader, RDLeader #27, RDLeader #1, or agent ops Best fit — tip ¥9.9 / ¥19.9 if the proof ladder helped your own agent-ops thinking; use ¥29.9 if you want a blunt first pass on your own AI / agent repo; use ¥99 if you want the fuller GitHub / README / landing-page packaging pass.

Current sponsor target: external submission follow-up, public-release sanitization, demo polish, and license/reuse posture clarification.

Tip now · Buy ¥29.9 quick read · Book ¥99 async review · Open project page · See current sponsorware issue

Resume Best note — Resume Best fit — tip ¥9.9 / ¥19.9 if the template saved you setup time; use ¥29.9 if you want a blunt read on your own portfolio / profile.

Tip now · Buy quick read · See latest support note · See support discussion · See FAQ · See case note

CSAPPLabsAndNotes Best note — CSAPPLabsAndNotes Best fit — tip ¥9.9 / ¥19.9 if one lab note saved you a debugging detour; use ¥29.9 only if you also want your own page reviewed.

Tip now · Buy quick read · See latest support note · See support discussion · See FAQ · See case note

github-profile-checklist Best note — github-profile-checklist Best fit — tip ¥9.9 / ¥19.9 if the checklist helped; use ¥99 if you want the same cleanup applied to your own profile / pinned repos / README.

Tip now · Book ¥99 async review · See support discussion · See FAQ · See case note

system-design-checklist Best note — system-design-checklist Best fit — tip ¥9.9 / ¥19.9 if it helped your interview prep or architecture review; use ¥29.9 if your own design materials need a blunt first-impression pass.

Tip now · Buy quick read · See support discussion

production-readiness-checklist Best note — production-readiness-checklist Best fit — tip ¥9.9 / ¥19.9 if it caught a release / handoff risk; use ¥29.9 if you want your own checklist or repo judged quickly.

Tip now · Buy quick read · See support discussion

backend-engineer-checklist Best note — backend-engineer-checklist Best fit — tip ¥9.9 / ¥19.9 if it helped you prioritize backend growth; use ¥99 if you want your public backend story packaged more clearly.

Tip now · Book ¥99 async review · See support discussion

go-service-starter Best note — go-service-starter Best fit — tip ¥9.9 / ¥19.9 if this starter saved you initial service wiring time; use ¥29.9 if you want a blunt README / repo pass.

Tip now · Buy quick read · See support discussion

go-http-middleware-kit Best note — go-http-middleware-kit Best fit — tip ¥9.9 / ¥19.9 if one middleware saved you copy-paste time; use ¥29.9 if your own backend repo feels technically okay but under-packaged.

Tip now · Buy quick read · See support discussion

happydb Best note — happydb or database internals Best fit — tip ¥9.9 / ¥19.9 if this repo saved you database-internals study time; use ¥29.9 or ¥99 if you want the same packaging applied to your own systems / Java / portfolio repo.

Tip now · Book ¥99 async review · See support discussion

HRpc Best note — HRpc or Java RPC framework Best fit — tip ¥9.9 / ¥19.9 if it helped your Java / Netty / RPC study; use ¥29.9 or ¥99 if you want the same packaging applied to your own backend / systems repo.

Tip now · Buy quick read

Ways your support helps

I want to keep shipping practical public assets rather than half-finished personal experiments. Support helps me spend more time on things that are genuinely useful to backend and systems engineers.

  • improving starter templates and developer tooling
  • publishing more backend / systems learning material
  • shipping more code fixes and implementation-oriented open-source contributions
  • turning rough internal ideas into reusable public repositories

If you want to support my work without paying, that still helps a lot:

  • star and share my repositories
  • link my projects to other backend engineers
  • open issues with concrete suggestions
  • reference the projects in communities, blogs, or newsletters

Zero-cost ways to help right now

  • star the repo that helped you instead of only bookmarking it
  • share one useful link in a backend / AI / bot / interview-prep group
  • mention the exact repo name when recommending it, so the link keeps compounding
  • if qq-ai-bot helped, the best short pitch is OneBot 11 + ACP + /metrics + Docker demo
  • if Resume helped, say it is a clean GitHub Pages portfolio template, not just a random HTML resume
  • if github-profile-checklist helped, share the checklist plus the sample audit link together
  • if one OSS fix helped you debug something weird, link the PR or release note when sharing
  • this kind of targeted sharing compounds better than a generic “follow me” ask

Small support is enough

If one repository, checklist, template, or code contribution saved you time, a small direct tip is already meaningful.

¥9.9 If one repo, note, or checklist saved you ten minutes.
¥19.9 If a checklist or repo helped your interview prep, onboarding, or design review.
¥49.9 If a starter template or writeup saved you real implementation time.

Any amount is appreciated. If you are supporting because of a specific repo, feel free to mention it in the payment note.

Best note to include: repo name + what it helped with (for example: `Resume`, `CSAPPLabsAndNotes`, `github-profile-checklist`, or `pflag`). That makes support feel tied to real engineering value instead of a generic donation.

Low-friction tip path: if one repo or checklist saved you time, ¥9.9 / ¥19.9 is already meaningful and helps keep these public backend assets improving.

If qq-ai-bot helped: the cleanest note is qq-ai-bot or qq-ai-bot setup; if you want the same packaging applied to your own bot / agent repo, the ¥29.9 quick read or ¥99 async review is the best paid path.

If happydb helped: the cleanest note is happydb or database internals; for most readers the best path is still a direct ¥9.9 / ¥19.9 thank-you tip.

If HRpc helped: the cleanest note is HRpc or Java RPC framework; for most readers the best path is still a direct ¥9.9 / ¥19.9 thank-you tip.

If CSAPPLabsAndNotes helped: the cleanest note is CSAPPLabsAndNotes; for most learners the best path is just a direct ¥9.9 / ¥19.9 tip, not an overthought request.

If github-profile-checklist helped: the ¥99 async review is the fastest way to turn the checklist into a concrete set of edits for your own profile, pinned repos, or README.

If go-service-starter or go-http-middleware-kit helped: the cleanest note is go-service-starter or go-http-middleware-kit; for most users the best path is still a direct ¥9.9 / ¥19.9 thank-you tip.

If backend-engineer-checklist helped: the cleanest note is backend-engineer-checklist; use the ¥29.9 / ¥99 path only if you want the same blunt cleanup applied to your own GitHub or README.

If system-design-checklist or production-readiness-checklist helped: the cleanest note is system-design-checklist or production-readiness-checklist; for most users the best path is still a direct ¥9.9 / ¥19.9 thank-you tip.

If Resume or an old student repo resonated: the quick review is often the highest-conversion option—send one public link and I tell you exactly what to hide, keep, or rewrite first.

¥29.9 quick blunt read

The lowest-friction paid option. Best if you want the sharp answer first before paying for a full rewrite pass.

  • Scope — one public GitHub profile, repo, README, or landing page
  • Deliverable — one blunt first-impression paragraph + top 3 fixes
  • Best use — “does this page feel weak / random / too student-like?”
  • Turnaround — usually faster than the full async review
  • How to buy — pay via WeChat Pay or Alipay, then email the public link plus payment screenshot
  • Best subject — Quick read | profile/repo/page link
  • Not included — no full rewrite, no multi-page audit, no bundled pass
  • Upgrade path — if you want concrete rewrites and repo-ordering help, use the ¥99 async review below
  • Current offer — first paid request in July gets one extra public page / README in the same pass

After paying: what to send

  • Tips / support — payment note with the repo or page that helped, e.g. qq-ai-bot, Resume, or system-design-checklist
  • Quick read — note Quick read and email one public link plus the payment screenshot
  • Deploy read — note Deploy read and email one repo link plus the deployment shape and what feels stuck
  • Async review — note Async review and email the public link(s), target role or use case, and what feels weak
  • Email — [email protected]
  • Best subject — Quick read | link or Async review | target role | repo/profile link
  • Fastest conversion path — tip directly if one repo saved you time; use the ¥99 path if you want concrete edits back

One-click email templates

If you already paid, the lowest-friction path is to open one of these, replace the placeholders, and attach the payment screenshot.

Open quick-read email Open async-review email

Fastest path: one public link + one sentence about what feels weak is enough to get started; keep payment screenshots out of public issues and attach them only to email / private chat.

Need to see the output style first? the deploy-read sample is the closest preview for bot / agent / infra repos.

One lightweight async review = ¥99

The simplest way to support practical open-source work and get something concrete back. Best fit if github-profile-checklist helped and you want me to apply the same cleanup to your own profile, repo, or portfolio page.

  • GitHub profile / pinned repos — positioning, proof-of-work ordering, and signal cleanup
  • Public repo README — title, description, setup flow, architecture framing, and CTA polish
  • Portfolio page — wording, credibility, and conversion fixes
  • Production readiness checklist — sanity-check a service launch / release checklist for obvious gaps
  • Scope — one public profile, repo, or page per request
  • Step 1 — pay via WeChat Pay or Alipay
  • Step 2 — email the public link(s), target role, what feels weak, and a payment screenshot to [email protected]
  • Suggested subject — Async review | target role | repo / profile link
  • Step 3 — I reply with compact, prioritized feedback plus ready-to-paste wording / README edits / repo-ordering suggestions, not just general advice
  • Typical turnaround — usually within 72 hours for ¥99 requests, often faster for simple profile / README passes
  • Best use of ¥99 — GitHub profile packaging, pinned repo ordering, README cleanup, or one focused landing page
  • Current offer — first paid request in July gets one extra public page / README in the same pass
  • Bundle option — ¥199 for a GitHub profile + one repo README + one resume-site / landing-page packaging pass
  • Preview first — if you want to see the style of output, start from the redacted sample audit in github-profile-checklist

Paid support / collaboration

If you want to support my work and also get something useful back, these are the fastest options.

  • ¥19.9 — tip for a repo, article, checklist, or doc contribution that saved you time
  • ¥29.9 — one quick blunt GitHub / README / landing-page first-impression read
  • ¥49.9 — thank-you support for interview prep material, backend checklists, or system design notes
  • ¥99 — one lightweight async feedback request on a public GitHub profile / README / repo positioning / portfolio page / production-readiness checklist
  • Deliverable — concrete copy edits, repo-ordering suggestions, README section rewrites, and credibility / conversion notes instead of vague advice
  • Current offer — first paid request in July gets one extra public page / README in the same pass
  • Email template — send: role target + link + what feels weak + payment screenshot
  • ¥199 — bundled GitHub profile + one repo README + one portfolio-page / landing-page packaging pass
  • Best payment note — write the exact repo that helped, e.g. Resume, github-profile-checklist, go-service-starter, or go-http-middleware-kit
  • After paying, you can mention the repo or page that helped you in the payment note.
  • Best fit for interview packaging, public repo positioning, and polishing technical assets so they feel more credible.
  • If Resume, CSAPPLabsAndNotes, or a checklist helped, a small direct tip is already meaningful.
  • If a repo page shows a Sponsor button, it routes here as the same support entry.
  • If you want lightweight paid feedback, contact me by email: [email protected]
  • I currently accept support through WeChat Pay and Alipay only.
  • If you just want to say thanks for a useful repo, tipping directly is the fastest path.

Best fit

  • Job seekers — use the ¥99 async review if you want your GitHub, pinned repos, and README lineup to feel more hireable.
  • Indie devs — use a small tip if a checklist, starter template, or landing-page idea saved you implementation time.
  • OSS maintainers — tip if one contribution, docs clarification, or bug fix saved triage or integration time.
  • Fastest support path — direct WeChat Pay / Alipay tip.
  • Highest-value paid option — ¥99 async profile / README / landing-page packaging review.
  • Most common trigger — “one repo saved me ten minutes, so I tipped.”

What you may know me from

  • go-service-starter — a minimal production-minded Go HTTP service starter
  • go-http-middleware-kit — reusable net/http middleware for request IDs, structured logs, recovery, timeout, and real IP handling
  • qq-ai-bot — production-grade QQ ↔ AI bot scaffold using OneBot 11, ACP agent bridging, persistent sessions, progress streaming, and multi-arch image smoke evidence
  • RDLeader — local-first control plane for AI R&D workers with task ownership, context routing, runtime dispatch, approval gates, and QA evidence
  • happydb — a Java database internals learning project covering storage, indexes, MVCC-style visibility, recovery, optimization, and replication experiments
  • backend-engineer-checklist — a practical roadmap for backend engineering fundamentals
  • system-design-checklist — a practical framework for interviews, design reviews, and distributed-systems tradeoffs
  • production-readiness-checklist — a launch / go-live checklist for backend services and release reviews
  • github-profile-checklist — a practical checklist for making a GitHub profile look more intentional, technical, and hireable
  • Resume — a reusable résumé / portfolio template with 160+ stars
  • hashicorp/go-retryablehttp#288 / #289 / #290 / #291 / #292 / #293 — a run of focused Go behavior fixes around response handling, nil-body safety, logger safety, readable backoff bodies, deadline-aware retry waits, and safe zero-value defaults
  • spf13/pflag#485 — make explicit empty typed slice values round-trip as empty slices instead of parse errors
  • prometheus/client_golang#2040 — clamp out-of-range formatted timestamps to avoid overflow on round-trip parsing
  • prometheus/procfs#833 — split proc stat limit coverage by architecture to keep 32-bit and 64-bit parsing checks correct
  • urfave/cli-altsrc contribution — add StringMap-compatible config value support for JSON / YAML / TOML sources
Thanks for supporting practical open-source work.
Shirong Lu · happysnaker