Recent Posts
11
Features / Re: New revs
« on April 18th, 01:27 AM by Nao »
[Commit revision e80acb5]
Author: Nao
Date: Tue, 18 Apr 2017 01:27:11 +0200
Stats: 1 file changed; +12 (insertions), -20 (deletions)

  • Two new techniques for the key-value file cache, to combat possible race conditions. First of all, Wedge will no longer attempt to delete an expired file when it sees it expired. It's the script's responsibility to regenerate the cache (and thus the file) when it gets an invalid result (also, this saves more bytes, and I like saving bytes). Secondly, files are now created under a random name (like in Subs-CachePHP.php), and then renamed if everything works. This should help in a LOT of situations. And I'm serious. Just like I fixed race condition issues with the PHP minifier, I'm hoping this will also be the case here, although it happens much less often-- in fact the only reason I fought this is because Opera Chromium is bloody running two queries on my site at the exact same millisecond, even if I didn't ask for that. For once, it's Opera's fault. (Subs-Cache.php)
  • Seriously, someone should report that to them... Opera is actually loading Atom feeds even though I never added them to my feed list.
12
The Pub / Re: Question about SHA1/256 (github issue #60)
« on April 18th, 01:09 AM by Suki »
If there are any changes, it will be known pretty early, any change in the default algo will be made in the next full release after a proposed algo was included. Plenty of time IMO.

And you will always know what thing was changed and to what. Theres a similar problem if you chose an user defined algo, sooner or later you will have to upgrade your script to get rid of obsolete ones.
13
Features / Re: Language revs
« on April 17th, 09:25 PM by CerealGuy »
@Freñiçh  If you need help with git, feel free to ask. Git has a steep learning curve but is absolutly worth learning it.
14
Features / Re: Language revs
« on April 17th, 05:21 PM by Nao »
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...
15
Quote from Nao on April 16th, 04:13 PM
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...?
As long as you always hash it with the same algorithm on client side, it wouldn't matter, because you always hash it again on server side. The problem i see is that the unclear nature of password_hash() would result in inconsistencies across different php versions. So you couldn't use a backup from a newer php version on one with a server with an older php version.
16
Features / Re: Language revs
« on April 17th, 02:40 PM by Freñiçh »
Quote from Nao on April 17th, 02:19 PM
@Freñch, please stop committing individual files and sending pull requests for those!
Also, move them to the proper folder!
What do you mean it looks like you don't want the dutch translations (first you don't react on pull request and then you ask for zip files)....so i create new files again and send them with pull request.

 :edit: Also committing language files plugins topic_solved
17
Features / Re: Language revs
« on April 17th, 02:22 PM by Nao »
[Commit revision 5a0dc43]
Author: French77
Date: Mon, 17 Apr 2017 14:06:39 +0200
Stats: 1 file changed; +658 (insertions), -0 (deletion)

  • Create index.dutch.php (#41)
18
Features / Re: Language revs
« on April 17th, 02:21 PM by Nao »
[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)
19
Features / Re: Language revs
« on April 17th, 02:19 PM by Nao »
@Freñch, please stop committing individual files and sending pull requests for those!
Also, move them to the proper folder!
20
The Pub / Re: Question about SHA1/256 (github issue #60)
« on April 16th, 04:13 PM by Nao »
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...?