Use Case Scenario

There are two main types of user: Senders and Recipients, though I think Senders will require the same features as recipients… posting and fund withdrawal permissions will differ.

Currently provided by WordPress:

  • Easy to use wysiwyg editor
  • embed videos from Odysee and other non-scummy video sites.
  • Non-spying social links – only for users to post article links to their social accounts.
  • Blogs and pages for recipients, along with categories and tags they can use.
  • Roles system to allow access to certain features
  • Membership sign in, and registration system

Provided by BuddyBoss and BuddyX theme:

  • Member Profiles
  • Groups – for different topics and projects.
  • Direct Messaging
  • Activity Streaming
  • Notification System
  • Forums – no need for comments if the comment section of an article leads to a forum post of that article. As in MacDailyNews (at least a few years back).
  • Gamification – i.e. levels and achievements.

The above features are all provided by the BuddyBoss plug-in which is well-maintained. BuddyBoss is a fork of BuddyPress which is full-featured but looks bad out of the box. I tried a few different ways using BuddyPress (Youzify and its dependent theme and plug-ins) but ended up too bloated with plug-ins making the site almost unusable. BuddyBoss also includes a fork of BBPress to provide the forums.

Other Features

Website Tools

  • Mining page
  • Surveys section (so we get all the revenue instead of sending users to other sites).
  • PTC section (once we have enough traffic)


  • .A method to show the accounts for each project in a page for that project’s accounts.
  • An interface for the project owner to enter expenses and attach receipts etc.
  • Access the data from the wallets plug-in to automatically show when a user sends funds.

Access Restrictions

Ability to restrict pages or areas of content to specified user roles. Members plug-in (among others) provides this but we are not using it because we only need one small part of that it does.

Project Verification System

This could be something like the Web Of Trust system used to verify PGP signatures. For example, I have had independent verification of Evans’ project in Kenya by a friend from here in Ireland who visited the site and verified all he has said. Further, we had a long-time friend who is a Professor (now retired) at Nairobi University visit the site too.

Further, the project is part of the PRI (Permaculture Research Institute of Australia). It’s all down to whom you trust of course. This will need some brainstorming… But we don’t need it until after we open source the whole thing so it’s not urgent.


  • The site will not bleed data to google, facebook etc. Fonts and everything else are stored locally.
  • We don’t need to know who any sender is, only the recipients need to have a real identity.
  • Sender only needs a username and email address.
  • Recipient real identity is not public unless they want it to be. Only senders of funds can have access to it.