n.a

if only there was a way that donation perks could be approved faster. I have to wait 1 month to get my custom rank because of a website error or something. But TPM has a good idea with using that as a perk.

 

Only Matthew can do the user images / custom ranks. This is because you are adding a new image to the server, something only tech admins can do. Richard doesn't deal with it and neither does Govind. n4n0 has said Matthew's pretty busy at the moment irl, so all you can do is wait. Donation perks are a privilege remember.

 

I know, it's just something anyone would have liked to avoid.

 

Naw if you take that away its gonna be spam city in mfer.

 

If people really want to spam for post-count, they'll do it anyway

 

I would support at a $100 donator level. Anyone who gives the site $100 would not DDOS it (I think....)

I understand there would have to be a new usergroup, but it would be a nice perk to have! Wouldn't you say?

 

Is the only reason it's not going to happen the issue related to the time spent implementing such a feature? Or could it create other issues?

 

After reading this thread, I'd say it's safe to assume the 30 second delay has been around since the start of sythe?

I honestly don't see it as that much of an inconvenience. If i'm doing multiple searches, i'll just tab out for a few seconds and read an article, or have another Sythe tab open to look at new threads.

If it'll take days of work to just change the donator user group to work with this implementation... I don't see it as being worth the admins time.

I mean, it would be nice if it took them 5 minutes to fix, but days and re-arranging ranks... all for a 30 second delay? Not worth it imo, but I wouldn't mind it if the staff was up to it.

 

I don't see this as a problem, I see this as patient issues. Sorry guys but I do not support this.

 

You'd have to ask Matthew about this. He's the one who stated that multiple donor usergroups are NOT going to happen. If he says it won't happen, then it probably won't happen.

 

If we can't make this a donor perk, would it be possible to show a countdown of (30-t) seconds where t is the seconds until we can post? In this case, if you tried to post 12 seconds after posting elsewhere, it would say "You can post again in 18... 17... 16... 15... etc." seconds until it gets down to 1, after which it would post for you, in the same way that hopping worlds in-game logs you in automatically after a given amount of time.

 

this is bullshit, get some knowledge instead of only increasing your post count. the search results are cached which means loading the page is just as demanding for the server as loading a normal page.

massive support for removal, it should be done

 

I also want to add - those of you pressing for the multiple donor usergroups and stating it won't take long to do - YOU ARE WRONG.

Changing/creating multiple donor usergroups would FORCE Matthew to re-write large portions of the code used for the donation center in order to account for and properly manage the new usergroup(s), which would be a time consuming process.

 

The administrators, both Sythe and Matthew themselves have stated this point. -Ryans on their staffing team, so of course he trusts their point of view on the situation.

Thanks for the clarification n4n0.

Does anyone know if Sythe started like this, or was their a particular instance that forced the change? I'd love to see if we could trial the site without the 30 second limit and see the "Stress" that's caused.

 

Reposting because I'm curious.

 

Just try to post again. It tells you exactly how long you have left. You don't need a countdown timer. That's just a waste of time to code.

 

@n4n0
you still haven't responded to this. No need to make a workarounds, just remove the whole limit.

 

I can't answer that because I don't know if it's really cached or not. I don't know enough about VB or how it works.

Edit: Just did some spam-searching on a couple users, and I noticed SOMETIMES it pulls a cached version (as shown here: ) but this only happens about 50% of the time, if not less.

 

Is it possible to test it out for 24 hours? If it slows the servers down anymore then I'd understand keeping it.