Post Critiques [library support]

[Wormopolis]

Well I went with the concept of companion plugins, because lets say someone wanted the opposite. they wanted just the smaller function of the a plugin without the need of tracking individual users. instead of making a single plugin that HAS to use 2 keys, I make 2 plugins where the main plugin does most the work and doesnt cost the super key.

Look at it from the coder's side as well when it comes to the time where we can start charging for plugins. someof these codes are in the thousands of lines. Peter's money plugin is nearly 3000 lines. for free. if Peter instead charged $1.00 for that plugin, would you still get it? I bet a lot of forums would go ahead and invest the $1 to be able to use that plugin. by now, there has to be at least 500 forums that are using that plugin. thats $500 Peter could have earned. money which inspires him to write even better codes. if a code was 10 lines, the I wouldnt pay $1 for it eaither.

[Tohsaka Rin]

Jul 21, 2013 16:47:35 GMT -8 Wormopolis said:

Well I went with the concept of companion plugins, because lets say someone wanted the opposite. they wanted just the smaller function of the a plugin without the need of tracking individual users. instead of making a single plugin that HAS to use 2 keys, I make 2 plugins where the main plugin does most the work and doesnt cost the super key.

Look at it from the coder's side as well when it comes to the time where we can start charging for plugins. someof these codes are in the thousands of lines. Peter's money plugin is nearly 3000 lines. for free. if Peter instead charged $1.00 for that plugin, would you still get it? I bet a lot of forums would go ahead and invest the $1 to be able to use that plugin. by now, there has to be at least 500 forums that are using that plugin. thats $500 Peter could have earned. money which inspires him to write even better codes. if a code was 10 lines, the I wouldnt pay $1 for it eaither.

Nope, I completely understand that. My note was that I hope in the future other coders do not abuse it like it has been done on various systems. I am all for how things are right now - they should stay this way too. My issue is with lucrative marketing ploys other code developers start shortly after this sort of avenue is "explored" and they run with said crazy idea.

"If a code was 10 lines, the I wouldnt pay $1 for it eaither." - Quote

I am in the same boat here, since things I make rarely get profit. Hence the careful consideration and narrow-eyed looks scrutinizing some things right now to see what happens in the near future. I definitely rather put my money onto a few super-keys for things I WANT to support (such as this plugin and several others), not for the nickel-and-dime tactics which come from said snippet quote above.

[Wormopolis]

along those lines, Im likely going to rewrite relationship status to not use a super key, but instead use custom profile fields. that plugin was my first one using a key, but it became popular enough I never deleted it. the advantage the plugin currently has, is you can easily define certain status to HAVE the name amended, whereas the custom profile field someone could put something in that had a name attached to a status that didnt make sense.

[Tohsaka Rin]

Jul 21, 2013 19:33:40 GMT -8 Wormopolis said:

along those lines, Im likely going to rewrite relationship status to not use a super key, but instead use custom profile fields. that plugin was my first one using a key, but it became popular enough I never deleted it. the advantage the plugin currently has, is you can easily define certain status to HAVE the name amended, whereas the custom profile field someone could put something in that had a name attached to a status that didnt make sense.

Well, sometimes there are good updates and sometimes not so much. In this case, it would free up a super-key for anyone currently using it. I wonder if their data would be reset?

A relationship-status does not seem to be something so huge that the member could not just take 30 seconds of their time to fill it back out. Hahaha. Such is the progress of life I suppose.

I wish proboards would clearly state how many plugins you can have, how many keys and super keys you start out with right on the plugin page; or at least the page where it lists your keys.

^ Tagging: VS Admin, Tim Camara, Ryan Roos, Brian, Chris < This should do..I am not about to go through the entire list of staff just to tag them for something like this.

For months I had people asking me how to keep track of that, and for at least three months I didn't even know myself till I dug into the search function to see if there was a thread on this.

It definitely would give a better perspective on controlling the mishandling/misusage of certain keys. That is just my thought though. I am a terrible person rooted in reality. My common sense tends to not apply to the logic the rest of the world has.

Cest la via~

[Wormopolis]

