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
556
Plugins / Re: Suggestion: HTTPS Login
« on September 24th, 2014, 12:16 PM »
Two more details...

- Yes, forcing the login page into HTTPS is probably possible, but I'm not willing to put work into that (because of the above mostly),
- And among the disadvantages of HTTPS are that it's slower. But AFAIK, HTTP/2.0 should be based off SPDY and has the secure flag enabled by default, so it should be as fast as HTTP/1.1 without the penalties incurred by HTTPS, I think. I'm not sure how SSL certificates will work for HTTP/2 though, since it's a PITA to build them, and dedicated IPs are a real problem on shared hosting, obviously...

:edit: Apparently, if you have no SSL certificate, then you can't use HTTP/2... Simple as that, uh.
Posted: September 24th, 2014, 11:45 AM

It's more complicated than that; apparently, nothing is set in stone regarding HTTP/2, so I'll just wait until something more concrete surfaces...
Anyway, I've just gone to the https version of wedge.org, and posting from it, and I'm happy to report that apparently it's working fine (once of course you get past the browser prompting you to accept the certificate as it's signed for alwaysdata, not for wedge.org).
557
Plugins / Re: Suggestion: HTTPS Login
« on September 24th, 2014, 11:41 AM »
AFAIK, if you're not in https, worst case situation is someone can steal your session ID, although I'm not sure it'd allow them to do a lot...
Login page in https means your hashed password is transmitted safely, but people can't steal your password itself, only your access to your account, which is barely better than getting a session ID.

Hmm, makes me think... Shouldn't we store two hashes for admins...? One hash for their account, and one hash for their admin verification (same password, different salt). That would probably make the whole thing even safer, I don't know..?

Regarding https, last week I spent a couple of hours configuring a free SSL certificate for wedge.org, until I realize, at install time, that it required to have a stand-alone IP, i.e. no virtual host, like wedge.org is using... Oops! So, that's a waste of a certificate for me, I guess... Unless I move to a server with a dedicated IP :-(
And I'm not ready to move yet, as I switched ISPs this month, and the new one has a shorter and faster path to alwaysdata.com, meaning the site is finally blazing fast for me... :lol: Unless the server was upgraded in the meantime, I don't know...
558
Features / Re: New revs
« on September 22nd, 2014, 05:23 PM »
[Commit revision 52ad1bb]
Author: Nao
Date: Mon, 22 Sep 2014 17:23:09 +0200
Stats: 1 file changed; +3 (insertions), -0 (deletion)

  • In Chrome browsers, admins could no longer manage (delete, etc.) anyone's profiles but theirs. Hmm, this was due to my recent trick for forcing Chrome to retrieve your saved password in admin login boxes. (QueryString.php)
559
Plugins / Re: Tapatalk support?
« on September 21st, 2014, 01:44 AM »
Quote from Cataphractus on September 20th, 2014, 11:19 AM
This is the one thing that's preventing me from migrating my forum to wedge. About ~80% of my users enter from tapatalk.

From my point of view, Tapatalk Inc should be responsable for developing the plugin. After all, they're making money out of it. Unfortunately, I don't think it's gonna happen anytime soon... :(
It's not a POV thing. It's the fundamental way Tapatalk is built: they add support for your software, and individual forum owners add their spam splash to their forum. The forum software author has no say in it, except "Tapatalk sucks! I don't frigging want a splash screen on a forum I'll just be spending 10 seconds on to check out a message!"
It's similar to websites that ask you to download their own app, or websites that launch a popup asking you what you thought about them, preventing you from reading them in the first place...
560
Features / Re: New revs
« on September 20th, 2014, 05:55 PM »
[Commit revision 437382a]
Author: Nao
Date: Sat, 20 Sep 2014 00:02:16 +0200
Stats: 1 file changed; +25 (insertions), -14 (deletions)

  • Various minor improvements: more responsive topic titles (using flexbox if available), blog comment bubble tail position, and thought list fixes. Please note that the @if test was useful in Weaving until I decided not to proceed with identical $window_bg and $window_bg2 values, although it's still easy to do on your own skins. (sections.css)

[Commit revision eae8bcf]
Author: Nao
Date: Sat, 20 Sep 2014 00:02:58 +0200
Stats: 1 file changed; +1 (insertion), -1 (deletion)

  • Commenazi. (Wireless/extra.css)

