Another question here...

would you like to force submitters to sign up for a submit account (even if it was instant) for public submits? It would certainly cut down on the number of blind autosubmits, since each submitter would have to take the time to register...also, it would allow better backend tracking of each submitter. Opinions?

I actually was going to post about that a couple days ago....admin option to select between open submit/the image verification thingy/or sign-up before submitting

Well, with submitter registration I could allow submitters to log in, see the status of their submits (no more "was this reviewed yet" emails), see how many of their sites are currently listed (no more "was this site listed" emails), avoid email address on the submit form altogether, allow submitters to edit their email address, allow better mass mailing to all submitters, do a better job of checking for multisubmitters, and a shitload of other things.

I could even allow submitters to see rejection reasons back to their first submit.

I'm just wondering how many LL owners would be turned off or on by this feature :)

My opinion on this is simple: No matter what "security" features you create, some programmer with more time on their hands will develop a way to spoof the system. The more complicated the system, the more complete the spoof. I have heard about companies hiring out workers in third world contries to type "human check" boxes and such... so what can you do?

Dishonest people will try their damndest to get around your systems. It's just a fact of life.

Alex

Oh, it wouldn't be any kind of "fool proof" security measure :) It would, though, be a great tool to add more robust backend features with. :)

Beta Testers, you have PMs :)

I'd like a blacklist to be more extensive. Say add submitters email, IP, domain, maybe adding dns server and email host?

I have to say one thing here...I am not a fan of shared blacklists.

I can of course see the benefits of them, but I feel they are harsh.

As far as I know I have only once been put on a blacklist in over 2 yrs, and Greenie was the one who put me there :)

It was way back in 2003 when I was just learning the tgp game, and somewheres Link-O-Rama was on a list to submit galleries to.

So I submited a gallery to him, and was banned. Was a totally innocent error on my part, and Greenie cleared me immediately when I asked.

Problem is link list owners are very divergent in what they do not like or will not accept....and ban for in fact.

And I fear with a shared list some may be trigger happy. I've seen it second hand in the useful scripts one here on the boards. Someone gets banned for something that is acceptable and listable at others that use the list, but cannot because of the script submit to anyone. The scripts no matter how well coded are basically stupid. They do not say well this poster was banned for I'm concerned about his ip...or he submitted the same template two times in 4 days...they say BANNED...and the link list scripts that subscribe automatically throw his submissions in the dumpster for occasionally weeks on end until the appeal is resolved. Then it is found out there was a mistake in some cases but the submitter lost weeks of business.

No I do not like black list scripts, GG telling Cleo this guy sucks ...yes....auto by script with little recourse no.

I agree Meat Pounder. I have posted in this thread or another this very thing. My suggestion is to have a more detailed blacklist seperated by categories so that you can choose which set of blacklist categories you want to use instead of just one general list.

And that's what I'm working on ;)

Blacklist will include submitter's email, IP, domain and domain IP (with choices at the blacklist interface on how much of this info to add...I used to ban domain IPs then one day I unknowingly blacklisted one of Fonz's freesite domains...which is when I said "enough is enough" on that, lol). Email host is a possibility, dns server is something a little bit trickier because of the necessary script access of the whois database to accomplish this so that's a bit of Kung Fu that the jury's still out on.

I really should change hosts, seems like a lot of cheating bastards are hosted on that same IP. Even the host my LL is on blocked that IP so I can't submit to my own LL through the regular submit form :)

BTW. I really think MadMax's script is gonna beat every other excisting script |thumb

ROFLMAO

Shared blacklist can be "toss out" or "advisory". I personally like to know when someone else has been fucked over. We are not talking blacklisting because someone didn't like the color of their links, but rather someone pulled content, return links, redirected traffic, or did something else to fuck the surfers over.

If you work only by yourself without this type of input, you have to make the same mistake that hundreds of other links sites make. If you have some good communication, you can avoid the problem and perhaps help others to avoid similar problems in the future.

It all depends on how you look at things.

Alex

Right now I'm looking into making it optionally prevent submission or just throw up a flag, configurable by the user. The added complexity of allowing some users to access only certain sections of the shared BL database for themselves is the biggest issue, since I need to have an architecture that supports an unlimited number of sites accessing the shared BL. I'll get there...the biggest issue is finding the BEST way to do it :).

One of the biggest turn-ons for me with the idea of a shared BL is the number of times I've blacklisted someone for being a serious cheater, posted about it here and had several other webmasters tell me they had the loser on their BL a year ago ;)

I would really like that feature... I always review at a time different from when I want it to update.
Sigh.. can't believe I missed this earlier, I wanted to be a beta tester (even tho' I don't think I have enough posts |snail )

How about more involved submit limiting...

Beyond how many sites a submitter could submit daily, you could have an option to set limits per category.

