MageUK

Our custom pose/background URLs now have a maximum length of 48 characters. Edit : Will also be trying something else that will reduce both the custom and non-custom URL lengths by around a further 10 characters.

I don't really think it needs to be unique at all, it's just an easy way to pick poses. As for comparing it to yours, our pose previews are slightly larger and actually use the same amount of poses per row etc. Actually, just looking at the boxes, our pose selection areas are almost identical in size (wasn't intended). Here's our pose selection areas in actual size compared:

Our sigs are already competitive with the lengths of the Draynor, Leetsigs, etc. URL lengths. Using the shortest options from Leetsigs but with a 12 character RSN, I get a URL length of 55 characters. Using the shortest options from Draynor but with a 12 character RSN, I get a URL length of 62 characters. Using the longest options from Tip.It for a NON-custom sig and a 12 character RSN we have a URL length of 55 characters. Using the longest options from Tip.It for a custom sig and a 12 character RSN I get a URL length of 61 characters. Edit : Actually just thought of something that will reduce the URL length of the custom sigs by ~10 characters on average. Will try it later.

Always edging closer to our release, here are some screenshots of the web interface. Creating a signature with Tip.It poses and backgrounds... [hide=Screenshot][/hide] Creating a signature with a Tip.It background and a custom pose... [hide=Screenshot][/hide] Creating a signature with a Tip.It pose and a custom background... [hide=Screenshot][/hide] Creating a signature with a custom pose and background... [hide=Screenshot][/hide] Looking up your custom signatures in case you didn't receive the e-mail... [hide=Screenshot][/hide]

Do it a few times and you should see what I mean, I expect it's probably to try and stop people faking their clicks/hits. The first thing to do would probably be to tell them our server can't check the image size because of that "Invalid Referrer" error and see how they respond to that.

I expect the reason for this is something to do with DragCave.net's servers and their mechanisms for checking what is loaded. Try clicking this URL. You should see the image. Then try refreshing and you'll notice you get "Invalid Referrer". This is what the Tip.It server will be seeing when it attempts to get the dimensions of the image. If you want to use it I'm afraid you'd need to speak with DragCave.net about lightening their restrictions a little.

. Try another IM program which allows you to use the MSN protocols. any chance you could suggest one? Trillian should do.

I meant did you get any unexpected e-mails before you noticed someone had access to your account? Ever get anything asking you to reset your password or personal information or something that you never requested?

Takes a bit more than a stolen cookie to get into Paypal that's for sure. How secure of a password did you have? Could it have been guessed? Did Hotmail and Paypal use the same password, and have you recently received any e-mails claiming to be from either one you weren't expecting?

I think you're looking for http://www.uzzisoft.com/

I've been using Messenger Plus! Live since it came out and Messenger Plus before that (pre-Windows Live Messenger). I'd personally say it was safe although I can't endorse it directly of course. ;) I believe it asks if you want to install a toolbar to support it, but it's optional, you can choose NOT to give your support and hence not install it.

We could host the images and not be legally responsible for the images because the users upload them, however we would have to remove them on request. Because of this we're just going to moderate them at the source. And no, we won't be allowing users to input their stats, as Lordofrah says it's not really all that difficult to get plenty of stats ranked these days.

Pure_MageUK, wait... I thought the measurement was from 'Jan. 1, 1904'? :? ... Call me crazy, but something just doesn't add up about 1969... :oops: magmaguard3, as for the bug, I do have to say that's odd... But I'd bet Pure_MageUK can reach into the database tables and tweak that back into place. :thumbsup: ~D. V. Devnull http://en.wikipedia.org/wiki/Unix_time PHP's time() function :

That's because time in most applications is not measured by recording the date and time in a normal format, it's measured by recording the amount of seconds since January 1st, 1970. When the forum issues arose we lost the creation times of those threads, so the forum sees the time as 0, and hence as 1970.

I could do that but I'd have to change the style just for that link because none of the phpBB links are underlined by default. :P I'll add it to my list to look at.

No worries. ;) Also added the Tip.It logo to subsilver.

You could try FRAPS, might work for you since it's designed mainly for games.

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.

What OS? I'd personally go with the extra RAM but that CPU does have double the cache...

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.

Check perhaps? Yep, it seems to me that the browser is using the cache and not the actual page. Happens to me sometimes on Opera. He was right the first time... uncheck everything EXCEPT the cache. Whatever is checked gets cleared.

Because Tip.It doesn't allow the discussion of controversial topics like that. You'll see no one else with religious names either, rules are for everyone.

#4 is complete and awaiting upload. #3 should be fixed soon enough. #2 & #1 I don't really see as problems.

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.

No.