[Commit revision d49e096]
Author: Nao
Date: Sat, 20 Sep 2014 16:11:31 +0200
Stats: 1 file changed; +7 (insertions), -4 (deletions)

  • Fixes to Warm; also, trying to make it more... watchable. That'd be a good name for a skin. (Warm/extra.css)

[Commit revision c6bcd2a]
Author: Nao
Date: Sat, 20 Sep 2014 16:12:32 +0200
Stats: 2 files changed; +2 (insertions), -6 (deletions)

  • Firefox (no longer?) needs one of these many flex workarounds... (sections.css)
  • Select box border color benefits from being brighter, I think... (index.css)

[Commit revision 10a7860]
Author: Nao
Date: Sat, 20 Sep 2014 16:16:05 +0200
Stats: 1 file changed; +14 (insertions), -3 (deletions)

  • And some tweaks for Wilderless, for good measure. (Wilderless/extra.css)

[Commit revision 0d03088]
Author: Nao
Date: Sat, 20 Sep 2014 17:44:22 +0200
Stats: 2 files changed; +4 (insertions), -3 (deletions)

  • Chrome removed 'position: sticky' from their web platform experiments back in June. Hopefully it makes it back soon into the codebase, just like the vertical tabs feature. Eh? What did you say? They never restored vertical tabs?! Oh, yeah, now these are TWO things missing in stock Chrome that I hated to see go. Anyway. (common.css)
  • Firefox Mobile v32 doesn't seem to support sticky either (yet), so I'm removing support for it. (common.css)
  • A silly syntax error broke stickies in Wilderless. I never noticed it because it's a mobile-centric skin, my iPod is long gone, and none of the Android browsers support sticky for now. Also improved sticky rendering. Works fine in Firefox v32 for Windows. (Wilderless/extra.css)
561
Plugins / Re: Tapatalk support?
« on September 19th, 2014, 10:24 PM »
Also Tapatalk would need to implement support for wedge itself. 
562
Features / Re: New revs
« on September 18th, 2014, 09:33 AM »
[Commit revision 6375a3f]
Author: Nao
Date: Wed, 17 Sep 2014 16:19:22 +0200
Stats: 1 file changed; +2 (insertions), -2 (deletions)

  • Fixed some issues with the burger icon on mobile. (sections.css)

[Commit revision 98d6783]
Author: Nao
Date: Wed, 17 Sep 2014 16:21:09 +0200
Stats: 1 file changed; +3 (insertions), -2 (deletions)

  • Fixed animation on search form, as well as a sizing issue in... "Internet Explorer. What else?" (index.css)

[Commit revision a638f93]
Author: Nao
Date: Wed, 17 Sep 2014 16:25:55 +0200
Stats: 1 file changed; +2 (insertions), -0 (deletion)

  • Create a new stacking context for the search input, ensuring it shows on top of the 'Notifications' button when enlarging it on mobile devices. Trust me. (index.css)

[Commit revision 6bb1f10]
Author: Nao
Date: Wed, 17 Sep 2014 16:48:09 +0200
Stats: 1 file changed; +1 (insertion), -2 (deletions)

  • A less 'original' background for Warm. I'll leave original stuff to external skins... Right? (Warm/extra.css)

[Commit revision 9e31847]
Author: Nao
Date: Wed, 17 Sep 2014 16:49:14 +0200
Stats: 1 file changed; +1 (insertion), -1 (deletion)

  • Semibold looks good on Windows, so I'll use that (for now) in Wilde headers... (Wilde/extra.css)

[Commit revision 40b9961]
Author: Nao
Date: Wed, 17 Sep 2014 17:43:14 +0200
Stats: 1 file changed; +7 (insertions), -5 (deletions)

  • Subtler alternate backgrounds for Weaving. Dunno if it'll stick. Feel free to suggest better defaults! (common.css)

[Commit revision e7143f3]
Author: Nao
Date: Wed, 17 Sep 2014 17:49:43 +0200
Stats: 1 file changed; +2 (insertions), -2 (deletions)

  • Search input should have a more subtle border. (index.css)
  • Make use of your own macros, man..! (index.css)
563
Plugins / Re: Tapatalk support?
« on September 18th, 2014, 08:36 AM »
That's a piece of shit. Why would I provide support for spam software that keeps bugging me to install it when I'm just trying to read a lambda forum post accessed from google?

Wedge has responsive mode.

