portland independent media center  
images audio video
newswire article portland metro

take your soma

laziness or censorship ?
Yet again, the dreaded "no story to tell yet" byline has reared it's
ugly head. The general opinion of many people here seems to be that
this is due to hardware shortages, software failure and general ineptitude.

The average 'surfer is not in a position to question any of this. One
might wonder, though, about the editorial bias of the censorship hating, freedom of the press loving PDX Indymedia Staff. Hardware is pretty cheap these days. Dumpster cheap. And Linux ALWAYS runs faster on a server...I know about THAT. And the right wing sites I also like to throw dissenting opinions into respond, invariably, in tiny fractions of the time it takes for the gears of PDX Indymedia to turn. Why is this ? Hello staff ? Are you spending so much time sifting through all of the masses' opinions, deciding what is politically viable to let through, that you have somehow managed to become stuck in 1997 technology ? No, I don't buy it.

To every other individuality oriented dissenter out there...what is going on here at PDX Indy ? Perhaps they might explain why controversial opinions seem to run into software and hardware problems all the time, and extremely lengthy data transmissions of photograph after high-res photograph of Communist rallies
just slide right on in, problem free ?

phone: phone: .
address: address: .


hm 17.Jan.2003 03:19

hrmph

today:

"--no story to tell yet--

#40969-(refreshed)-remembering the plan that never was (?): operation northwoods
#40926-refresh (science, civilization's ally)
#40899-refresh (we are a peaceful nation)
#41009-HOW BUSH, CHENEY AND CLINTON USED MIND CONTROL TECHNIQUES TO MOLEST CHILDREN"

all articles were "refreshed". i won't speculate any further.

good questioning--why not "survey/surveil" instead of gripe?

wow 17.Jan.2003 03:53

hrmph

even had to immediately refresh this article :)

due to technical difficulties... 17.Jan.2003 08:43

ranger

I don't think it is censorship, because some run of the mill discussions have been plagued by "no story to tell". This is however, frustrating. I'm sure there is a technical explanation. Maybe someone at IMC can elaborate.

Paranoia is good and helpful and often right 17.Jan.2003 10:10

GRINGO STARS gringo_stars@attbi.com

But paranoia isn't always accurate. Suspect everyone and everything. That way you get to the bottom of things. But I have refreshed many articles here - sometimes it works, sometimes it doesn't - both important (to me) articles and not. I do not suspect censorship here.

tyu467uiyu,ljhf, 17.Jan.2003 11:33

mfhujkryuik6

8i5786yujsyjfvhnsfgjghjkl,jklghcfksdfhjk;sd


stop getting paranoid about the no story to tell thing. please.

How do you fix the "no story..." thing 17.Jan.2003 14:07

a

I remember seeing a post that provided directions to fix the "no story to tell" thing. If anyone has a link or feels like writing out the directions again, I'd be most appreciative.

instructions back up 17.Jan.2003 16:28

indytech

the instructions for refreshing the 'no story to tell yet' are back up. . .replaced it inadvertantly, but it is there again

plans are progressing for a new server

and if the pdx indy volunteers want to hide useless disruptive crap posts and comments, we just will do it. . .none of this 'no story to tell yet stuff', which btw, happens to stories that indy volunteers put up as well. . .i suppose we screw up some of our own stories to make it look like it is just a technical glitch

damn, but aren't we all diabolical!

IMCers got terrible recall :) 17.Jan.2003 17:37

member when?

say you get a "no story to tell yet" mesg.

this is what the URL for the story looks like
{ http://portland.indymedia.org/front.php3?article_id=41121&group=webcast}

the article # (id) is "41121".

to refresh an article, the URL that you should enter should look like this:
{ http://portland.indymedia.org:80/REFRESH.php3?article_id=41121&group=webcast}

you have replaced the term "front" with "refresh" (no caps necessary) and you have added the number 80--http port number--preceeded by a colon.

also, when submitting articles and comments, there'll be messages that determine the success of your submission. i've noticed that you're post has been entered when the message has your article title in bold and some other term in bold, telling you your story has been posted. (other times there is no boldface type and i can't be sure if the post took..in this case it's best to wait a while instead of trying to re-send).

sometimes you get the database messages that say any number of things, but mostly that the connection was dropped by a peer or something like that; i tend to think that the post didn't make it when i see this message.

i noticed once an article go back to the "no story to tell" screen right after being fixed.

i would assume if more than one imcer is refreshing an article that there should be no major problems but i don't know what the overall effects of a server-side refresh are so...

who knows, maybe relaxing and not getting too noided is the best thing. just take note of the behavior and consider the "natural" things that could be going on that might be causing the problems.

at midnight and for about 2 minutes, pdx is unreachable--i presume it's a system thing and normal.

also, i think it's a best idea to go back to the front page before trying going to look at your work of master wit; this avoids the double post definitely and in general is good practice.

after a 1/2 a damn day 18.Jan.2003 05:47

nothing funny

to fix a "no story to tell" page:

if this is the URL of the article that is not being displayed

{ http://portland.indymedia.org/front.php3?article_id=41121&group=webcast}

then this is what you change it to to get it to display
{ http://portland.indymedia.org:80/refresh.php3?article_id=41121&group=webcast}

remember.

as for the database, yeah it's odd as hell to have so many problems w/ the d-base @ this site, but thankfully such probs get straightened out by competent and loving people.

(now, try to figure out which d-base messages mean that your posts haven't gone through and when you want to ensure that posts have gone through, go back to the main page first)

soma sleep 18.Jan.2003 06:30

sleep

to fix a "no story to tell" page:

if this is the URL of the article that is not being displayed

{ http://portland.indymedia.org/front.php3?article_id=41121&group=webcast}

then this is what you change it to to get it to display
{ http://portland.indymedia.org:80/refresh.php3?article_id=41121&group=webcast}

remember.

as for the database, yeah it's odd as hell to have so many problems w/ the d-base @ this site, but thankfully such probs get straightened out by competent and loving people.

(now, try to figure out which d-base messages mean that your posts haven't gone through and when you want to ensure that posts have gone through, go back to the main page first)

---------------------------------------------------
Number of files uploaded: 1

Thanks for contributing! after a 1/2 a damn day has been published.

go back to the front page
(press reload after you get to the front page to see your new story - please don't press reload before then, or we'll get two copies of your story! Your story may take a minute or three to appear while files are transferred behind the scenes)
Or add another story

Refreshing article id 41121 and summary pages (for group webcast).! !
Parse error: parse error, expecting `T_STRING' or `T_VARIABLE' or `T_NUM_STRING' in /www/active-cvs/portland/webcast/article_display.inc on line 221
!
Warning: PostgreSQL query failed: FATAL 1: This connection has been terminated by the administrator. pqReadData() -- backend closed the channel unexpectedly. This probably means the backend terminated abnormally before or while processing the request. in /www/active-cvs/portland/shared/db_class.php3 on line 1113

Warning: Supplied argument is not a valid PostgreSQL result resource in /www/active-cvs/portland/shared/db_class.php3 on line 1033