Fire Starter

Problem solved! We all PM to Fang then he resends them to whoever is the receiver :D Plus! Wookie, you can thank Fang, cause now you don't need to do all the coding for the new PM system :P Edit: And the best of all - we all get to blame Fang if any message gets lost/mis sent/altered etc. :cool:

AVG? What was that? It was eatable around 3 years ago... Not now ;)

With all being said I also think, that the stones with acousticremains will artificially get their price quite high. And a personal reason, which no body is bound to consider: I tend to forget many things with lightning speed, so for organizing my MD life it's essential to be able to make quick logs from time to time.

Google offers translation of entire pages, though I am not confident that it will manage that well with the suggestions made. In translate.google.com we can influence the outcome. but translating the whole page imho will make MD look rather bad.

If the delay is intended, then I am OK with it. I can see Mur's reasons, while looking from his point of view, and No one's also from the other side. Looking from MD's point of view though, I must admit, that Mur's points are more logical. I also would prefer the faster interface, but I have already experienced much of MD through the past years, and can do without some things. Which is bad, because I DO feel that I am already loosing some of the MD touch. This is mostly due to the intense RL stuff on my mind, but that would never excuse me for trying intentionally loose more of what MD feels and looks like.

The only thing I do mind is that I have to wait for the text to disappear to give space for the resources info. It's sometimes annoying to have to scroll/PgDown+PgUp at a particular scene, but in any way it takes much less time than the current situation. What if the text and resources info show at the same time, one at it;s place now, and the other just below it. Then after the text expires it just blends and the resources info moves up. Or smth similar to this.

You mean you have lost all the PMs we have sent you prior the Big Bang?!? tz, tz, tz dst..., how could you...

I would add that the best evolution would be for smth like a suggestions search. Idk what it's called, but every search provider uses it. Like when I type "d" for example, I get all the players I have talked with, that start with a d - dst, DARK DEMON, Draconas, etc. In alphabetical order perhaps. and it remembers the selection after we return to the messages list when done reading certain message.

Well, with the above data it shows in the "Options" menu, but not in the main page.

And I do see what No one is talking about - the only nice thing is, that the whole page goes smoothly up and down. It's kind of fun and it seems I can play with this all day long :D Browser: Firefox 21.0 OS: Win7 32 bits PrtScrns: http://storenow.net/my/?f=3782c899fe260bb8b1b5e44637874c65 http://storenow.net/my/?f=3e569643724c922c2a8f146428f11539 Download and compare - it shows.

It will be only an option, John, you take it if you need it. You won't be forced to use it, just like the Messages sorting cloud ;)

I hope I am still on the topic, bringing it out while working on the crits pages functionalities: http://magicduel.invisionzone.com/topic/12395-battle-icon-activeinactive/ ...and... this one: http://magicduel.invisionzone.com/topic/11282-new-functionality-in-the-ritual-creating-interface/ If this falls enough into off-topic, then this post can be removed.

*Fire Starter seconds both dst first (ofc!!!) and Shem second*

And thank you, dear Winner, for the fast payment. 5 gold note and 10 SCs received. This topic can now be closed.

Since it's been over 24 hours after the last bid I am pleased to announce the winner in our 15th Auction: Congratulations Mallos! Contact me in game for further details. Thank you to all the others, who have participated and good luck the next time ;)

It's the "The Longest Joke in the World" http://longestjokeintheworld.com/ more than 42 meters long :) And in the end there are some answers.

I believe I was in those 11% :D What can I say - I love reading :P

I am getting one of those Chinese android phones this Friday, so I will be able to make more extensive testing during the weekend.

hmmm, now I gotta dig out that HTC and see what was on it, that was working fine... You all got me puzzled :)

It's not in my garden, but it seems it's in my neighbor's one :D Ping statistics for 164.138.28.154: Packets: Sent = 73, Received = 72, Lost = 1 (1% loss), Approximate round trip times in milli-seconds: Minimum = 46ms, Maximum = 74ms, Average = 53ms That is with no load on the system, ofc.

EE's one should state "withdrawn" or similar. It was a bid, but not with the proper "funds" :)

Yeah, I know. If you're phone is up to the challenge use the normal site. It should load just fine. But it is still depends on the phone and android versions.

So, the sum of the oppinions is - the Eastern part of the World wins this time. Maybe our ISPs are better at last, LOL

