Skip to main content

PostBump™

PostBump™ is an idea for an app that would enable blog readers to incentivize blog authors by trading PostBump™s of free licensed blog posts they appreciate, for bitcoin.

This would give readers a new opportunity to strongly influence authors to make available more of the kind of content the readers like. This would also provide authors a direct way to earn bitcoin for their work in posting that kind of content. This idea aims to help vastly improve the quality of desirable content freely available to the general public.

The Link: A PostBump™ would consist of a little link contained in the actual blog post. The blog author would use the app to get the unique link for each new blog post. Then, the reader could follow the link to use the app to trade the PostBump™ for bitcoin.

Trading: Traders could buy and sell shares of the PostBump™, somewhat like stock in the stock market. The author would start out owning the shares, and the author would set the initial asking price. The first traders would buy original shares from the author.

Bitcoin: App users could use bitcoin to buy and sell shares.

Authenticity: Before allowing an author to offer shares for sale, the app would require the author to verify the PostBump™. To verify, the author would submit the URL where the content, including the PostBump™, was available. At this point, the app would verify the content included appropriate notice that it was licensed under the CC BY-SA license.

Other Ideas:
  • This app could start with blog posts then expand into other things (music, videos, software)
Note: PostBump™ is an MVP (Minimum Viable Product) for Dev Cloud, another idea on this site.

Comments

Popular posts from this blog

Shared Project Manifesto Version 2

Contents:IntroductionLaunchTradeRewardDevelopVoteHarvest 1. Introduction IP (Intellectual Property) is a great asset but it is hard to produce well. We hypothesize that a market to facilitate shared projects would make it easy to produce IP better.


The market contains projects. Each project has one admin and a number of traders and developers. One user can have any combination of roles at the same time. For example, a user may be an admin and also a trader, or a trader and also a developer. ProjectsUsersAdmin: Provides ideas in exchange for controlTraders: Provide incentives in exchange for growthDevelopers: Provide IP in exchange for incentives 2. Launch When somebody came up with an idea for an IP product, they could create a project for it on the market. That person would be the admin.
The market would record the time the admin launched the project. That lasting record could provide for the admin to claim credit for the project idea, on a first-come, first-served basis. This recogn…

Fog Machine

Fog Machine™ (named because fog is like a cloud, on the ground) is a software product to provide cloud services to customers without a cloud service provider. The problem with the traditional cloud is that it requires a provider. Fog Machine™ would run cloud "nodes" in idle system resources on ordinary user's devices. This would be a peer to peer system in which each connected device would be a peer.

It would support standard cloud APIs (perhaps Cloud Foundry?) and it would be easy to port cloud apps to it off providers such as Google cloud, Azure, or AWS--or maybe it would be effortless for apps that were already portable through compliance with open standards.

We might use encryption for privacy, redundancy for reliability, and remuneration/incentive for resource consistency. The showstopper (critical assumption) is that the synergy would be sufficient to significantly surpass the overhead, and provide competitive performance for at least some types of cloud applicat…

Nuke Login™

Nuke Login™ is a software product that would provide secure access to computer accounts without the user needing to worry about passwords or related concerns. Like other password manager products, Nuke Login™ would provide the ability to automatically login to many different accounts, but it wouldn't require a password to login to itself. Instead of replacing many passwords with one, it would replace many passwords with a different process.

Also, Nuke Login™ would not only manage the process of logging in. It would manage the whole login-related processes for the accounts, including registering, logging in, changing the security information, logging out, and closing accounts.

When a user was registering for a new account, if they only needed login credentials to register, Nuke Login would automatically generate those credentials and register them. If other things were needed, Nuke Login™ would take care of the login credentials and mask them in the registration process so the user…

Please Comment

Have you ever heard of a similar idea? What challenges might an idea run into? How might you like to be involved? Comment to add your voice to each idea.