1. The main idea
The main idea is to create a plugin that tracks what you read and watch whenever there is a Redd-ID tagged in the content.
The plugin will then look up whether this particular content belongs to a source that has been registered as public proof of a social network identity. An example is down at the bottom.
The plugin documents how much quality time has spent on which ReddID to a database. Users can chose whether they want to share the data or not.
The users can also define how much they assume to spend on content creation (e.g. 20$/month)
After a period that can be set by the user the plugin will inform you about what you read and will ask you to tip the money to the creators. If you prefer not to do it manually, the plugin will do it automatically for you and document it in a tipping history.
If the plugin is connected to the global database, the ammount of the tip will be registered as money flow + a “favourite” is saved for the domain + a favourite is saved for the particular content.
**So as a short tl/dr: what the plugin effectively does is identifying the content that you consume and sum it up for you, so at the end of a certain period (e.g. a month) the content creators are effectively paid by the consumer. **
Why is that important?
There is a gap that is not yet filled for millions of content generators. Many content generators are not paid by their readers/watchers/fans but by the attention that they receive from them which is eventually monetized by commercial ads. We know from several studies that there is huge interest that creators on the web are independent and there is also interest to pay them for what they are doing, but there are only few solutions that effectively allow to do that. Patreon and Flattr are the one who are currently dominating the market but with both users pay money for providing a money transfer system. Cryptocurrencies can do without and it´s much more transparent.
2. The Tools
The plugin generates data that can provide another added value: by documenting who receives tips a semantic network is created that shows who likes what. This can be shown as co-occurence and used as a browser for other interesting content. I created a sketch and will explain how it could work:
(1) Each Redd-ID is shown as red dot. The size of the dot shows the ammount of tips or the ammount of likes (see ). The position shows the relation between the content. So if you tipped page A and page B then in the browser they will appear closer to each other.
(2) If you click on a dot, it will show the ID and a preview of the page. By clicking on the page the page is opened (see )
(3) You can chose how to look at the “map” by using different perspectives. The first (from left to right) visualizes how many and in which relation RDD have been spent. The second visualizes how often and in which relation the page was “favourited” . The third shows how much and in which relation quality time has been spent on the content.
There is also a search bar that allows to add search terms. These allows the user to focus on a particular sector of the network. Tags can be removed by clicking on the X.
(4) A zoom field allows to explore the content if the space becomes too filled to browse.
(5) The sidebar shows the values for each visualizations, here how many RDD have been spent. The sidebar can be fold down to have more browsing space (especially on mobile devices)
(6) Is the blank logo space (I have a cool idea for a product name, but I won´t reveal for now)
(7) Whenever a dot is clicked the page can be fold up by clicking on this arrow. This would look like that:
(8) by clicking on the arrow section the user may re-enter the co-occurence browser.
*If someone enters https://www.youtube.com/watch?v=KlYJ0sNVVpg & there is a ReddID tagged anywhere on the page, the plugin will lookup whether that ID owns the channel (https://www.youtube.com/channel/UCh6LrEE_hX1eKgdQUngqVFw) and if it does it will count the time that a person spends on this page.
There needs to a time-out, obviously, because if you leave the computer with the browser open that shouldn´t be counted. For texts this is easy to do: the plugin will count how much text the page shows and estimate how much time a reader would need on avarage to finish reading. After this time the counter stops unless the user scrolls up or down. In this case the counter is resetted. For videos this is probably more complicated because it would need to extract the time from the video, so probably the code needs to be adjusted for each platform.)*