“Scientists have calculated that the chances of something so patently absurd actually existing are millions to one. But magicians have calculated that million-to-one chances crop up nine times out of ten.”

Everything seems fine here: [spoiler] Pinging magicduel.com [164.138.28.154] with 32 bytes of data: Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=63ms TTL=57 Reply from 164.138.28.154: bytes=32 time=62ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=60ms TTL=57 Reply from 164.138.28.154: bytes=32 time=57ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=47ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=57ms TTL=57 Reply from 164.138.28.154: bytes=32 time=52ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=62ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=56ms TTL=57 Reply from 164.138.28.154: bytes=32 time=50ms TTL=57 Reply from 164.138.28.154: bytes=32 time=47ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=47ms TTL=57 Reply from 164.138.28.154: bytes=32 time=61ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=57ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=50ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=47ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=56ms TTL=57 Reply from 164.138.28.154: bytes=32 time=57ms TTL=57 Reply from 164.138.28.154: bytes=32 time=56ms TTL=57 Reply from 164.138.28.154: bytes=32 time=50ms TTL=57 Reply from 164.138.28.154: bytes=32 time=51ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=80ms TTL=57 Reply from 164.138.28.154: bytes=32 time=62ms TTL=57 Reply from 164.138.28.154: bytes=32 time=50ms TTL=57 Reply from 164.138.28.154: bytes=32 time=66ms TTL=57 Reply from 164.138.28.154: bytes=32 time=52ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=91ms TTL=57 Reply from 164.138.28.154: bytes=32 time=50ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=47ms TTL=57 Reply from 164.138.28.154: bytes=32 time=52ms TTL=57 Reply from 164.138.28.154: bytes=32 time=51ms TTL=57 Reply from 164.138.28.154: bytes=32 time=56ms TTL=57 Reply from 164.138.28.154: bytes=32 time=49ms TTL=57 Reply from 164.138.28.154: bytes=32 time=65ms TTL=57 Reply from 164.138.28.154: bytes=32 time=47ms TTL=57 Reply from 164.138.28.154: bytes=32 time=68ms TTL=57 Reply from 164.138.28.154: bytes=32 time=61ms TTL=57 Reply from 164.138.28.154: bytes=32 time=50ms TTL=57 Reply from 164.138.28.154: bytes=32 time=60ms TTL=57 Reply from 164.138.28.154: bytes=32 time=59ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=58ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=65ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=50ms TTL=57 Reply from 164.138.28.154: bytes=32 time=51ms TTL=57 Reply from 164.138.28.154: bytes=32 time=51ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=47ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=48ms TTL=57 Reply from 164.138.28.154: bytes=32 time=50ms TTL=57 Reply from 164.138.28.154: bytes=32 time=62ms TTL=57 Reply from 164.138.28.154: bytes=32 time=51ms TTL=57 Reply from 164.138.28.154: bytes=32 time=73ms TTL=57 Reply from 164.138.28.154: bytes=32 time=58ms TTL=57 Reply from 164.138.28.154: bytes=32 time=77ms TTL=57 Reply from 164.138.28.154: bytes=32 time=60ms TTL=57 Reply from 164.138.28.154: bytes=32 time=62ms TTL=57 Reply from 164.138.28.154: bytes=32 time=51ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=56ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=57ms TTL=57 Reply from 164.138.28.154: bytes=32 time=72ms TTL=57 Reply from 164.138.28.154: bytes=32 time=52ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=54ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=52ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=57ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=57ms TTL=57 Reply from 164.138.28.154: bytes=32 time=60ms TTL=57 Reply from 164.138.28.154: bytes=32 time=62ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=52ms TTL=57 Reply from 164.138.28.154: bytes=32 time=53ms TTL=57 Reply from 164.138.28.154: bytes=32 time=52ms TTL=57 Reply from 164.138.28.154: bytes=32 time=52ms TTL=57 Reply from 164.138.28.154: bytes=32 time=63ms TTL=57 Reply from 164.138.28.154: bytes=32 time=60ms TTL=57 Reply from 164.138.28.154: bytes=32 time=55ms TTL=57 Reply from 164.138.28.154: bytes=32 time=64ms TTL=57 Ping statistics for 164.138.28.154: Packets: Sent = 124, Received = 124, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 91ms, Average = 54ms Control-C ^C[/spoiler]