Imagine a coffee shop with a lanimated gif printer, a near-future device that prints out an animated gif, each frame individually lainated, and bound together in a flipbook.
What follows is an account of how Other Chat might let the shop sell access to the lanimated gif printer.
You navigate to #coffeeshop, the shop's domain channel (perhaps advertised via BLE in #nearby by the iPad register)
In the coffee shop's pocket you find the link to #coffeeshop/lanimate and navigate
You scroll to the printer's pocket and find laid out a description of how to use it, and a little shop of tokens for making [1], [2], and [5] lanimated gifs. You'd like to scroll further but there is a wall blocking your way because you don't have any tokens.
You tap [1] which prompts you if you want to purchase. Transacting UX always happens in the chrome of the user agent for security and the user agent may store (locally?) your credit card info.
You purchase an [unused lanimated gif token], which you put in your pocket.
You now scroll past the wall to a /widget that lets you paste in a gif, which (after confirmation) prints out the gif on the lanimated gif printer and changes your token to a [used lanimated gif token], and logs the transaction in the token's read-only pocket, turning the token into a kind of a receipts.
In general—and behaviorally-skeuomorphicly— /walls can be used as paywalls. I can imagine most news sites putting sets of articles behind /walls that require some form of subscription token to get past. The NYTimes etc already do this.
Now, imagine that you make a channel you'd like sell a modest subscription to: a blog/newsletter model. To do so you might:
Nav #:other.xyz/apps (maybe default installed in side-nav nicknamed to something), search for 'subscription store'.
You find one you like so you select the store widget's and copy it it.
You navigate to the channel you want to install it on, and paste it into the pocket.
You long hold on the store widget and select 'edit'
That navigates you to the store's channel, which is accessible only by the owners/mods of the channel.
In the channel's pocket (perhaps it's a pocket-only channel) are the instructions, settings, and wall.
You copy-paste a subscription type you want's token, to the store's "products you are selling" section.
You long hold the token, select edit, and customize name, price, and display image (via the /text-input, /price-input, /image-input widgets in the token's pocket).
Press back to return to the store's pocket. Find the store's /wall and copy-paste it at the appropriate places in your channel.
After setting up your deposit info back in the store's pocket, the store front becomes live in your pocket.
Woo!
All the objects here are view-source-fork, and the same base store works for independent authors and part-time bloggers to the major news sites like the NYTimes to other kinds of things, like bands giving access to their music. Much cheese.
Copied from original issue: other-xyz/time-cone#95
From @aza on August 29, 2016 5:16
Imagine a coffee shop with a lanimated gif printer, a near-future device that prints out an animated gif, each frame individually lainated, and bound together in a flipbook.
What follows is an account of how Other Chat might let the shop sell access to the lanimated gif printer.
[1],[2], and[5]lanimated gifs. You'd like to scroll further but there is a wall blocking your way because you don't have any tokens.[1]which prompts you if you want to purchase. Transacting UX always happens in the chrome of the user agent for security and the user agent may store (locally?) your credit card info.[unused lanimated gif token], which you put in your pocket./widgetthat lets you paste in a gif, which (after confirmation) prints out the gif on the lanimated gif printer and changes your token to a[used lanimated gif token], and logs the transaction in the token's read-only pocket, turning the token into a kind of a receipts.In general—and behaviorally-skeuomorphicly—
/walls can be used as paywalls. I can imagine most news sites putting sets of articles behind/walls that require some form of subscription token to get past. The NYTimes etc already do this.Now, imagine that you make a channel you'd like sell a modest subscription to: a blog/newsletter model. To do so you might:
/text-input,/price-input,/image-inputwidgets in the token's pocket)./walland copy-paste it at the appropriate places in your channel.All the objects here are view-source-fork, and the same base store works for independent authors and part-time bloggers to the major news sites like the NYTimes to other kinds of things, like bands giving access to their music. Much cheese.
Copied from original issue: other-xyz/time-cone#95