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.
1651
The Pub / Re: Wedge repo -- installation feedback
« on February 2nd, 2014, 07:57 PM »
Really..? I'm planning to remove it actually... :^^;: (To move it to the skins repo definitely, as an example, more than something I'd be proud to have in the default package.)
For instance, what's with this <we:title> styling..?! Wine is the very first skin I built for Wedge, back in 2010, and the goal was to stay within reach of the default SMF theme, Curve, so I kept similar titles. Ever since I finished Wine, I made sure to stay away from these horrible things.
The problem is that I no longer test in Wine, and sometimes you get, ahem, some 'amusing' glitches like blog homepages getting broken titles.
For instance, what's with this <we:title> styling..?! Wine is the very first skin I built for Wedge, back in 2010, and the goal was to stay within reach of the default SMF theme, Curve, so I kept similar titles. Ever since I finished Wine, I made sure to stay away from these horrible things.
The problem is that I no longer test in Wine, and sometimes you get, ahem, some 'amusing' glitches like blog homepages getting broken titles.
1652
Features / Re: Plugin revs
« on February 2nd, 2014, 07:52 PM »
[Commit revision 2d25292]
Author: Nao (Signed-off)
Date: Sun, 02 Feb 2014 19:50:35 +0100
Stats: 3 files changed; +10 (insertions), -10 (deletions)
Date: Sun, 02 Feb 2014 19:50:35 +0100
Stats: 3 files changed; +10 (insertions), -10 (deletions)
- Fixed calendar dates. (From SMF 2.0.7 patch.) (calendar/Subs-Calendar.php)
- Indenazi. (we_pinterest/We-Pinterest-Main.php)
- Duplicate scripts. (we_pinterest/We-Pinterest-Main.template.php)
1653
The Pub / Re: Wedge repo -- installation feedback
« on February 2nd, 2014, 06:49 PM »
Re: time zone, how exactly would a different TZ have an influence over the recorded absolute date..? I don't think Modified Date is recorded using anything less than server time... (??)
If yes, it's a bug.
Re: EOS line, well, if you'd read the Requirements stuff, you'd know you need PHP 5.3.
I'm just annoyed by the fact that I keep getting into situations where Wedge doesn't even get the time to reach the point where it says, 'stop! PHP 5.3 needed'... -_-
Anyway, I know for a fact that Charlottezweb supports PHP 5.3, so just switch!
If yes, it's a bug.
Re: EOS line, well, if you'd read the Requirements stuff, you'd know you need PHP 5.3.
I'm just annoyed by the fact that I keep getting into situations where Wedge doesn't even get the time to reach the point where it says, 'stop! PHP 5.3 needed'... -_-
Anyway, I know for a fact that Charlottezweb supports PHP 5.3, so just switch!
1654
Importing into Wedge / Re: Database permissions
« on February 2nd, 2014, 12:58 PM »
Hopefully split everything into this topic correctly.
Needs attention, I think!
Needs attention, I think!
1655
Importing into Wedge / Re: Importer tool
« on February 2nd, 2014, 12:43 PM »
You could have said thanks, or something... Your post feels like you're punishing me :lol:
1656
The Pub / Re: Minimum PHP version?
« on February 2nd, 2014, 12:42 PM »
It shouldn't matter that they use the same credentials; stored hashes won't be the same, even on the same software across different installs, because of the extra salt that's added to them. Still, if black hats steal your credentials in a more devious way (such as keylogging), you can't do anything about it, but AFAIK the forum software itself can't be hacked into submission to steal passwords, if anything because password inputs don't allow keylogging from JavaScript events. (They don't... Do they??)
No, the official reason I went for 5.3 is because of security yes. Basically, if your server has 5.2 or less, chances are it hasn't been updated in years, and then it means your Linux server might also be an older version, and Linux vulnerabilities are regularly found and patched; which is also why I prefer to rely on someone hosting my websites rather than having to myself deal with keeping the LAMP software up to date and secure. To me, it's a full-time job.
The non-official reason, of course, is that I wanted to play with lambda functions (and what fun they are!), and wanted to be done with pre-5.3 problems. It's also about comfort for me. In the last SMF patch, there's a whole block of code with complicated regex functions (include one with a nice typo in its name... Serious work, bravissimo), and a mention that this crap should be removed once SMF is made 5.3+ only.
No, the official reason I went for 5.3 is because of security yes. Basically, if your server has 5.2 or less, chances are it hasn't been updated in years, and then it means your Linux server might also be an older version, and Linux vulnerabilities are regularly found and patched; which is also why I prefer to rely on someone hosting my websites rather than having to myself deal with keeping the LAMP software up to date and secure. To me, it's a full-time job.
The non-official reason, of course, is that I wanted to play with lambda functions (and what fun they are!), and wanted to be done with pre-5.3 problems. It's also about comfort for me. In the last SMF patch, there's a whole block of code with complicated regex functions (include one with a nice typo in its name... Serious work, bravissimo), and a mention that this crap should be removed once SMF is made 5.3+ only.
1657
The Pub / Re: Design Goals | SSL / HTTP
« on February 2nd, 2014, 12:30 PM »
Yes; that's pretty much what Wedge does. I put some thought into it. You can analyze core/app/Subs-Template.php if you want to find out more about it.
I've recently seen your blog post from 2012 saying you were waiting for Wedge, I'm just surprised you didn't ask for an alpha pass back in November 2012, when I released the first private alpha... ;)
I've recently seen your blog post from 2012 saying you were waiting for Wedge, I'm just surprised you didn't ask for an alpha pass back in November 2012, when I released the first private alpha... ;)
1658
Development blog / Re: That'll do.
« on February 1st, 2014, 11:56 PM »
Yes ema, no kidding! :P
And, it's only the beginning! All of this for zero bucks! Long live free software... :angel:Quote from Maxx on January 30th, 2014, 08:08 PM Well, I haven't played a video game in over a year I think, and I've got a large backlog of games I'd like to play with at some point. The last games I managed to finish (at least 90%) were Skyrim and Kingdoms of Amalur, to give you an idea...
Apart from that, the only games I get to play are Spider Solitaire on my PC, and Classic Words on Android. I can only do casual because I just don't have the time.
Oh, re: this topic.
I've added a 'skins' repo on github. Do what you want with it!
Also, I'm hereby announcing that the BitBucket mirrors for all Wedge repositories are now retired.
The reasons?
- Nobody really bothered with them, including me.
- Everybody who's over there is also on github, and all the activity is taking place here. I didn't want to force github onto anyone, so it looks like it was an unneeded precaution.
- As much as I prefer the BitBucket design, they also have bugs, they're not responsive (for mobile), and they lack all of these nice little stat pages.
- It's kind of annoying that even on a public repo, you can't have more than a few collaborators... And if you add more, you get an even more annoying permanent popup asking you to upgrade.
- Pushing to two repos at the same time takes twice longer. Just do the math. It's only a few extra seconds, but I don't see the point in spending them, when github is obviously enough for millions of developers.
I wish all the luck in the world to BitBucket, because they'll need it. They offer good service, but the developer world seems to have chosen their champion, and I can't for the life of me afford not to be on github.
And, it's only the beginning! All of this for zero bucks! Long live free software... :angel:
I don't even know if you and the guys had a chance to even take a break?
Apart from that, the only games I get to play are Spider Solitaire on my PC, and Classic Words on Android. I can only do casual because I just don't have the time.
Oh, re: this topic.
I've added a 'skins' repo on github. Do what you want with it!
Also, I'm hereby announcing that the BitBucket mirrors for all Wedge repositories are now retired.
The reasons?
- Nobody really bothered with them, including me.
- Everybody who's over there is also on github, and all the activity is taking place here. I didn't want to force github onto anyone, so it looks like it was an unneeded precaution.
- As much as I prefer the BitBucket design, they also have bugs, they're not responsive (for mobile), and they lack all of these nice little stat pages.
- It's kind of annoying that even on a public repo, you can't have more than a few collaborators... And if you add more, you get an even more annoying permanent popup asking you to upgrade.
- Pushing to two repos at the same time takes twice longer. Just do the math. It's only a few extra seconds, but I don't see the point in spending them, when github is obviously enough for millions of developers.
I wish all the luck in the world to BitBucket, because they'll need it. They offer good service, but the developer world seems to have chosen their champion, and I can't for the life of me afford not to be on github.
1659
Plugins / Re: Calendar Plugin
« on February 1st, 2014, 11:36 PM »
Feel free to submit signed-off pull requests, though! ;)
1660
The Pub / Re: Design Goals | SSL / HTTP
« on February 1st, 2014, 11:34 PM »
I think Arantor had some plans with this... Or something. Although, I don't know, maybe it works in both out-of-the-box. My knowledge of https is limited. Even more limited? spdy :P
As for me, for years I've been the frontend guy, and I made sure to do my duty here. The only thing that was needed on the frontend was to accept external connections, regardless of their protocol. Wedge handles these nicely, AFAIK.
As for me, for years I've been the frontend guy, and I made sure to do my duty here. The only thing that was needed on the frontend was to accept external connections, regardless of their protocol. Wedge handles these nicely, AFAIK.
1661
The Pub / Re: Minimum PHP version?
« on February 1st, 2014, 11:31 PM »
I've got access to 5.3 only for now for wedge.org, although I know if I took a separate account on the same host (or if I discussed it with my hosting account owner), I could have 5.4 and 5.5. So, for now, it's 5.3 only for me, but only because Wedge is kindly hosted for free by the aforementioned third-party. ;)
(I'm just sad that this server has been doing great for years, and right when I'm going public, it's starting to show signs of fatigue... -_-)
(I'm just sad that this server has been doing great for years, and right when I'm going public, it's starting to show signs of fatigue... -_-)
1663
The Pub / Re: Minimum PHP version?
« on February 1st, 2014, 10:29 PM »
Well, the poll is long over now. The results said I should go for 5.4. I chose 5.3 because it's supported by a more realistic number of hosts.
However 5.3 is not even supported anymore. Let alone 5.2...
Yes it was a hard decision to make. Hence the poll. You could make Wedge work on 5.2 by either using an older commit from github that's 5.2 only, or modifying the current version to revert the 5.3 changes. It'll take you at least a day of work if you're a dev, and it won't be easy for you to update to the new versions.
Drop an email to your host and ask them why they're only offering a version of php that hasn't been patched in 5 or 6 years...
However 5.3 is not even supported anymore. Let alone 5.2...
Yes it was a hard decision to make. Hence the poll. You could make Wedge work on 5.2 by either using an older commit from github that's 5.2 only, or modifying the current version to revert the 5.3 changes. It'll take you at least a day of work if you're a dev, and it won't be easy for you to update to the new versions.
Drop an email to your host and ask them why they're only offering a version of php that hasn't been patched in 5 or 6 years...
1664
Importing into Wedge / Re: Importer tool
« on February 1st, 2014, 09:34 PM »
Moving this topic into its own board.
Thorsten, you're now a moderator over this section, so you should be able to split posts into topics yourself, unless you want me to do it!
Thorsten, you're now a moderator over this section, so you should be able to split posts into topics yourself, unless you want me to do it!
1665
Archived fixes / Re: Not exactly a *bug* but...
« on February 1st, 2014, 09:04 PM »
It's really odd that it didn't work for you...
Heck, when I updated my language files for the calendar, I didn't even have to refresh anything... :-/
Heck, when I updated my language files for the calendar, I didn't even have to refresh anything... :-/