Comment Field Patch

[se.nsuo.us]

Originally Posted by raminia

thanks but be more considerate. I've asked you to send me info but you didn't. (you published it on the forum) and I was so busy to follow.

Heh! can the devs please be consistent in what they are asking - when I first sent you the PM about SQL injection you said post it to the forum - I did not because I have not looked into all the other possibilities and I am sure posting that to the forum would open a pandora's box. Now you are saying that I should not publish to the forums! Please note I still do not publish sensitive info on the forum - unless it has been pointedly igonored and I have a solution.

anyway I have more things than Pixelposting in life.

Yes Sir - I am not exactly unemployed either and besides my regular job and hobbies I already am a contributor to several other open source projects

In case you have missed the point here - I am trying to teach devs to fish rather than give them the fish... I feel that is a better form of community service.

If you publish an Open Source software which you claim to be stable you own it to the community to give them protection. You have taken up that responsibility now shrugging it is bad form - you should gracefully hand it over to someone you deam fit - Unfortunately, I am presuming, there is some amount of in-fighting in the dev team and it now spilling out.

So please be considerate to your users... I will put out a more complete patch when I have time

[raminia+]

I gracefully hand in Pixelpost (if I can ) ) to someone as rude as you and you will ruin the community in days.

O Dr. O the greatest! O The biggest teacher O Please tell me to be more considerate to my users!! O great father please teach me! Please tell all people on the forum that you teach pixelpost dev team because you are the greatest!

Thanks. That was the best answer someone could give me to the hundreds of hours and hours of scripting for Pixelpost. Take care ... I don't have time for you anymore.

[se.nsuo.us]

ROFLMAO! I don't have time for you either Ramin - but I do have for Pixelpost as I find the program useful.

I refuse to stoop down to your level. End of thread for me!

[raminia+]

Cheers! now when I talk in you language the discussion stopped. Ballance!

Please do it. Fork Pixelpost into a better software. It's not my own property. It's not even my desire to Pixelposting for good. but please delete every part of the code that I wrote and do it again. because you have no time for me buddy. Take the chance to be the ONE.

no more post here from raminia

[se.nsuo.us]

Ramin, I will respond to you once you start talking like an adult and are done with your tantrum!

Once again! No I am not going to fork Pixelpost and I am not going anywhere I have already written that in this thread

[Joe[y]+]

can we get back to the topic on hand please?

i'm not expert on xss despite reading a couple of the links se.nsuo.us kindly shared with us but if i'm not mistaken would a good (if not temporary) solution be to simply strip comments entirely of script and just leave them as plain text.

i'm happy to admit that the pixelpost team isn't perfect and neither is pixelpost despite our efforts - there's no such thing as perfect open-source software and when a problem, however basic, like this one pops up there's no use in pointing fingers at anyone. i for one appreciate all of se.nsuo.us's input into the project so ony my behalf thanks.

anyway, yeah - what are thoughts on stripping comments down to plain text? i can't see why this would be a problem and if users care so much about their smilies or whatever they use then they just don't have to install the patch...

[se.nsuo.us]

@Joe[y] Thanks for lending the voice of sanity to the thread

Apologies to the general public for being so harsh with my words but I stand by all of them

I hopefully will have time later in the afternoon and will write that patch or may be a bit later!

Let us hear which tags should be allowed - my personal recommendation is (format 'tag' => 'attribute' (allowed) )

'a' => 'href', 'target'
'b' => None
'blockquote' => None
'em' => None
'i' => None
'img' => 'src', 'width', 'height', 'alt', 'title'
'strong' => None
'u' => None

Anything more needed?

P.S. the above list is taken from Flickr

[blinking8s+]

we all started this project for fun, when pixelpunk created pixelpost it was because there wasnt anything like it out there, and we all just loved helping out. this isnt some super awesome wordpress like organization with a serious business mindset...yes we try to keep it on a remotely professional level, but we're not in it for that level of things...we love photography and pixelposts helps us share that. if we cant meet someones needs or expectations then there is nothing we can do about that. it's a fun atmosphere, we spend hours on end helping people setup blogs and talking about photography, and in our spare time outside life and that pixelpost takes it's form...this is our process and we depend on people to give feedback.

we've had a run of luck on this forum, i moderate in 4 other large communities, and this is one of the first heated debates we've had here. it's not a bad thing though so i urge everyone to just take a deep breathe and be chill about it. we're all here for the same reason, and pixelposts code isnt perfect. but with each thing we do together it gets closer and closer to what a userbase demands out of it.

i've thought about a revamp for the comments system for a while, a bbcode or markdown editor system would be nice for the future, but in truth outside a linkback tot he commenter, who needs the rest of those things in a comment anyway?

[whiskerz]

I am a new user to pixelpost. I love the fact that I can implement a photoblog without wasting my life trying to get my MT to function as such.

In regards to comments I can take them or not. Comments at least let me know I have been viewed and they can offer constructive criticism but I would like the ability to turn them on or off for individual entries. In addition, I see no reason to allow any html scripting for comments. I think plain text in a comment should be enough, if not at least an option.

Of course my desires are more involved than developing a rapid-fix to a current problem. I simply offer my opinions as fodder for your creative juices in the pursuit of a lean yet robust photoblogging tool.

Thanks for all you guys have done! *nod*

[Joe[y]+]

Originally Posted by whiskerz

I love the fact that I can implement a photoblog without wasting my life trying to get my MT to function as such.

hehe. well that's exactly what pixelpost is for!

Originally Posted by whiskerz

I would like the ability to turn them on or off for individual entries. In addition, I see no reason to allow any html scripting for comments.

this is something we have recently considered as well and will certainly appear in a later version of pixelpost - if not in an addon before then.

Originally Posted by whiskerz

I think plain text in a comment should be enough, if not at least an option.

an option sounds like a good compromise. good thinking! thanks.