Could not find this listed already. Is it possible for Sick to pick a random article when it is submitting instead of just the one you have filled out in the Article Creator field.

Have Sick randomly choose one of the articles you have posted in \Sick Marketing\articles for Sick 3 or \Submitter4\articles for Sick 4.

Instead of just using the article that's in the Article Creator field.

Vote if you like this idea! Think how much time you could save not having to open or create a new article for posting. Have Sick randomly pick them instead. I would find this very useful.

Could you please include the functionality within your software that would enable the auto posting of a single (or x number of posts) to each forum...

You could code the app, after confirmation of links, to access the private message/notification area, mark the message as read, then auto post an intro to the newbiesintro section, general section, oldest post section etc... before dropping a backlink?

As to the topic one could post on any of these forums, you could use the $keyword attribute for general comments such as "{noob here, good to be here at $keyword forum|I'm new to this forum, but not to $keyword}" etc... (spinnable the better)!

This could make your software highly desirable and very unique, and maybe even used for white hat methods, thereby almost guaranteeing all links to stick!

If SIC coding allowed template builders to do live queries of the SQL database, the template codes could automatically pull links and build out Tiered link pyramids automatically (similar to the profile "automatic link wheel function", but would allow for much more creativity. The live data query could then be used to populate data in the current run.

Example 1 - Massive interlinked blog network

Using one of the blog style posters (ELGG, Bogex, Wordpress, etc.), as posting is done links from previous runs, and current runs could be automatically inserted into the content. I could set the template content posting step to run on loop 10 times, and with every post, the query would pull up links from the previous posts and allow me to insert into the post content automatically, building a massively interlinked blog network.

Example 2 - Tiered Linking(Pyramid)
Templates could be programmed to automatically build link pyramids. For example, I might setup a project as follows (all setup at once with one "run" to accomplish)
- (TIER 1) 10 articles are submitted to high PR auto-approve article sites (auto-approve so links are captured and output to database)

- (TIER2) after high PR articles is complete, 500 ELGG blog submissions run next, querying database automatically inserting links from TIER1 into blog content built

- (TIER3) 1,000 SMF Profiles start, querying database automatically inserting links from TIER2 into profile

- (TIER4) 5,000 Guestbook template starts, querying database automatically inserting links from TIER3 into guestbooks

Of course, these are just examples I'm thinking of. I think with this functionality (combined with scheduler), SIC template programmers could get very creativity and unlock A LOT of value for users.

NOTE - I think for this to function optimally (and increase creativity), the link database would require two additional user defined fields (custom1/custom2). In my examples above, Custom1 would define "project-name", to allow database queries to be done by project name (thus links from across multiple VARS could be pulled), Custom2 I would define "link type" (bookmarks/blog-postings/profiles/etc) - (thus I could query by "project-name" AND "link-type" for appropriate tiered linking for each project).

Of course leaving them user defined variable would allow for some creativity in how the data is initially stored for future pulls.