Wedge

[Commit revision db90bfd]
Author: Nao
Date: Tue, 18 Apr 2017 23:59:26 +0200
Stats: 2 files changed; +0 (insertion), -179 (deletions)

• Nearly there! ;) (ManageScheduledtasks.dutch.php, dutch/license.txt)

Hi Suki/Marceline! Hadn't seen you here in 3 years ;)

So, you guys think I should use something like that..?
https://github.com/dcodeIO/bcrypt.js/blob/master/dist/bcrypt.js

I'd suggest using the bcrypt parameter explicitly so that if Wedge is ever abandoned, it doesn't break completely.

(Unless I really don't understand the problem...)

I'm not trying to frustrate anyone. Just trying to frustrate *me* as little as possible. :P

I'm absolutely for any new translations.

What I'm against, however, is wasting time. So, if you want your translations to be in the main languages repo, you should learn how to handle Github and pull requests. That's all.
Yesterday you sent empty pull requests. Today you sent one pull request *per* file, meaning I got an e-mail notification for each of those. When I started accepting the pull requests, I then realized the files were all committed to the root folder (which is NOT for anything other than English files, this isn't SMF, this is Wedge, where files are carefully sorted in language folders!) So I had to do another commit to put them all into place. You also committed a junk file in the lot. It's a real mess. So I said, I'll stop merging your PRs, yet you kept sending them so at the end I just canceled them all.

All I want is a clean repo with just a single commit for all of your files. That's all... Just create a new repo locally from Github, move your new files to the dutch folder, right-click them all, "Add", then commit, and send a single pull request (you can do that one from the Github website as long as it knows your repo is forked from mine, IIRC). It's really easy... It just takes a couple of minutes. Not the couple of hours it took you to upload everything manually...

[Commit revision a00d78c]
Author: Nao
Date: Mon, 27 Mar 2017 20:12:03 +0200
Stats: 1 file changed; +1 (insertion), -1 (deletion)

• Grammar nazi. (ManageInfractions.french.php)

If I do password_hash() with PASSWORD_DEFAULT, then it means I can't be sure what algorithm will be used to hash the password, right..?

So, how exactly can I hash the password on the client side if I don't know which kind of crypt system PHP will use to compare it with my own hash...?

Did someone look into the Subs-Login semi-mystery?

I also have a quick note for optimization purposes. Just can't bother to add it to Wedge, but this should probably be in the next database update batch (remember? ;))...

I found out that {db_prefix}thoughts has no index on the id_parent column. It's often used in inner joins, so it should REALLY be there. I don't use thoughts a lot, so it's no biggie, but I can imagine that after a while, it'd have an influence over performance.