Wedge

I was just wondering... Did anyone ever receive spam at their git e-mails, following your use of that particular e-mail address as their commit e-mail on public github repos..?

I've always been very wary of making my e-mail address public (actually, I even have two addresses, in case one of the two ends up being spammed), because my old e-mail address (nao at kyodai dot com) was spammed to death -- about 30K spams per hour at its peak, meaning I eventually had to give up on that e-mail account. I'm aware that Google has better spam management (I'm already getting spam in both my gmail boxes despite NEVER making them public... Sigh, but at least they're mostly in the spam box), but I'm really really not excited about the idea of giving my e-mail address "like that".
My fake e-mail is nao at wedge, implying the org thing for those who can read a website URL, which in turn redirects to my gmail.

GitHub no longer wants to associate fake e-mails with accounts, even though they accepted them up til now.
So, if I associate the 'implied' e-mail address with my git account, the results are:

- I'll have to rewrite history for ALL of my frigging repos (about a dozen, including my Nao ones)... Seriously, that's f*cked up. I spent 4 days last month rewriting my histories to be as clean as possible, squashing newline-fixing commits together to avoid f*cking with the "lines added/lines removed" statistics, etc... I wanted to be as clean as possible, and then 3 weeks later -- GitHub is telling me they changed their mind and want me to do the same again. What next, then..?

- None of the repos I can't control will be able to update my e-mail address, although it doesn't matter as much.

I'd like to know who's currently using a cloned repo of Wedge, or any of its repos.

[Commit revision 6fed32d]
Author: Nao
Date: Thu, 20 Feb 2014 11:13:50 +0100
Stats: 1 file changed; +40 (insertions), -39 (deletions)

• Reverted wess_rgba changes from Dec 2013, because PHP 5.3+ doesn't accept calls to protected methods within closures that are declared inside a child class. This doesn't make sense at all, it's definitely a PHP bug, and I'm going to file a complaint at office 2A, but they're claiming I need to get hold of form 637-5c before I can proceed, and I don't know where I can get it. Perhaps from GitHub's customer support, but they're telling me that using a fake address in my commits is no longer supported and I'll now have to rewrite the entire history of all my repos and break everything for everyone because they can't make exceptions for not-so-fake addresses. Also, rewriting history forces me to get form 67E from the TheseThingsPissMeOffice, and I just checked, their address was fake.

---

[Commit revision 6207a43]
Author: Nao
Date: Thu, 20 Feb 2014 11:31:34 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)

• Syntax error breaking registration. Another 'oops', but honestly, I expected more errors at this point. (Register.php)

---

[Commit revision 427c1a2]
Author: Nao
Date: Thu, 20 Feb 2014 11:32:14 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)

• Better pixel placement of my avatar. I'm a bit vain, I'll admit it. (Credits.php)

Well, it doesn't appear when the function isn't executed. I haven't looked too much into it, but that's what's happening... I guess!

(edited your post to remove link; I prefer not to see the path to wedge.org in plain view.)

I'm aware of that, I'd just rather know how you triggered the errors, I guess... ;)

Nice! :)

Oh, didn't you manage to get attachments converted..? I thought the importer tool dealt with these without issues..?

It's probably a Facebook bug.

See a similar report...
http://stackoverflow.com/questions/13744673/facebook-php-sdk-misbehaving-after-december-12-updates

Or, maybe the file needs to be updated with the latest SDK version, I don't know.
Didn't have that bug myself.

Hopefully fixed. That was quick. :P