Permanently Closed Marketplace Sales Thread

Status
Not open for further replies.
You couldn't have Cpannel or some other site hosted email system on a domain you own integrated and just spit out unlimited email accounts? Not any of the "big" email providers. I think you will probably even get better registration rates by not using some major name.

We have considered this but it's not a long term solution. The problem here is that we'd probably get banned pretty fast because of the large amount of incoming emails (we've already experienced this with Hostgator). Let's say we have 100 users and each of them does 1 WikiBase run per day which generates about 2000 emails. That equals to 200.000 emails per day.

Right now we're looking at creating Yahoo email accounts and that looks quite promising, much easier than Hotmail.
 
We have considered this but it's not a long term solution. The problem here is that we'd probably get banned pretty fast because of the large amount of incoming emails (we've already experienced this with Hostgator). Let's say we have 100 users and each of them does 1 WikiBase run per day which generates about 2000 emails. That equals to 200.000 emails per day.

Right now we're looking at creating Yahoo email accounts and that looks quite promising, much easier than Hotmail.

Sounds good :)

Regarding the CPU thing, I just thought it would be less intensive to separate the tasks than running submission and spinning at the same time. Perhaps resources could be allocated better.... but that stuff is beyond me anyway. It was just a thought. Thanks :)
 
Sounds good :)

Regarding the CPU thing, I just thought it would be less intensive to separate the tasks than running submission and spinning at the same time. Perhaps resources could be allocated better.... but that stuff is beyond me anyway. It was just a thought. Thanks :)

Thanks for the thoughts. It probably wouldn't make too much of the difference. We are collaborating with SpinRewriter team on making our spinning algorithm even better (if there's anything to do anyway, since it's already pretty efficient) since that's their area of expertise.
 
An update has been released - WikiRobot 1.0.4:

  • added ability to load articles from directory
  • added ability to load articles from url on the fly by using #url[http://www.link.com] in content title and body
  • fixed scheduler start button getting disabled in some cases
  • fixed filters not working correctly when filtering by specific platforms
  • fixed unrecoverable crash that happened with some complex sites
You can manually trigger the update process by going into Help / Check For Updates or by restarting WikiRobot.
 
Sweet update! :) Thanks for the "load articles from directory" option.
 
An update has been released - WikiRobot 1.0.5:

  • added estimated time remaining for actions
  • fixed some nasty sites never timing out
  • fixed new lines being treated improperly while posting to DokuWiki and WikkaWiki
  • fixed DeathByCaptcha dll which would crash WikiRobot if DBC was unreachable
You can manually trigger the update process by going into Help / Check For Updates or by restarting WikiRobot.
 
It would be very helpful to chain Captcha Solves to improve Success rate. So if 1 fails, it goes to the next, and the next... however many Solvers somebody has accounts and/or software for. Captcha Solving PRoviders freequently experince connection errors, or the operator types in a wrong response... this is a way of improving success rate. What do you think?
 
Also, any chance of possibly allowing the filters to also include/exclude posted content. That way we could export/copy and paste the posted links that have PR, that are ********, etc. Would be very handy to be able to show clients the quality of links they are receiving. Just a thought. Thanks....

Great product BTW, I'm putting it through the paces :)
 
A minor update has been released - WikiRobot 1.0.6:

  • fixed connection issues for DBC and GSA Captcha Breaker
You can manually trigger the update process by going into Help / Check For Updates or by restarting WikiRobot.

It would be very helpful to chain Captcha Solves to improve Success rate. So if 1 fails, it goes to the next, and the next... however many Solvers somebody has accounts and/or software for. Captcha Solving PRoviders freequently experince connection errors, or the operator types in a wrong response... this is a way of improving success rate. What do you think?

Yes, there have been many request for this functionality and I've passed it to our dev team. Thanks for the suggestion. :)

Also, any chance of possibly allowing the filters to also include/exclude posted content. That way we could export/copy and paste the posted links that have PR, that are ********, etc. Would be very handy to be able to show clients the quality of links they are receiving. Just a thought. Thanks....

Great product BTW, I'm putting it through the paces :)

