Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Nao
Plugins / [Plugin] Re: CountLikes
« Yesterday at 11:16 PM »
Well, I guess I'm lucky, since I couldn't remember where your repo was (I still don't :P), I didn't update it, so I could have redone the same thing you did... As I said, I'm lucky, because I hate wasting time. :P

Hmm, I noticed that doesn't seem to enable my plugins when I try to turn them on... It only accepts one, I don't know why. So weird.
Features / Re: New revs
« Yesterday at 11:12 PM »
[Commit revision 7196a1f]
Author: Nao
Date: Wed, 29 Mar 2017 23:10:05 +0200
Stats: 3 files changed; +4 (insertions), -3 (deletions)

  • Another potential fix for non-cooperating PHP versions that complain about empty buffers. (Subs.php)
  • Fixed weird menu background color in Warm. (Warm/extra.css)
  • Useless + sign. (wraph.js)

[Commit revision 2e9a0be]
Author: Nao
Date: Wed, 29 Mar 2017 23:12:36 +0200
Stats: 1 file changed; +36 (insertions), -19 (deletions)

  • Replaced board state icon (except for IE8 and older) with a CSS representation of the same thing. It looks better, and it saves at least 300 bytes off the gzipped CSS file. And it's Firefox-friendly. If you need to replace the icon, you can always reset the class entirely. Seriously, it's a cool update. (sections.css)
Features / Re: New revs
« Yesterday at 12:46 PM »
[Commit revision 2f082c8]
Author: Nao
Date: Wed, 29 Mar 2017 12:45:48 +0200
Stats: 5 files changed; +5 (insertions), -5 (deletions)

  • A few captcha images, typically the static ones, were being deleted twice. Once in Subs-Captcha.php, and once in their class' destructor. (captcha-grid.php, captcha-ledicons.php, captcha-ledicons_anim.php, captcha-silhouette.php, captcha-stripes.php)
Features / Re: New revs
« Yesterday at 12:18 PM »
[Commit revision b42ffae]
Author: Nao
Date: Wed, 29 Mar 2017 12:03:12 +0200
Stats: 1 file changed; +1 (insertion), -1 (deletion)

  • So, hmm... I forgot to add whitespace search before // comments in the Packer code. Yeah, well, what can I say, I'm busy. Sorry for the mess with 'http://' strings... I double-checked, and none of my JS files use comments without whitespace before them. (Subs-Cache.php)
Features / Re: New revs
« Yesterday at 12:18 PM »
[Commit revision 26810ca]
Author: Nao
Date: Tue, 28 Mar 2017 19:37:01 +0200
Stats: 1 file changed; +1 (insertion), -1 (deletion)

  • Undefined variable when posting. Yeah, that pretty much broke your new feature Cereal, didn't it..? ^^ (Post2.php)

[Commit revision f02dd70]
Author: Nao
Date: Tue, 28 Mar 2017 19:39:16 +0200
Stats: 2 files changed; +3 (insertions), -1 (deletion)

  • Removed debug code. Not even mine... (Class-Packer.php)
  • Now removing comments by myself before submitting them to Packer. Why? Because its over-complex removal code returns errors when compiling on some servers. (At least the one I'm on.) (Subs-Cache.php)

[Commit revision fe47054]
Author: Nao
Date: Tue, 28 Mar 2017 19:42:59 +0200
Stats: 1 file changed; +0 (insertion), -1 (deletion)

  • Removed more debug code. Not even mine, again. Ah ah. And not even from the same guy as the previous commit's. (Subs-BBC.php)
Plugins / [Plugin] Re: CountLikes
« on March 28th, 02:57 PM »
Okay, I'm just gonna upload this fixed version of the main file. It gave me an error if attempting to view likes that didn't belong to a post. ;)
I used the opportunity to clean it up: fix typos, spacing, and a few database issues.
Features / Re: Language revs
« on March 24th, 12:44 PM »
[Commit revision 1ac5400]
Author: Nao
Date: Fri, 24 Mar 2017 12:41:55 +0100
Stats: 1 file changed; +3 (insertions), -3 (deletions)

  • OMG typos!!!!!!! Not from me I think! I hope! Can anyone check? (ManagePermissions.french.php)
Bug reports / Re: Couple things to look into...
« on March 20th, 10:25 PM »
Well, I wouldn't have committed otherwise... ;)
But it's still in the air. I mean the problem with post manipulation inside topics is that there are so many niche situations... Like people showing topics in reverse order, etc... I'm just hoping nothing was broken.
Features / Re: New revs
« on March 20th, 04:28 PM »
[Commit revision 7fdc0bd]
Author: Nao
Date: Mon, 20 Mar 2017 16:28:03 +0100
Stats: 2 files changed; +6 (insertions), -6 (deletions)

  • This is a follow-up to rev c92eb3fb73b94a545029e73a830540e5779dfd5c from October 2013. I'd changed the Mark Topic as Unread system to better accomodate for infinite scrolling, but it also broke 'regular' use of the feature by resetting the read post counter to the beginning of the page, instead of the last unread post. I've tweaked the files to always reset to the last unread post, unless (1) you're on a read page (in which case it will mark the LAST post in THAT page as unread), (2) you're in infinite scrolling mode and you just viewed a new page (here it'll simply mark the penultimate read page's last post as unread.) This sounds complicated, but it works better for me. Until, of course, someone tells me it's broken... (Display.php, Subs-Boards.php)
Features / Re: New revs
« on March 20th, 03:40 PM »
[Commit revision d9f6873]
Author: Nao
Date: Mon, 20 Mar 2017 15:40:19 +0100
Stats: 1 file changed; +12 (insertions), -19 (deletions)

  • Simplified 'test' strings in the BBCode list. Looks like when the strings were originally moved to the database, extra useless backslashes were added to them. (Subs-BBC.php)
Thanks, your last bug report was addressed. ;)
Features / Re: New revs
« on March 20th, 12:28 AM »
[Commit revision e5868b1]
Author: Nao
Date: Mon, 20 Mar 2017 00:28:38 +0100
Stats: 1 file changed; +77 (insertions), -77 (deletions)

  • Fixed lightness value being treated is a 0-1 float instead of a 0-100% value. (Class-CSS.php)
  • Changed all array()'s to [] while I was at it. Looks so cool. But, yeah, dream on, I won't do it across the entire project. Maybe just the commonly loaded files. This has no influence on performance, so it's just to a developer's benefit. (Class-CSS.php)
