Well, I do. And Jeff has a vague idea, if only because he's been watching me replace huge swaths of code in the past few days. It's been a bit frightening.
But the bottom line is that there's now a new way (under the hood) for SixLinks to process anything that happens - from a guide step being done to a blog post to a comment. Everything goes through events now, and it's lovely.
What this means for you fine users is that things like email notification (which worked, but was intermittent to put it kindly) should now be solid. We still have to wire up a few of the notices, but for things like suggestions and FAQ they already work.
A nice side-effect of this refactoring is that the updates feed is now faster, simpler, and more flexible. Thanks, Django's generic foreign key support!
In other notes:
But the bottom line is that there's now a new way (under the hood) for SixLinks to process anything that happens - from a guide step being done to a blog post to a comment. Everything goes through events now, and it's lovely.
What this means for you fine users is that things like email notification (which worked, but was intermittent to put it kindly) should now be solid. We still have to wire up a few of the notices, but for things like suggestions and FAQ they already work.
A nice side-effect of this refactoring is that the updates feed is now faster, simpler, and more flexible. Thanks, Django's generic foreign key support!
In other notes:
- You can now submit new questions to be included in the FAQ, from any FAQ page
- As a result, all the old FAQ questions have been tossed. They were outdated anyway.
- The funky look for suggestions in Firefox has been fixed. That was my fault. I forgot a </span>. I apologize for slandering Firefox.
- Screenshot uploading bug has been fixed.


Get the Facts
Do Your Part

Me
My Part
Following
Community
Talk
Even More
Comments
Comments
No comments yet.