For instance, if you were getting a large number of "teen" submits per day and this was throwing off the balance of your LL or causing a logjam, you could set a limit as to how many "teen" sites the script would accept daily before telling the submitter to try again tomorrow.

BTW, I kinda like your idea about the registration thingy. I think it would also be very useful for submitters to have access to some kind of account interface where all their submit info was available. You could add all kinds of cool features.

Good luck with the script Max, and please feel free to let me know when it's ready. I'm thinking to start a LL in the somewhat near future and will be looking for a script.

Regards,
SF

One feature I like in a submittal form is multiple categories.

Blonde, Oral, Interracial maybe for something like a Blacks on Blonds site

And a search feature within the link lists archives with an input for several keywords on the submit form.

Hell I gets as much traffic from penisbots search as I do from the initial listing :)

Max, I have been keeping up with your progress here. Seems like you are heading in the right direction for a good product.

I hope you do not consider my posting here as whoring in your thread.

As you know, it is my belief that host free sites will be widely used in the future for the same reason that TGP's jumped on the free hosted galleries craze. Therefore, I would consider admin controls to deal with hfs' separate from submitted sites. Some of the things you will want to consider:

1. Entering several hundreds or thousands of sites into a database is boring and very time consuming. Therefore, you should have the ability to mass import sites via a delimited text file. (Stay away for insert statements as I don't think average WM will be able to handle that)
2. Most often the import would cause the sites for each sponsor lumped together. Since most db apps will pull the sites from the table in the order they were enter, you will want the ability to randomize your hfs database.
3. You should have the ability to tell the script how many hfs' to include each day and define the algorithm to be used to pull the sites from the database. I would also include a scheduling feature to allow one to specify when a site becomes eligible for display.
4. Click tracking has been mentioned. Consider adding a field for sponsor names in your db so you can track sponsor clicks. Increase productivity should be increased by knowing which sites, categories and sponsors are the most poplar with the surfers.
5. It is natural for me to think it is cool to be able to go to one site and get links for most available hfs'. How cool would it be to have your script poll such a site for new hfs' and have them imported into the script owners' hfs database? This could be done with a cron job or manually. Or perhaps go the other way and have HFS resource send an RSS update as new sites are added to its database.

One final thought. I would not limit this to a Link List script. IMO, there is a trend to do hybrid sites. This should not increase scripting too much but the templating system would be a little more complicated to handle thumbnails. You will also need a field in the database for type - FS, TGP, MGP.

That can certainly be done :)



My thoughts exactly :)

Thanks smutferrit, I'll be sure to :)

There will definitely be a search feature. In Admin you will have the option to put a site in as many categories as you like...one of the things I love about the current script. :)

I'd never consider you to be whoring bud ;)

You bring up a bunch of excellent points, and I thank you for taking the time.

1. Bulk import is a must have. I'm heading for something similar in functionality to the one on AGS, allowing comma or pipe delimited text to be imported. I like the interface in AGS for the most part, so the style will be the same.

2 & 3 This will only become an issue if the sites are being displayed by date and not alphabetically in one or more different formats. There will be a function to put a site's "approved date" into the future, and it won't display until after that date. I could probably work something in the mass import to apply sequential dates as it's importing the sites if the option is checked, and since HFS should always be reviewed there will be another option to change the display date. Let me know how feasible this sounds to ya.

4. Sponsors will have their own section of script Admin, including the ability to put all links from a sponsor (or from a given submitter) on "hold" status and keep them from being displayed (or the ability to bulk delete all the links from a sponsor or submitter at once instead of requiring a search beforehand. If I implement the click tracking in version one, I'll certianly be able to track clicks to a given sponsor. The Admin interface will be full of statistics options. One benefit of being a stats junkie myself :D

5. I would CERTAINLY like to discuss this more, and for obvious reasons you'd be the man to talk to :D

Also, the user creates their own "site types" with this script, so they will be able to create as many different ones as they like. Tumbnail management won't likely make it into the first version since there's so much else that needs to be done, but this script will continually evolve.

Thanks as always for all your advice :)

Alright everyone, thanks a million for all the input so far, it's been tremendously helpful and I'm glad so many took an interest in giving their opinions :)

I think I need to put the project back into "skunkworks" mode at this point, so I don't give away all my secrets or features too quickly...never know when the competition's watching :D

I'd love to get any and all suggestions in PMs or emails though :)

Thanks again, you guys are awesome |thumb

DEAR SIR:

I click in your signature link: http://www.fetishphiles.net/freesites.shtml, and after it I click in the Preview that are inside of tables by category, BUT except the Teen category, other give me 404 error message. For example:
Not Found. The requested URL /3d-porn/3d-strap-on-fuck/anime-lesbian-strap-on-fuck.html was not found on this server.
Best regards,

TALLEYRAND