Hi,
I want services in my install of MT but I do not want the streams. If I had all the users adding their Twitter accounts it would bring my server to a crawl. I thought that deleting the streams.yaml, or just commenting everything out in it, would do. But nope, I get this error when I do:
No such pseudo-hash field "oneup"
So, can someone please tell me how I can have all the services and none of the streams?
Thanks,
Ken
Reported on Movable Type 4.2
1) Why would you want to tease your users like that.
2) Have you just deleted the streams that you don't want available?
3) How did you comment things out in the yaml file? Yaml is very temperamental, like XML, in that regard.
1. Do you realize what the affect of fetching hundreds or thousands of streams of Twitter, Delicious, Digg, Flickr, YouTube, etc. feeds would do to my server? Dedicated or not, it would kill it. It is not a tease, I am not offering FriendFeed on our community site, I am offering Pownce, ironic, no?
2. No, I have not tried deleting selective ones, seeing as I want them all gone. Also considering the oneup one is the very first one in the YAML file, I figured that trying to be selective was going to be fruitless. But I will give it a shot.
3. I commented the entire file out. I did not try commenting out each and every entry.
Since Action Streams is now officially included in MT Pro, maybe Six Apart Support will support it now, did not think of that until now. I will open a ticket with them.
BTW, if I edit a 3rd party stream, such as 12seconds.tv, and take out the stream in the config.yaml, it works. But it has to end in a new line or I get an error, because yaml is very temperamental, I know :(
Okay, I have made some progress. I was able to delete oneup from the streams.yaml and it now works as I want it to, with no error message.
It looks like this is going to be a heck of a lot of trial and error.
It would be easier for you to just copy the streams you DO want and put them into a new streams.yaml file.
Btw, I am well aware of what ActionStreams could do if thousands of users are using it at once, but my question was why you'd offer it to them in that situation ;)
Granted, if you were to use the publish queue for their action stream pages and configure ActionStreams to run only ever 6-12 hours, it probably wouldn't be that big of a deal. You can change the frequency it runs in the YAML file.