So if I understand you correctly, all you want is that filters would be applied to "Export Links" function/button? E.g. you filter your posted sites in sites list list by PR > 3 and then export the links.

@everyone else: Thanks for all the new purchases!
 
So if I understand you correctly, all you want is that filters would be applied to "Export Links" function/button? E.g. you filter your posted sites in sites list list by PR > 3 and then export the links.

Yes Exactly. It could be just a "export filtered links" button where you set filters for say sites that have PR > 2 and are ********, and you export the links created on those site. That way you can show clients links of various quality, or in a certain order. Or alternatively, and maybe even better, Is it possible to export a .xls of the entire project? It looks nice, and gives the client what they need to see as far as platform diversity, PR, ******** etc.

Thanks for the great support :)
 
Yes Exactly. It could be just a "export filtered links" button where you set filters for say sites that have PR > 2 and are ********, and you export the links created on those site. That way you can show clients links of various quality, or in a certain order. Or alternatively, and maybe even better, Is it possible to export a .xls of the entire project? It looks nice, and gives the client what they need to see as far as platform diversity, PR, ******** etc.

Thanks for the great support :)

For the first part - you can expect it to be done tomorrow. As for the XLS -could you send me (or describe) the format of that XLS file? How exactly would it look and what data would be included?

Thanks.
 
For the first part - you can expect it to be done tomorrow. As for the XLS -could you send me (or describe) the format of that XLS file? How exactly would it look and what data would be included?

Thanks.

Easy.. all the data on the sites tab of wiki robot to just be exported to an Excel Spread sheet. After the run is done all the checkmarks next to weather or not the site was registered, weather the link was posted successfully, the PR of the site, the platform of the site.... All the data is already there, but itseems you can only export the url of the wiki? If you could just export the entire spredsheet with all the data included, that make for a much more impressive and comprehensive report IMO.
 
Anyway to submit using the same already registered email accounts? The accounts are there, multi posting to same account is allowed by all wiki platforms is it not? Seems like a big waste of time to register a new account for every submission. The post to all sites function seems to work, but is it not possible to resubmit to the sites where you have previously registered and only those sites?

Cheers.
 
Easy.. all the data on the sites tab of wiki robot to just be exported to an Excel Spread sheet. After the run is done all the checkmarks next to weather or not the site was registered, weather the link was posted successfully, the PR of the site, the platform of the site.... All the data is already there, but itseems you can only export the url of the wiki? If you could just export the entire spredsheet with all the data included, that make for a much more impressive and comprehensive report IMO.

Roger that! :)

Anyway to submit using the same already registered email accounts? The accounts are there, multi posting to same account is allowed by all wiki platforms is it not? Seems like a big waste of time to register a new account for every submission. The post to all sites function seems to work, but is it not possible to resubmit to the sites where you have previously registered and only those sites?

Cheers.

Of course you can reuse the same accounts for posting multiple articles. Just don't go berserk, since your accounts will have higher chance to get deleted. You can accomplish that in two ways:

1. You can select all the posted sites in a project, right click and reset "posted" status. You can then post in the same way as the first time (e.g. by using "Automatically determine postable sites") as all the "posted" statuses will be cleared and WikiRobot will treat the sites as if nothing was ever posted.

2. You can just select all the sites you wish to post to, right click and force posting by choosing "Post To Selected Sites". By doing this WikiRobot ignores current "post" status of sites and posts again no matter what.
 
i am getting an error database.sdf not present....

There can be various reasons for that (e.g. you are using Windows XP < SP3, you don't have sufficient permissions, etc.). Please send us log.txt file located in your WikiRobot installation folder (usually C:\Program Files\WikiRobot\) to see what's going on.
 
An update has been released - WikiRobot 1.0.7:

  • added imagetyperz support
  • filters are now applied when exporting posted / verified links
  • fixed POP3 disconnect crash bug (when confirming mails)
You can manually trigger the update process by going into Help / Check For Updates or by restarting WikiRobot.

i have windows 7 pro running on i5

OK, we can rule OS issue out then. Still waiting for that log.txt - PM me or send it to [email protected], else we can't help you.
 
Status
Not open for further replies.
Back
Top