bitcoin bounties for unbazaar
37 views
Skip to first unread message
dinosaur
Mar 30, 2013, 7:47:20 PM3/30/13
to unho...@googlegroups.com
hi,
i agree that remoteStorage is awesome and we need to do something cool
with it.
i have been thinking about a decentralized open source marketplace:
unbazaar. the general idea is to provide an unhosted webapp people can
use to
- post listings of tools (tools use recipes + materials to produce goods)
- post listings of recipes (an example of a recipe is a 3d printer design)
- trade money for the sharing of tools, materials, recipes, and goods.
in the end it must provide a friendly interface to the various specs of
[PaySwarm](http://payswarm.com/) and [the Web Payments Community
Group](http://www.w3.org/community/webpayments/).
unbazaar requires creating, reading, updating, and deleting from many
remoteStorage modules containing a variety of object types. this can be
done with an open source framework that implements
(CRUD)[https://en.wikipedia.org/wiki/Create,_read,_update_and_delete) on
JSON-LD objects (http://json-ld.org). i think the easiest way to do this
is to generalize an existing remoteStorage webapp.
[litewrite](https://github.com/litewrite/litewrite) is a stable editor
that implements CRUD on documents; i think it can be carefully
generalized beyond documents and thus fulfill the role of a webapp i
like to call 'un'. if done properly, i believe un is capable of being a
solid foundation for the unhosted movement by allowing one application
to fulfill many use-cases.
i think this project would be best done by the community for the
community, so i'm offering bitcoin bounties for completing work on the
road to un/bazaar. this summer my roommate and i will have at least 3
months to devote to un/bazaar, but in the meantime we could really use
some help.
un/README.md
# un
un is a platform for unhosted applications, forked from litewrite.
[dinosaur](https://dinosaur.io) will pay bitcoins to developers who
complete items on the todo list. contact dinosaur with any questions,
comments, critiques, or suggestions. everything is open to
consideration, including bounty amounts.
## todo
### now
litewrite to un/documents:
- 5 btc to fork litewrite into un/documents.
- generalize document storage module to be applied to any number of
independent remoteStorage modules with any number of type definitions.
- generalize read view so something like views/{module}/{type}/read.js
applies to type objects within module.
- generalize write view so something like
views/{module}/{type}/write.js applies to type objects within module.
- make sure un/documents has consistent behavior with litewrite.
- change default ui of un/{module} to something at least:
un/{module}
__________
|_{obj.id}_| + - r w
|_{obj.id}_|
|_{obj.id}_| read / write view
|_{obj.id}_| of obj.id
|_{obj.id}_|
|_{obj.id}_| => CRUD-ing obj
|_{obj.id}_|
|_{obj.id}_|
|_{obj.id}_|
where
- +,-,r,w are buttons corresponding to add, delete, toggle to read
mode, toggle to write mode
- modules are suffixed after un/ like subreddits are to r/
- objects are listed by id in a column on the left
- current object is in either read or write view
### short-term future
#### related to un/
- 2 btc to add public reads of others
- change default ui of un/{module} to something at least:
un/{module}
__________________________________________________
|__ self___|_other_|_other_|_other_|_other_|_other_|
__________|_other_|_other_|_other_|_other_|_other_|
|_{obj.id}_|_other_|_other_|
|_{obj.id}_| + - r w
|_{obj.id}_|
|_{obj.id}_| read / write view
|_{obj.id}_| of obj.d
|_{obj.id}_|
|_{obj.id}_| => implements CRUD
|_{obj.id}_|
|_{obj.id}_|
- 1 btc each to add 'calendar' and 'todo' modules.
#### related to un/bazaar
- 2 btc each to add 'tool' and 'recipe' modules (to CRUD Web Commerce
assets)
- http://payswarm.com/specs/source/web-commerce/
- http://www.heppnetz.de/ontologies/goodrelations/v1.html
- tool types that must be supported:
- 3d printer
- build volume
- resolution
- types of materials supported (white ABS, blue PLA, etc)
- cnc machine
- build volume
- resolution
- types of materials supported (douglas fir, aluminum, steel, etc)
- types of drills/routers supported
- laser cutter
- build area
- power wattage
- recipe types that must be supported:
- 3d design (for 3d printer or cnc machine)
- 2d design (for laser cutter)
- recipe generalized to use tools to transform materials into goods.
- circuit schematic
- 3 btc to add 'keys' module (to CRUD Web Keys)
- http://payswarm.com/specs/source/web-keys/
- 5 btc for integrating the above and completing an interface to CRUD
PaySwarm listings on un/bazaar
### medium-term future
- ? btc for un/wallet integrating Web Payments
- http://payswarm.com/specs/source/web-payments/
- ? un/bazaar using un/wallet for payments on listings
### long-term future
- implement a method of monetization roughly such that a minimal
percentage (~1%) of every transaction is sent to a transparent fund
operated by dinosaur to be used for sponsoring un/ development.
- implement Payment Intents (like Kickstarter, IndieGoGo)
- http://payswarm.com/specs/source/payment-intents/
i agree that remoteStorage is awesome and we need to do something cool
with it.
i have been thinking about a decentralized open source marketplace:
unbazaar. the general idea is to provide an unhosted webapp people can
use to
- post listings of tools (tools use recipes + materials to produce goods)
- post listings of recipes (an example of a recipe is a 3d printer design)
- trade money for the sharing of tools, materials, recipes, and goods.
in the end it must provide a friendly interface to the various specs of
[PaySwarm](http://payswarm.com/) and [the Web Payments Community
Group](http://www.w3.org/community/webpayments/).
unbazaar requires creating, reading, updating, and deleting from many
remoteStorage modules containing a variety of object types. this can be
done with an open source framework that implements
(CRUD)[https://en.wikipedia.org/wiki/Create,_read,_update_and_delete) on
JSON-LD objects (http://json-ld.org). i think the easiest way to do this
is to generalize an existing remoteStorage webapp.
[litewrite](https://github.com/litewrite/litewrite) is a stable editor
that implements CRUD on documents; i think it can be carefully
generalized beyond documents and thus fulfill the role of a webapp i
like to call 'un'. if done properly, i believe un is capable of being a
solid foundation for the unhosted movement by allowing one application
to fulfill many use-cases.
i think this project would be best done by the community for the
community, so i'm offering bitcoin bounties for completing work on the
road to un/bazaar. this summer my roommate and i will have at least 3
months to devote to un/bazaar, but in the meantime we could really use
some help.
un/README.md
# un
un is a platform for unhosted applications, forked from litewrite.
[dinosaur](https://dinosaur.io) will pay bitcoins to developers who
complete items on the todo list. contact dinosaur with any questions,
comments, critiques, or suggestions. everything is open to
consideration, including bounty amounts.
## todo
### now
litewrite to un/documents:
- 5 btc to fork litewrite into un/documents.
- generalize document storage module to be applied to any number of
independent remoteStorage modules with any number of type definitions.
- generalize read view so something like views/{module}/{type}/read.js
applies to type objects within module.
- generalize write view so something like
views/{module}/{type}/write.js applies to type objects within module.
- make sure un/documents has consistent behavior with litewrite.
- change default ui of un/{module} to something at least:
un/{module}
__________
|_{obj.id}_| + - r w
|_{obj.id}_|
|_{obj.id}_| read / write view
|_{obj.id}_| of obj.id
|_{obj.id}_|
|_{obj.id}_| => CRUD-ing obj
|_{obj.id}_|
|_{obj.id}_|
|_{obj.id}_|
where
- +,-,r,w are buttons corresponding to add, delete, toggle to read
mode, toggle to write mode
- modules are suffixed after un/ like subreddits are to r/
- objects are listed by id in a column on the left
- current object is in either read or write view
### short-term future
#### related to un/
- 2 btc to add public reads of others
- change default ui of un/{module} to something at least:
un/{module}
__________________________________________________
|__ self___|_other_|_other_|_other_|_other_|_other_|
__________|_other_|_other_|_other_|_other_|_other_|
|_{obj.id}_|_other_|_other_|
|_{obj.id}_| + - r w
|_{obj.id}_|
|_{obj.id}_| read / write view
|_{obj.id}_| of obj.d
|_{obj.id}_|
|_{obj.id}_| => implements CRUD
|_{obj.id}_|
|_{obj.id}_|
- 1 btc each to add 'calendar' and 'todo' modules.
#### related to un/bazaar
- 2 btc each to add 'tool' and 'recipe' modules (to CRUD Web Commerce
assets)
- http://payswarm.com/specs/source/web-commerce/
- http://www.heppnetz.de/ontologies/goodrelations/v1.html
- tool types that must be supported:
- 3d printer
- build volume
- resolution
- types of materials supported (white ABS, blue PLA, etc)
- cnc machine
- build volume
- resolution
- types of materials supported (douglas fir, aluminum, steel, etc)
- types of drills/routers supported
- laser cutter
- build area
- power wattage
- recipe types that must be supported:
- 3d design (for 3d printer or cnc machine)
- 2d design (for laser cutter)
- recipe generalized to use tools to transform materials into goods.
- circuit schematic
- 3 btc to add 'keys' module (to CRUD Web Keys)
- http://payswarm.com/specs/source/web-keys/
- 5 btc for integrating the above and completing an interface to CRUD
PaySwarm listings on un/bazaar
### medium-term future
- ? btc for un/wallet integrating Web Payments
- http://payswarm.com/specs/source/web-payments/
- ? un/bazaar using un/wallet for payments on listings
### long-term future
- implement a method of monetization roughly such that a minimal
percentage (~1%) of every transaction is sent to a transparent fund
operated by dinosaur to be used for sponsoring un/ development.
- implement Payment Intents (like Kickstarter, IndieGoGo)
- http://payswarm.com/specs/source/payment-intents/
Jan-Christoph Borchardt
Mar 30, 2013, 10:25:07 PM3/30/13
to Unhosted, Marco Stahl
Regarding unbazaar, do you know about http://sharedstuff.org ? It’s a platform to share stuff with others, made by Marco (cc'd). As an example, see my stuff at: http://sharedstuff.org/#/j...@5apps.com
Marco, is Shared Stuff updated to remoteStorage.js 0.7.1 by the way?Michiel B. de Jong
Mar 31, 2013, 2:25:56 AM3/31/13
to unho...@googlegroups.com
On 2013-03-31 01:47, dinosaur wrote:
> i agree that remoteStorage is awesome and we need to do something
> cool
> with it.
great, that makes you and your roommate a part of the unhosted
> i agree that remoteStorage is awesome and we need to do something
> cool
> with it.
movement! :)
> unbazaar requires creating, reading, updating, and deleting from many
> remoteStorage modules containing a variety of object types. this can
> be
> done with an open source framework that implements
> (CRUD)[https://en.wikipedia.org/wiki/Create,_read,_update_and_delete)
> on
> JSON-LD objects (http://json-ld.org). i think the easiest way to do
> this
> is to generalize an existing remoteStorage webapp.
part of Litewrite you want to generalize. :) Its documentation is here:
http://remotestorage.io/integrate/
Cheers,
Michiel
dinosaur
Mar 31, 2013, 3:43:40 AM3/31/13
to unho...@googlegroups.com
Jan: yeah, huge fan of SharedStuff, definitely a source of inspiration.
it got me excited about the unhosted movement when it released. not sure
why i haven't put my stuff up yet.
Michiel: remotestorage.js is great, but it doesn't have a ui, so when
anyone wants to make something unhosted that interfaces with users they
need to figure out how to integrate remoteStorage into an existing
framework or model/view library like backbone. this means every unhosted
app needs to make and maintain their own method of integrating
remoteStorage. i really like that Litewrite is composed of modular
libraries, as opposed to a framework that tries to do everything. by
generalizing Litewrite i mean use the same libraries as Litewrite
(remoteStorage, backbone, requirejs, etc) to make a generic ui layer,
almost an "unhosted app framework", on top of modules in
remotestorage.js. then hopefully maintaining an unhosted app would just
be maintaining the module and the module-specific ui, while we can all
maintain the common data layer (remotestorage.js) and the common
application layer ('un').
really appreciate the feedback,
Michael
it got me excited about the unhosted movement when it released. not sure
why i haven't put my stuff up yet.
Michiel: remotestorage.js is great, but it doesn't have a ui, so when
anyone wants to make something unhosted that interfaces with users they
need to figure out how to integrate remoteStorage into an existing
framework or model/view library like backbone. this means every unhosted
app needs to make and maintain their own method of integrating
remoteStorage. i really like that Litewrite is composed of modular
libraries, as opposed to a framework that tries to do everything. by
generalizing Litewrite i mean use the same libraries as Litewrite
(remoteStorage, backbone, requirejs, etc) to make a generic ui layer,
almost an "unhosted app framework", on top of modules in
remotestorage.js. then hopefully maintaining an unhosted app would just
be maintaining the module and the module-specific ui, while we can all
maintain the common data layer (remotestorage.js) and the common
application layer ('un').
really appreciate the feedback,
Michael
pir...@gmail.com
Mar 31, 2013, 7:30:44 AM3/31/13
to unho...@googlegroups.com
Maybe you are talking something about Dropbox javascript library? I find it really easy to integrate, specially the PopUp class...
Sent from my Android cell phone, please forgive the lack of format on the text, and my fat thumbs :-P
Sebastian Kippe
Mar 31, 2013, 2:01:27 PM3/31/13
to unho...@googlegroups.com
> Michiel: remotestorage.js is great, but it doesn't have a ui, so when
> anyone wants to make something unhosted that interfaces with users they
> need to figure out how to integrate remoteStorage into an existing
> framework or model/view library like backbone. this means every unhosted
> app needs to make and maintain their own method of integrating
> remoteStorage.
remoteStorage.js gives you the connect widget and public methods that you can use from your framework of choice.
> anyone wants to make something unhosted that interfaces with users they
> need to figure out how to integrate remoteStorage into an existing
> framework or model/view library like backbone. this means every unhosted
> app needs to make and maintain their own method of integrating
> remoteStorage.
galfert and I are currently developing an Ember Data adapter with it e.g.. Albeit people here suggested otherwise before, remoteStorage.js works suprisingly well as just a storage API lib, that you can build upon.
We're almost at the point, where we can release the code (which will be most likely tomorrow). Maybe you can draw some inspiration for writing a Backbone sync adapter or similar.
Cheers,
Basti
Marco Stahl
Apr 1, 2013, 12:30:19 AM4/1/13
to Jan-Christoph Borchardt, unhosted
I'm still traveling without computer until 16. April. When I 'm back I will start to update first my time tracker and after that shared stuff.
dinosaur
May 27, 2013, 8:14:36 PM5/27/13
to unho...@googlegroups.com
On 03/30/2013 04:41 PM, dinosaur wrote:
> hi,
have time to work and old bounties were no longer up-to-date with
current unbazaar plans.
new bounty, because why not:
1 BTC - write and test JugglingDB (https://github.com/1602/jugglingdb)
adapter for remoteStorage
cheers!
Michael
> hi,
>
> i think this project would be best done by the community for the
> community, so i'm offering bitcoin bounties for completing work on the
> road to un/bazaar. this summer my roommate and i will have at least 3
> months to devote to un/bazaar, but in the meantime we could really use
> some help.
>
previous unbazaar bounties are now expired, as i'm done with school so
> i think this project would be best done by the community for the
> community, so i'm offering bitcoin bounties for completing work on the
> road to un/bazaar. this summer my roommate and i will have at least 3
> months to devote to un/bazaar, but in the meantime we could really use
> some help.
>
have time to work and old bounties were no longer up-to-date with
current unbazaar plans.
new bounty, because why not:
1 BTC - write and test JugglingDB (https://github.com/1602/jugglingdb)
adapter for remoteStorage
cheers!
Michael
Reply all
Reply to author
Forward
0 new messages