Dynamic Signature Discussion

[Mercifull]

Noone has answered the question yet :P

[MageUK]

Noone has answered the question yet :P

 

 

 

No.

[Mercifull]

Then a second question... how many people are assigned to moderate the queue? Will this be the role of Tipit Crew or only a select few people?

 

 

 

Scenario: If I upload a pose and its approved is it logged against a username or account of sorts? So if i decide I want the purple background instead of the wood will I need to wait for it to be approved again before being able to use it. And if its not yet approved what will show in the mean time? i.e Plain background and blank area for pose.

[MageUK]

Then a second question... how many people are assigned to moderate the queue? Will this be the role of Tipit Crew or only a select few people?

 

 

 

Scenario: If I upload a pose and its approved is it logged against a username or account of sorts? So if i decide I want the purple background instead of the wood will I need to wait for it to be approved again before being able to use it. And if its not yet approved what will show in the mean time? i.e Plain background and blank area for pose.

 

 

 

If you change something on the sig and your sig includes an uploaded image you will need to wait for re-approval for that sig.

 

 

 

The queue will be moderated frequently enough that you don't need to wait too long for it to be approved.

 

 

 

If you have a sig without a custom image then you can change what you like on it without a wait time.

 

 

 

If your sig does contain an uploaded image it will have its own unique 10 digit string of characters to identify it, if you change something about the sig, then a new ID will be generated for that image. You will still be able to use the old image and ID while you are waiting for the new one to be approved, but you will not know the unique ID of your image until it is approved, so you won't have a direct link to it.

 

 

 

The idea is you will be e-mailed with your link after it's approved so people don't put them into their signatures before they're approved. If this happens it means we either have to cache an image that says "not approved", causing it to take longer for your approval (since the cache will have to clear), or we'll be serving SQL queries on every sig load for that. With the method I've coded it's only one query per cache load.

[Jimmyw3000]

Just thought of a few problems with custom poses/bgs:

 

 

 

1. Spammers may make many requests for sigs, wasting the time of the crew

 

2. From what i can get, we're going to have customable back grounds, but people can still abuse this by having a mature image in the background.

[Kaphias]

Just thought of a few problems with custom poses/bgs:

 

 

 

1. Spammers may make many requests for sigs, wasting the time of the crew

 

2. From what i can get, we're going to have customable back grounds, but people can still abuse this by having a mature image in the background.

 

1. Maybe we could have a limit of "X requests per day" or something?

 

 

 

2. That's why we have to approve them. ;)

[Beaumonde]

1. Maybe we could have a limit of "X requests per day" or something?

 

 

 

X requests a day per what? Account, multiple accounts. IP's, random, resetting ip's, proxies ect. There's no way that could be done effectively.

[Kaphias]

1. Maybe we could have a limit of "X requests per day" or something?

 

 

 

X requests a day per what? Account, multiple accounts. IP's, random, resetting ip's, proxies ect. There's no way that could be done effectively.

 

I believe anything would be better than not having one at all.

[tryto]

1. Maybe we could have a limit of "X requests per day" or something?

 

 

 

X requests a day per what? Account, multiple accounts. IP's, random, resetting ip's, proxies ect. There's no way that could be done effectively.

 

I believe anything would be better than not having one at all.

 

 

 

 

 

If it's the crew doing it, I'd say we'd ip ban all and any spammers, and also make a limit.

[Beaumonde]

If it's the crew doing it, I'd say we'd ip ban all and any spammers, and also make a limit.

 

 

 

Dsl has renewing IP's and there are always proxies.

[tryto]

Naturally. But we have the contact us page, and we rarely get deliberate repeated spam on it. I'm confident that we won't have much of a problem with it. It's still not certain who, or even if we will be screening, and I'm not the one to decide that.

[Beaumonde]

Naturally. But we have the contact us page, and we rarely get deliberate repeated spam on it. I'm confident that we won't have much of a problem with it. It's still not certain who, or even if we will be screening, and I'm not the one to decide that.

 

 

 

I could just see Zybez making a new game called put gay pron on Tip.It sigs. -.-

[MageUK]

Things are getting quite close to completion for the stats sigs now.

 

 

 

Fully uploadable poses and backgrounds are working. Poses are working with PNG-24 alpha layered images on our backgrounds.

 

 

 

