Log in to discuss and edit this issue
Magnova aims to create a new economy that doesn't depend on markets or money for distributing goods and services. A large part of the infrastructure necessary for this is a database of Resources. In the context of Magnova, "Resource" with a capital R specifically means "one kind of physical item".
Each Resource will have its own page on Magnova that stores information about the Resource, which Projects/Tasks it can be used for, which users want to share it or give it away, Formulas for how to make it with different materials or tools, links to Formulas that make use of it, a unit for quantifying it, and potentially any other data that could be useful.
Resources will be semantically organized. That means the meaning of the resource is key to how a person finds it. Rather than throwing all of our Resources onto a single feed, creating arbitrary algorithms and categories a priori, you can look for a specific thing, and see many people giving that exact thing away. You shouldnt have to expend creative researching work to find the thing you're looking for. The method for searching should intuitively lead you to the Resource you want.
Resources on Magnova will be recursively organized to make it more semantic, meaning "tool" is a Resource that breaks down into "hammers", "screwdrivers", "power washer", etc. Then, each of those breaks down into subtypes, e.g. screwdriver has children "flat head", "phillips head", "hex", etc. In this fashion, you can ask for Resources specifically or broadly.
The automatic metadata such as proximity or post date that governs how salient an item is in other sharing networks is not useful for getting things you need, rather it creates a Secret Santa scenario where you have access to random listings that are one-off. Their short lifespan and disconnection from other listings of the same kind of thing means they cannot use crowdsourcing to accrue meaningful data that helps connect gifters to recipients. Further, these systems are fundamentally incapable of integrating with production or systemic distribution.
The Magnova community says the following issues give rise to Resource. Addressing this issue could be accomplished by dealing with the following sub-issues. (Registered users can upvote/downvote these connections.)
The following projects have been created by the Magnova community to address this issue. (Registered users can upvote/downvote which projects they want to see implemented.)
Is Resource affecting your community? Issue pages, like the one you're on now, are ideal for talking about general problems. Each Issue can be deployed to a Location to create a "Local Issue" page, where users can measure an Issue's impact on that Location, and discuss things that are particular to the community.
None identified yet! Registered users can identify new Local Issues.
This QR code links to this page. Print stickers, add it to fliers, or chalk it onto your driveway.