A huge round of applause to paulej72 for going through the bug list and sorting out much of what was there. Furthermore, I'd also like to extend thanks to iWantToKeepAnon and TheMightyBuzzard for contributions to this release.
As always, feel free to submit your issues to our bugtracker where our crack team of flying monkeys will labor to try and make it part of future site upgrades.
Check past the break for more thoughts and comments on these changes.
There's still a quite a bit of low hanging fruit, so if you like to blowtorch old codebases, grab the source and start deleting!
Subscriber Code Enabled
We're not offering subscriptions until post-incorporation, but we wanted to start looking and smoketesting this code in preparation for that happy day. Expect to see a few users with *'s after their name that marks them as a subscriber. As a note, the subscriber +1 pseudo-mod is disabled by default, so subscriber posts do not show up higher than they otherwise would.
I'd like to get a discussion going with the community on what sort of things you'd like to see from subscribing, so look for that article, and start brainstorming on what you would be willing to pay for (like shell accounts, USENET access, or some other service we could reasonable provide?)
(Score: 1) by paulej72 on Sunday June 01 2014, @03:46AM
For what ever reason, the page load after you save your prefs is in the old theme. I believe this is due to slash partially building the user page before processing the save request giving the old theme for that page. If you click on a new page you will get the new theme.
Team Leader for SN Development
(Score: 2) by Reziac on Sunday June 01 2014, @04:28AM
Ah, okay, that would explain it. One of the original devs must have been a time traveller who did not grok doing things in chronological order. ;)
Incidentally, comment posting seems to have gotten faster.
And there is no Alkibiades to come back and save us from ourselves.
(Score: 2) by NCommander on Sunday June 01 2014, @01:47PM
The DB save is the last step of the page (the logic is .. wonky to say the least). Most of the speed performance was removing 100-200 kib worth of unused javascript :-)
(plus code removal which helps speed up Apache on the backend, though since comments are memcached, its really not the part that slows things down).
Still always moving