Best I could do is write my own android app and make it non disruptive... But I have neither the time nor the motivation.
564
Features / Re: New revs
« on September 16th, 2014, 01:10 PM »
[Commit revision c3c77a3]
Author: Nao
Date: Tue, 16 Sep 2014 13:10:07 +0200
Stats: 4 files changed; +9 (insertions), -9 (deletions)

  • IE 11 (and presumably later) fails to support gz extensions. GO FUDGE YOURSELF, IE!! (Class-Editor.php, QueryString.php, Subs-BBC.php, Subs-Cache.php)
  • Broken link redirect code didn't work for non-gzipped css/js. (QueryString.php)
565
Archived fixes / Re: Wedge.org broken in IE11
« on September 16th, 2014, 12:29 PM »
I'm very annoyed to announce that after my initial round of testing (i.e. installing an update, restarting, launching IE, testing wedge.org, bis repetita), even though everything worked, I then tried to access my local site and it failed to show the CSS and JS...!!!

For some reason, IE 11 kept the 'correct' cache on the disk, but if I specifically erase the cache, then it starts failing.

So, phase 2... Applying the fix. I simply swapped the extensions for IE, and it seems to be working now. Please delete your file cache, and test again!

I'm wondering if I shouldn't swap extensions for ALL browsers, rather than just IE... It seems to be working everywhere, but... What if we then discover another specific browser that fails to run these, eh..?

@BurkeKnight, don't forget, this problem supposedly only occurs on Windows 8.1...
566
Archived fixes / Re: Wedge.org broken in IE11
« on September 16th, 2014, 11:54 AM »
Installed ALL updates (except for anti-virus stuff, which I won't need because it's just a temporary VM I'll delete later today), and it still works perfectly.

See screenshot... Meh?
567
Archived fixes / Re: Wedge.org broken in IE11
« on September 16th, 2014, 07:22 AM »
Quote from Johnny54 on September 10th, 2014, 11:04 AM
This problem is reported to MS IE team shortly after the release of patch kb2976627
(https://connect.microsoft.com/IE/feedbackdetail/view/950689)

One month past and another round of patches but unfortunately this problem hasn't be solved. :cry:
So... Long night, nothing to do, decided to install an evaluation of Win 8.1 + updates to see what MS was up to.

Anyway, here we are... I'm with the '627 update (the one you mentioned), the rest is pure unmodified stock English Windows 8.1, and it's working just fine.
I'm currently installing all other updates (excluding the other ones for IE11 which I'll do much later), so if I can then reproduce, it means it's not due to '627, but to some other Windows update.
568
Features / Re: New revs
« on September 14th, 2014, 08:43 PM »
[Commit revision eef8bbe]
Author: Nao
Date: Sun, 14 Sep 2014 10:33:25 +0200
Stats: 3 files changed; +18 (insertions), -23 (deletions)

  • Cleaner implementation of the burger (show sidebar) icon. It should look the same across all devices now, and not use non-semantic tags, although it didn't matter much because they were generated by JS anyway... (index.css, sections.css, script.js)
569
Features / Re: New revs
« on September 12th, 2014, 01:08 PM »
[Commit revision c763368]
Author: Nao
Date: Fri, 12 Sep 2014 13:07:27 +0200
Stats: 13 files changed; +26 (insertions), -26 (deletions)

  • Harmonized all 'timestamp' fields to use unadjusted times. The reasoning behind this is that (1) apart from a couple of occurrences not dealt with in this commit, NONE of these timestamps are actually used by Wedge, (2) wasting time on adjusting unused data is pointless, (3) it's easier to adjust times with timeformat() and time_tag() than un-adjusting them manually if needed. (Merge.php, MessageIndex.php, Modlog.php, PersonalMessage.php, Post.php, PrintPage.php, Profile-View.php, Recent.php, Search2.php, Split.php, Unread.php, UnreadReplies.php, Who.php) (Also a few plugins!)
570
Features / Re: Plugin revs
« on September 12th, 2014, 01:08 PM »
[Commit revision 94d7f71]
Author: Nao (Signed-off)
Date: Fri, 12 Sep 2014 13:08:27 +0200
Stats: 5 files changed; +7 (insertions), -7 (deletions)

  • WedgeDesk timestamps are no longer adjusted. None of them were being used anyway, so... (wedgedesk/*)
  • Oops, I said there were multiple plugins that were affected, but that's just the one.