tag a dev with the suggestion! I think its a good idea

[Chris]

If you click upgrades >> file storage when in admin panel it will give you a running tally (just in case you did not know this). I agree that having a summary of that info on the plugin page itself would make some sense.

[Tohsaka Rin]

Jul 21, 2013 21:46:05 GMT -8 Chris said:

If you click upgrades >> file storage when in admin panel it will give you a running tally (just in case you did not know this). I agree that having a summary of that info on the plugin page itself would make some sense.

Thanks for the expedited reply. It would be best to have it in plain sight, that way site owners can grasp what they have to work with and set aside proper finances/donations to get what they need. It is definitely not helpful to have the information places no one thinks of looking.

(Even I never go to that section of the forum...)

"c-o-w -- e-i-e-i-o" < someone has been watching too many silly commercials.

[Tim Camara]

Added to our list.

[Tohsaka Rin]

One suggestion did come up for this plugin: The ability to have a member added to a list which disables them from being allowed to critique.

Say the member decides to flame/troll everyone/specific others with the critique system by marking everything as terrible. The members can report that member if they have enough information on who is doing it. Right now the plugin cannot track said "offender" and so it might be easier to disable certain players from being allowed to critique at all?

I have been thinking about this for a bit, since it would be WAY too much work to make it so that you can specifically say who can and cannot critique by letting the member choose whether THEY want to be critiqued or not...or a specific thread. That person would likely change their mind on the decision how many times a day/week/month and ultimately just make the staff annoyed as heck.

Thus it would be an easier solution to stick with allowing which boards can have critiquing enabled (we already have this in the plugin) but then a way to add a specific member to "block" them from critiquing?

[Wormopolis]

actually it would be a lot easier to make it where a member cannot critique at all...

I can probably put in something that would allow someone to exempt their post from being critiqued.. but it would be a one time thing. otherwise it would just get abused. everytime someone thought they had too many of the wrong results, they would just clear them out and start fresh. if they click the button to exempt. its permanent.

[Tohsaka Rin]

Jul 23, 2013 16:14:41 GMT -8 Wormopolis said:

actually it would be a lot easier to make it where a member cannot critique at all...

I can probably put in something that would allow someone to exempt their post from being critiqued.. but it would be a one time thing. otherwise it would just get abused. everytime someone thought they had too many of the wrong results, they would just clear them out and start fresh. if they click the button to exempt. its permanent.

Yeah I know, that is what I did NOT want to get into. I was trying to think about how to do it for days...and it just gave me constipated thoughts. It is a can of worms that are best not even opened. Exempting a player from posting any critiques is soooo much easier. You can put them on, and take them off, that list and voila less headache!

Update: If you have Pebble 's [IP Look Up Buttons] plugin installed the Critique Plugin does not function properly. A member is able to still select an option for critiquing a post, however hitting "submit" does nothing.

[Wormopolis]

IP lookup.. why does that sound so familiar...?

reverse the order real quick to see what happens?

[Tohsaka Rin]

Jul 23, 2013 18:57:29 GMT -8 Wormopolis said:

IP lookup.. why does that sound so familiar...?

reverse the order real quick to see what happens?

Reversing the order does not resolve it. Already tried that, did it again to double-check. That was the only plugin that it had a confliction with as well.

[Wormopolis]

I have both loade don my test board, but I have been overwhelmed with stuff lately I havent been able to look at it yet

[Tohsaka Rin]

Jul 24, 2013 1:51:58 GMT -8 Pebble said:

Jul 23, 2013 20:09:30 GMT -8 Tohsaka Rin said:

Reversing the order does not resolve it. Already tried that, did it again to double-check. That was the only plugin that it had a confliction with as well.

Have you got a forum with both plugins running? I'll take a look if you have.
Wormopolis - If you want an editable version of the IP plugin then let me know. I have an update to it waiting to go 'live' (adding in guest ips and bot check) so I'll hang fire for now so that if the IP plugin needs a change then they can both go out together.
Pebble.

I can turn them both on over at my forum again. I had turned them off last night when testing stuff. I shall leave it running until otherwise noted.