Quote from Freñiçh on March 19th, 12:37 PM
Quote from Nao
Any reason you'd want to have an exclusive https connection?
Well a secure connection between internet browsers and websites is not a luxury it's a must, allowing to transmit details,passwords or any personal information.
But what personal information would you want to transmit over https here that isn't already encrypted..?
It should be enough that Wedge now fully supports https. ;) (It wasn't the case before.)
The only problem is with avatars, which sometimes use http links so you have to be smart about them.
So when an users on my Website which is secured with a SSL Certificate chooses to click on a link (on our credit page) it seems logical to me that this must be a secure connection.
Not really, no..?
Development blog / Re: The obligatory Christmas update.
« on March 19th, 12:40 PM »
I just realized this was my last post on the blog... :^^;:
Oh, and that comment system looks so cool.

I'm guessing I need to make a strong statement about Wedge still being alive.
Thanks to CerealGuy for never giving up and pestering me into coming back :)
Also thanks to for giving me a good reason to get back to work!
Well, IIRC I only added https support to for testing. I'm only making use of it on, where sensitive (or more precisely, 'valuable') data can be shared. I keep asking my host to enable http/2 on nginx[1] but she won't budge. I had my websites hosted by someone else so I wouldn't have to deal with keeping a list of installed modules to update, but apparently I'm not the only one not willing to do that ahah.

Any reason you'd want to have an exclusive https connection? Because AFAIK it's a bit slower (5% at least?), and there is no sensitive data here-- everything is open source and passwords are encrypted before they're transmitted anyway.
 1. This would give me a good reason to move everything to https, by making everything load noticeably faster.