- TypeScript 82.1%
- Vue 14.6%
- Dockerfile 2.6%
- Shell 0.7%
|
|
||
|---|---|---|
| fedify-proposal-poc | Improve debugging follow requests | |
| LICENSE.md | update to new project | |
| README.md | Compatibility update | |
Economiverse
First implementations in fedify
Implementation of Proposal part of FEP-0837: Federated Marketplaces in Fedify with PR #589 and Release 2.2.0.
fedify proposal poc (poc = proof of concept)
This is simple proof of concept with 2 shops and one marketplace. Via the form you can add new products in the shop and they should appear in the marketplace. The database is resetted every 60 minutes to the seed origin.
| URL | Server Type | function |
|---|---|---|
| marketplace.playground.54gradsoftware.de | Marketplace | Agregates all proposals from different shops |
| shop-postcards.playground.54gradsoftware.de | Shop | Has offers with different postcards |
| shop-posters.playground.54gradsoftware.de | Shop | Has offers with different posters |
flowchart TD
A[Shop Posters]
B[Shop Postcards]
C[Marketplace - List all products from all connected shops]
A-->C
B-->C
This is really limited proof of concept but it should show that the fedify implementation for "Proposal" is working according to FEP-0837.
next steps
- Example Project for federated daily changing menues (menuverse)
- WIP: Compatibility with flohmarkt
- Full Implementation of FEP-0837 in Fedify version 2.3
- poc with a full transaction from a marketplace to a shop
- building full shop system
- building full marketplace system
Limiting factor is currently no time because of funding. This might be resolved by a nlnet funding.
general goal
The goal is to build a federated, open-source e-commerce ecosystem that addresses the needs of small businesses and makers in the Fediverse. The project consists of two connected endeavours. First, we develop a simple shop system using FEP-0837: Federated Marketplace and semantic data to enable creatives to create products, accept and fulfill orders. Shops can either operate as conventional web interfaces and/or via the fediverse ordering system. The second milestone covers the marketplace software. Users can browse through products from multiple federated shops in one place, providing the name, image, description, shipping info and price of a product. They can communicate with the seller and follow shops to receive notifications about new products. An allow-list for participating shops reduces the risk of scam. In this project phase, payment, shipping logistics and digital product distribution are out of scope, but could be integrated later on. Nevertheless, users can initiate the transaction in two ways: directly via the marketplace account that already stores physical and email address (FEP-0837) or they visit the original shop.
possible use cases
- alternative to etsy or "online kunsthandwerkermarkt"
- one or multiple marketplaces
- focus marketplaces only agreating shops with hand made products, vegan products and so on
- generally ecomerce
- restaunt / canteen menu plans
- especially canteen menu plans which are changing daily
- listing services from companies, like: software development, communication, design work ...
- listing service products like hosting a mastodon instance, hosting emailes, so on
- listing different grant programs like nlnet, prototypefund, cc-stipendium
- listing different public/government services from different government levels, government agencies, or non-governmental organizations which are providing services for the government
- Using marketplaces to get products and services to complete semantic-defined blueprints.