Custom Nostr Fork Development
Budget: €250 – €750 EUR
I’m forking primal.net and need a seasoned TypeScript engineer who is totally at ease working Git-first and can dive straight into a Nostr codebase. The immediate goal is to introduce a suite of non-public features around improved listings and, above all, a powerful personalised content-suggestion layer.
Scope
• Extend the existing front-end and back-end (TypeScript, React, Node) with the new private listing modules I will outline in Figma and Notion.
• Build a recommendation engine grounded in socio-psychology principles rather than the usual collaborative or content-based filters. I will supply the research notes and sample scoring model; you will translate them into production code, unit tests, and API endpoints.
• Keep everything behind a feature flag so the public fork remains untouched until each block is signed off.
Workflow & Delivery
• Each milestone (“project block”) will be clearly ticketed in GitLab; payment is released only when the block’s MR is merged and passes CI tests. No hourly billing.
• You push code daily, write concise commit messages, and open merge requests early for review.
• All work must stay 100 % compatible with Nostr protocol changes upstream; regular rebasing against primal.net main is expected.
Acceptance Criteria for each block
1. All new TypeScript passes eslint and unit coverage ≥ 90 %.
2. Feature flag toggles behaviour without regressions.
3. CI/CD pipeline green; deployment succeeds on our Visual Studio preview.
4. My manual test script (I’ll provide) completes with zero critical issues.
If you can blend clean TypeScript, a solid Git flow, and an appetite for experimenting with socio-psychological recommendation logic, let’s get started on the first block right away.
Scope
• Extend the existing front-end and back-end (TypeScript, React, Node) with the new private listing modules I will outline in Figma and Notion.
• Build a recommendation engine grounded in socio-psychology principles rather than the usual collaborative or content-based filters. I will supply the research notes and sample scoring model; you will translate them into production code, unit tests, and API endpoints.
• Keep everything behind a feature flag so the public fork remains untouched until each block is signed off.
Workflow & Delivery
• Each milestone (“project block”) will be clearly ticketed in GitLab; payment is released only when the block’s MR is merged and passes CI tests. No hourly billing.
• You push code daily, write concise commit messages, and open merge requests early for review.
• All work must stay 100 % compatible with Nostr protocol changes upstream; regular rebasing against primal.net main is expected.
Acceptance Criteria for each block
1. All new TypeScript passes eslint and unit coverage ≥ 90 %.
2. Feature flag toggles behaviour without regressions.
3. CI/CD pipeline green; deployment succeeds on our Visual Studio preview.
4. My manual test script (I’ll provide) completes with zero critical issues.
If you can blend clean TypeScript, a solid Git flow, and an appetite for experimenting with socio-psychological recommendation logic, let’s get started on the first block right away.