Mahz's Dev Journal

[Ellri]

Excellent to hear an update, @Mahz.

We would think that the easiest solution to use while until you get the url parser to not override bbcode is to disable it. The feature doesn't add all that much function even as it makes certain things people want to do impossible. Later, when you get time to make it to understand bbcode, it can be re-enabled.

Even mobile users won't have all that much trouble copying raw unparsed urls to new tabs if necessary.

Alternatively, would it work to make the parser use bbcode? A check like this:
If url is not parsed, add url tags & repeat bbcode parsing. If it has tags, do nothing.

[Phantomlink959]

Totally random question, is there a particular reason that the clock on posts differentiates one day from 24 hours?

[Ellri]

24 hours is within a certain distance of exactly 24 hours, whereas 1 day is the increment above 24 hours and below 2 days. Not 100% sure if the time increment ends are 23:31 to 24:30 or if it is more/less, but that is the general difference, @Phantomlink959

[Phantomlink959]

That is super weird and seems inefficient.

[BBeast]

That is super weird and seems inefficient.

@Phantomlink959

It makes perfect sense.
Take the time in hours, so the code in the Guild might look something like this:
if time > 24:
print str(round(time/24)) + " days"
else:
print str(round(time)) + " hours"
(This is only a simple bit of code for demonstration of possible programming logic)
This would have the effect of the time displaying "24 hours" if the time is between 23:30 and 24:00
Of course, the programming logic Mahz uses is likely rather different (and a lot more sophisticated), but the effect would be similar.

[Phantomlink959]

/me is not a programmer
/me only knows 24= 1 day, 24< i not a day

[Shienvien]

Could always floor instead of rounding.

[Ellri]

Or the simple thing of putting the actual time of posting, fitted to local timezone, rather than keeping hidden except on hover (UTC time)?

[BBeast]

Could always floor instead of rounding.

@Shienvien

He could. But if Mahz did that, then Phantomlink probably wouldn't have observed the timestamp reporting 24 hours, unless Mahz is doing something more complicated.

/me is not a programmer
/me only knows 24= 1 day, 24< i not a day

@Phantomlink959

Ok. 23.5 hours rounds up to 24 hours. But, as you mentioned, 23.5 hours is not a day. Hence a possible reason why you're seeing both 24 hours and 1 day in the timestamp.
I'll delve into the guild code to see if I can find what's going on.

EDIT: I found it. He's using a little plugin for it called timeago.
var words = seconds < 45 && substitute($l.seconds, Math.round(seconds)) ||
seconds < 90 && substitute($l.minute, 1) ||
minutes < 45 && substitute($l.minutes, Math.round(minutes)) ||
minutes < 90 && substitute($l.hour, 1) ||
hours < 24 && substitute($l.hours, Math.round(hours)) ||
hours < 42 && substitute($l.day, 1) ||
days < 30 && substitute($l.days, Math.round(days)) ||
days < 45 && substitute($l.month, 1) ||
days < 365 && substitute($l.months, Math.round(days / 30)) ||
years < 1.5 && substitute($l.year, 1) ||
substitute($l.years, Math.round(years));

Key point is that, if time is less than 24 hours, it displays time in hours, rounded to the nearest hour. If time is equal to or greater than 24 hours, it will display time in days (or greater units)

[Shienvien]

@BBeast: This was more of a suggestion for a quick fix on my part, so to speak. Rounding time up tends to come across as a bit nonsensical.

[BBeast]

@BBeast: This was more of a suggestion for a quick fix on my part, so to speak. Rounding time up tends to come across as a bit nonsensical.

@Shienvien

I would disagree. For instance, 1 hour and 45 minutes is closer to 2 hours than it is to 1 hour. Of course, it's mostly a matter of preference.

[Shienvien]

@Mahz: Still being logged out on browser restart.

@BBeast: For me, it is more logical to see 3h and conclude three full hours and then some than to see three hours which might not be full three hours yet but may also be more than three hours... Similarly, if someone doesn't have seconds displayed on their computer's (or any digital) clock and I see 23:30 there, I'll assume 23:30:xx rather than 23:29:30-23:30:30 - this simply is how electronic clocks normally work, by flooring rather than rounding. And it'd get rid of oddities like 24h and 1d being different things.
But in the end, it is as you said: a matter of preference. My personal reaction tends to be a raised eyebrow when I see someone rounding time.

[Ellri]

We also rather prefer correct time over rounded time, @Shienvien. There's no real benefit to rounding time when the UTC timestamp is available by hovering mouse over the rounded timestamp.

[LegendBegins]

I prefer flooring the time as well. In my mind, I read it "At least 3 hours ago" as opposed to "About three hours ago."

[Hank]

Is it me, or do the GM/coGM post badges look different now? To be fair, I'm on a PC at work on Internet Explorer that's older than version 9 and the whole site looks a little different so it could be that.

[NuttsnBolts]

@Hank They look the same to me.

[Ellri]

No change on OP badge so far as we can see.

[Hank]

The whole site looks weird on this PC anyway.

Take a look.

[Shienvien]

It's old IE being old enough to not support the diagonal styling option. And a couple of other elements.

[Hank]

It also doesn't support post editing or opening hiders.