Brian Klug's dashboard

Brian,

Let's say you were going to "keep product quality low". There are three ways you could approach that:

1) Break existing features
2) Stop adding new features
3) Stop fixing broken features

No one has suggested that you're breaking existing features; that would be absurd. But, PBwiki has publicly committed to the next two: no new features ("we probably won't be releasing any new features on 1.0") and no bug fixes ("we can't support old versions indefinitely."). PBwiki has also stated that there will be more more V1 wikis ("you will also not be able to create a new 1.0 wiki any longer") and that everyone will eventually move to V2 ("that will mean moving everyone to 2.0.").

So what PBwiki is doing (keeping quality low and forcing users to V2) is well documented. I understand that, as Director of Engineering, you personally are committed to producing a quality product. But if you believe that the connection between those two things has been lost on everyone at PBwiki, then I think you're being a little naive.

Now, how hard is it to stop stripping line breaks from comments? My naive guess is that it would involve removing two bytes ("\n") from the bit of code that strips out unwanted characters.

Guy - I don't appreciate your accusation. It is absurd to suggest that we're intentionally keeping product quality low in order to force users to switch to 2.0.

I was directed to this thread by David, our CEO, who asked me, "If this is indeed a small fix, can it be made?".

Come on, Sean, you know better than that. PBwiki doesn't *do* "timelines". – Guy Fawkes, 9 days ago

Have we got a vague time-line on when this should be back up. Well not too vague! – Seanmac, 9 days ago

Click the 'Settings' link in the upper-right hand corner of the wiki. – Guy Fawkes, 11 days ago

How do you go into wiki settings? – George, 11 days ago

I've talked with Brian at length about the security issues, and they are indeed legitimate. I don't want to divulge too much here without proper authorization from the folks higher up, but they are working hard to get the custom HTML feature back. After talking with him, I agree that the security measures absolutely have to be taken care of first.

Thanks for understanding,
Vu

Brian, just out of curiousity: what sort of "security" problems could you be having? Back when you decided to implement this feature, the security implications should have been obvious, and dealt with before you ever announced it's availability (and started charging people for it).

Hi all - just an update to let you know we are still working on this. There are some security-related pre-requisites we need to fix first. We do take security seriously, so please understand this is the reason for the inconvenience of not having the Custom HTML feature.

No worries, I gotcha. I think there's a 15 min timer on being able to edit/delete a comment here, but i've noticed that disappearing if you refresh the page. Also, no notifications for comments. Now that sounds familiar... – Casey Greene, 29 days ago