What is DDIMario about?

DDIMario is a community-driven application for users to “get stuff done”. It is especially useful when a user wants to get comments on articles, comments/claps/follow/sharing of social postings, etc.

How does it help content creators?

Users (content creators) can create tasks (such as requesting comments on articles/websites/social postings) by spending DDINs (our application token, see below) and earn DDINs by completing tasks for others. What is special about it is that tasks usually need to be done thoughtfully by humans.

Content creators usually don’t have that luxury if they start out with a brand new website, new social media account, etc., unless they spend a massive amount on paid campaigns (and the results aren’t guaranteed) or they get a good amount of organic traffic from the search engine (none of those is available for anyone starting out on the internet with a small budget).

DDIMario solves this issue by creating a help-each-other network for high-quality content creators.

Tasks that are completed will be vetted by the task creator, who will then vote accept/reject and provide rating/review for the quality of task done by the task completer, for those specific categories of the task. For a completed task that is declined by the task creator due to its low quality, the task completer won’t be getting any DDINs, and the task will be made available to other task completers again. This way we have introduced a degree of accountability into the system, which will form the basis of reputations for users in all task type/expertise categories.

Creating tasks 1 at a time seems time-consuming. Is there a way we can speed things up?

Yes, there is a feature you will love. It is called “multiple task entries”.

For each task associated with a given URL (such as an article URL), you can check the box “Multiple task entries” shown in the video below.

It will allow multiple task completers to complete the task (for your review) and they will all earn DDINs if you approve their work.

The number of “slots” available for each task you can create will be limited to the number of DDINs you have in your DDIN wallet.

A great application will be to have your newly written article available for 5–10 task completers to write comments on. High-quality comments then drip-feed onto your article/social posting. It is designed to be a set-and-forget system for content creators. You can’t achieve that by spending a few hundreds on Facebook or Google ad campaigns.

How does it help income earners?

For those users who would like to earn DDIN incomes (which can be turned into USD, based on our current set of payout rules), you can do so by:

• completing tasks for other users;
• referring more users to DDIMario using your referral links;
• improving your good standing/reputation in the system and increasing USP (User-Selling-Price) of DDINs from your account (see rules above); Users with good reputations will see their USP going up from 0.3 to a max value of 0.7, for now.
• Signing up as a Power Mario user — you can then get instant email notification of tasks that are created in the system;

What is DDIN? How do I get it?

DDIN is the application token used in increasingly number of DDI applications. It will first be used at DDIMario, then it will become a crypto token which is tradable with other major cryptocurrencies.

Before DDIN becomes crypto, it can be exchanged back to USD according to our temp set of rules. Because of its experimental nature, the rules will be changed over time with the goal of promoting the overall usage of the applications (i.e. the change will always be in the interest of our members).

You don’t have to buy DDINs to use DDINs.

You can get DDINs by:

• signing up a new DDIMario account — each new account comes with 10 DDINs which you can use immediately after account approval;
• earning DDINs by completing tasks (see “task completion cycle” below);
• buying DDINs here (only if you can’t wait because you have a lot of tasks to create)

Any guidelines about the quality of tasks completed by a user?

Ask yourself, will you accept a lame comment on your article? such as “Thank you for the great article!”

Of course not.

Task creator spends real monetary resources (in DDINs) to create tasks. and those DDINs are put on hold with the system until the task creator clicks “approve”.

The quality of the task (such as quality of comment) should be at least adding value to the article by raising intellectual engagement level within the article/posting, and is perceived as thoughtful and helpful for the public. Yes, we take it personally because it is exactly the point of our building DDIMario, so that bot comments and spammers don’t have a place at all.

So if you are a task completer and you put in a lame comment as a completed task, you’ll need to expect rejection and earn 0 for that.

Any special guidelines for task creators?

When a user creates a task, it will be available for task completers to complete. The completed task will then be sent to the task creator for approval/rejection.

Therefore, the task creator’s job is not over UNTIL he/she approves the completed task sent over through email notification.

For the system to work well, task creators should respond to email notifications when the completed tasks require their approval/rejection decisions. 

What is a task creation cycle?

When we say a user is required to complete a task creation cycle, it means all of the following for 1 task:

• Create a task;
• Wait for the time it takes to receive email notification for the completed task;
• Make the Accept/Decline decision by clicking on the respective button;
• if task is reasonably well done and the user hits “Accept”

All of the above associated with 1 task represents 1 task creation cycle.

What is a task completion cycle?

When we say a user is required to complete a task completion cycle, it means all of the following for 1 task:

• Complete a task;
• Wait for the time it takes for the completed task to be accepted by task creator;
• If task creator declines the task done, the cycle breaks and task completion cycle will not happen (task completer will need to choose another task to complete and start over);
• If task creator accepts the task done, then the task completion cycle is “completed”;

All of the above associated with 1 task represents 1 task completion cycle.