The only thing we don't support at the moment is backgrounds with transparent parts in them, like if you didn't want your signature to be rectangular, this is because it's ridiculously difficult to convert all of the PNG images and make them compatible but also keep the support open for transparency on the background, it's unlikely this will change in the future but we'll see.

 

 

 

When images are uploaded if they're not the correct size then they will be resized, providing your image is correctly formatted the resize process should retain your alpha layers even in a multi-alpha-layered PNG. As a proof of this in reality, here is what a signature looks like with Mercifull's PNG-24 multi layered test image uploaded as a pose. Notice this has been automatically resized by the system hence there is a little quality lost since it's been made about 4 times larger.

 

 

 

 

 

 

Naturally it will be best to upload your image in the correct dimensions for best quality but at the end of the day that's a user decision. The other way to get around having to cope with transparency is to upload a pose that contains part of your background rather than transparency.

 

 

 

Shouldn't be too long before we have a release on the stats sigs now, the HTML/PHP frontend for creating them is near enough complete and the backend seems to be working fine (it generated this image).

 

 

 

 

 

-----------

 

 

 

A further update for anything interested in the more technical side of things...

 

 

 

To start sigs will be cached for 24 hours, this may actually decrease depending on our resource usage. Your stats will be stored in our SQL database upon being retrieved, if you regenerate another sig within a 24 hour period our cache will be used to reduce calls to Jagex. If after 24 hours your overall exp is unchanged then we won't re-cache your stats, and just use our database again, if they have changed we will update our cache and use the new ones.

 

 

 

If for some reason our SQL database fails, or we don't have a cache for you then we will fall back onto a live connection to Jagex to get your stats. If the latter fails then we'll use the SQL database even if it's outdated just to make sure you get your signature.

 

 

 

Also, there's a feature implemented so that your poses and backgrounds cannot be directly stolen by others who just change the URL. Each custom signature is assigned a unique ID and if the runescape name in use doesn't match the ID then the system won't allow it.

[evil_mumm_ra]

what would tipit do without you peter? that all sounds fine to me, albeit a bit technical jargony, but whatever, it sounds awesome and seems like you are doing a good job. keep it up.

[Celt23]

I can't wait for them, you've done an amazing job on them. :

[Mercifull]

Really awesome ^_^. Isnt it amazing on how the same idea can be implemented in a vastly different way (to how would have coded it) and yet the outcome looks EXACTLY how i imagined it lol =D> =D> =D>

[DarkDude]

nice on Peter :thumbup:

[Beaumonde]

To start sigs will be cached for 24 hours, this may actually decrease depending on our resource usage.

 

 

 

Didn't Jagex say they'd only allow automatic stat updates every 24 hours unless the user preforms an action that updates the sig?

[MageUK]

To start sigs will be cached for 24 hours, this may actually decrease depending on our resource usage.

 

 

 

Didn't Jagex say they'd only allow automatic stat updates every 24 hours unless the user preforms an action that updates the sig?

 

 

 

 

 

Stat updates are requested when someone goes on a page with one of the images on, it's 24 hours for YOUR particular stats, not a cron script that runs every 24 hours on the server.

 

 

 

Also, I've directly contacted Jagex about this and they said that they are happy for us to make automated requests to their site providing it's using the high scores text feed ONLY. They will not allow calls to their actual high scores page nor to the GE etc. unless they are user triggered, so even automated caching would be acceptable under their rules.

[InkofDeath]

Good job thus far Peter on the coding. That UserID and RSN correlating together to prevent somewhat 'thefts' or 'rips' is ingenious. :

[Mercifull]

Good job thus far Peter on the coding. That UserID and RSN correlating together to prevent somewhat 'thefts' or 'rips' is ingenious. :

It's something i'd thought about but woudlnt have bothered coding it in as I coudlnt work out how I would have done it the way I envisioned. the way peter has done it is much better.

[The Observer]

Keep up the good work! :thumbsup:

[tripsis]

GREAT job Peter! :D Everything is looking incredible!!

[Ouchy]

They are looking GREAT at the moment :)

 

 

 

Any estimation on when they will be released??

[Pat_61]

I made a banner if people want to use to link to this thread.

 

 

 

 

[url=http://forum.tip.it/viewtopic.php?f=90&t=744989][img=http://img206.imageshack.us/img206/9168/bannertifqz4.png][/url]