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 bziman on Saturday May 31 2014, @10:12PM
I've observed another oddity... I'm browsing with threshold/breakthrough at 1, flat, oldest first, and I noticed several posts either out of order, or with their time stamps wrong.
Screen shot at http://swisspig.net/images/snorder.png [swisspig.net].
Note that the first message is at 1:20 PM, the next at 11:27 AM, and the third at 2:14 PM.
Wait, is this because despite my having selected "flat" and "oldest first" it's grouping them by thread? I think it is... if so, then that is seriously broken.
(Score: 2) by NCommander on Sunday June 01 2014, @01:45PM
That's ... odd. I'm not sure its a regression (though its definitely a bug); we're probably engaging the threadsorter even when in flat which is what's causing that; I don't think we've touched that bit of code at all so its likely been there from the beginning and just been noticed since everyone is poking threads now. Will poke paul to look at it, or will look at it myself this weekend.
Still always moving