Jumpino
Updated
Finding a useful repository is only half the job. You also need to remember why it mattered and where you saw it. I am building Scouvi as a personal project to connect those parts of research. The image is an interface preview, not a launch announcement.
Preview supplied by the creator. Scouvi is a personal project under development.
Preview supplied by the creator. Scouvi is a personal project under development.
From discovery to a personal collection
The intended flow starts with topics and sources: GitHub for repositories, Reddit for communities and discussions, and opportunities indexed from sources including LinkedIn. Results retain their original links. The private library accepts GitHub repositories, organized with folders, tags and notes. For Reddit and LinkedIn, users keep the search to revisit rather than a copy of every profile or post.
An architecture that keeps the context
The project uses Astro SSR, TypeScript, React components for interactive workspaces and SQLite for application persistence. GitHub provides the planned sign-in route. Discovery relies on SearXNG plus indexing and cache services. Personalization follows explicit interests and saved activity; it is not a trained recommendation model.
What I am checking next
The priority is making the route between searching, inspecting and saving dependable while keeping collections private. OAuth configuration, external services and production workflows still need verification. Editorial and advertising tools are also under development, but I am not presenting them as an operating commercial service. Scouvi gives me a concrete problem to work on: retaining the reason for a discovery alongside its link.
Working on something similar? Tell me what it needs to do.