WF Blog Farm?
- Thread starter Sharksfan
- Start date
Also, I am going to make these two ground rules - open to discussion from mods:
1.) If you are banned from WF you are banned from the Blog Farm. I MAY make this web-enabled so one or two select others could help administer it. That is very easy for me to do.
2.) N00bs need not apply.
1.) If you are banned from WF you are banned from the Blog Farm. I MAY make this web-enabled so one or two select others could help administer it. That is very easy for me to do.
2.) N00bs need not apply.
What's your plan for the automatic link wheel part? Do you mean a traditional web 2.0 spoke type linkwheel or actually using the member blogs as the different spokes?
If you're going traditional, I might be able to contribute something to the project. Working on a hosted automated system for that...
If you're going traditional, I might be able to contribute something to the project. Working on a hosted automated system for that...
How would this be related/beneficial to WickedFire though?
Its an interesting project, but along with most of the projects we've seen here, they become just too much work and time consuming with little or no financial payoff.
People have suggested creating a wiki division for the site, and now that we'll be moving to a hosting provider that can support our growth projections and won't cave to nasty emails or C&D's, its becoming a more viable option, especially with the implementation of a management and support team.
WF already has a pretty high trust authority within the SERPs, and although it fluctuates from time to time, the fact that we've done it without a blog farm may have something to do with it, which is why we've never taken on the project from the beginning.
Just trying to gauge what your goal is here, and if its worth pursuing or not, for everyone.
Its an interesting project, but along with most of the projects we've seen here, they become just too much work and time consuming with little or no financial payoff.
People have suggested creating a wiki division for the site, and now that we'll be moving to a hosting provider that can support our growth projections and won't cave to nasty emails or C&D's, its becoming a more viable option, especially with the implementation of a management and support team.
WF already has a pretty high trust authority within the SERPs, and although it fluctuates from time to time, the fact that we've done it without a blog farm may have something to do with it, which is why we've never taken on the project from the beginning.
Just trying to gauge what your goal is here, and if its worth pursuing or not, for everyone.
Before I say anything else - I'm happy to see WickedFire growing - if you ever need any help/assistance/whatever with setting up support systems let me know. I have a LOT of experience in that area.
As far as benefitting WF directly - there is none. It would be more accurate it to say it's a non-official blog farm for WF members to use to promote offers and essentially get some link juice off of select unique IP's.
There are a number of people doing this already of course. I think there's one called Free Traffic System. The FirePow people also have one - and there are others I've seen. The problem with those is they are spammed heavily. I looked into this once a while back when I first started doing AM and I think the concept is sound as long as you can get a number of unique IP's and limit the amount of crap (ie, dupe content) that is pushed out there.
There are about a million ways this could be implemented. I'm in favor of doing it as simple as possible to start with just to get a proof of concept going.
And if for some reason this is thought to be detrimental to WF - let me know.
Just sent you a PM about all of the above. Also, the work-flow looks simple enough, I guess just limitations on # of articles posted & niches covered would be the only real ground rules needed. You'd need to log each email as it comes in so we can boot members that break the rules.
I might also suggest that each person brings something like 5 IPs & domains to the table ... if we're going to do this, lets do it right. 20 people sharing 20 domains is much less appealing than sharing 100 domains. It also allows us to consider theming domains and articles tightly instead of just being random. Something like 10 categories (electronics, entertainment, travel, ...) and then get people to mark what category the post should go in.
Something like:
email subject: finance||How the greatest American presidents killed the bank.
email body: words, words, words ... with some links
It also allows us to get into some riskier niches (porn, pharma, ...) without compromising the entire farm.
I've got the link structure part of that covered, it's something I've had in my arsenal for quite some time and it kicks ass.
I agree though, something that does a quick scrape to randomly check for unique sentences would be best to (loosely) verify for uniqueness in the content.
I might also suggest that each person brings something like 5 IPs & domains to the table ... if we're going to do this, lets do it right. 20 people sharing 20 domains is much less appealing than sharing 100 domains. It also allows us to consider theming domains and articles tightly instead of just being random. Something like 10 categories (electronics, entertainment, travel, ...) and then get people to mark what category the post should go in.
Something like:
email subject: finance||How the greatest American presidents killed the bank.
email body: words, words, words ... with some links
It also allows us to get into some riskier niches (porn, pharma, ...) without compromising the entire farm.
I've got the link structure part of that covered, it's something I've had in my arsenal for quite some time and it kicks ass.
I agree though, something that does a quick scrape to randomly check for unique sentences would be best to (loosely) verify for uniqueness in the content.
Actually - I can do this like this or a few other ways. The software I intend to use allows for templating in the body of the email in a similar fashion.
Wouldn't a simple webapp backend be way more efficient and consistent than trusting everyone to know the correct email formats for the different categories?
You could just have it setup to add and remove users, setup posting limits/category restrictions, and add categories and then blogs to those categories. Then, users can just login and post where and how much they are allowed to. Have the app accept the post, and then shoot out emails according to where it should go.
Just some thoughts...
Sure it would.
That said - at this point I'm working with the tools I have that actually already do this instead of the tools that I would like to have and would cost time, bug fixes, etc, to develop.
At this point though getting a proof of concept up and running is best I think. If it looks promising - then we go from there.
I speak from experience when I say that most projects die before they are born because people won't just move forward and try something.
That said - at this point I'm working with the tools I have that actually already do this instead of the tools that I would like to have and would cost time, bug fixes, etc, to develop.
At this point though getting a proof of concept up and running is best I think. If it looks promising - then we go from there.
I speak from experience when I say that most projects die before they are born because people won't just move forward and try something.
Keep it simple from the start or else it will never materialize.
Please let me know what you need from me when you need it.
Nope, I'd rather not have to write a custom script to log in and do all that stuff ... blasting off emails is sooooo much easier.
I believe I speak for most when I say, I have no intention of doing this manually. Set up the cron, load up the queue and the forget about it until next month ... outsourcing 100% of the content.