 |
That is wonderful. Thank you!
I like the optional include feed links too... you really put a lot of polish into these pipes you're building.
Posted 14 months ago.
(
permalink
)
|
 |
Hehehe ;)
You are welcome.
Posted 14 months ago.
(
permalink
)
|
|
Updated it to show thumbnail image of each set's primary photo in the Pipe's page…
Posted 14 months ago.
(
permalink
)
|
|
I was having some issues with the feed on one service and I realized, there's only one pubdate for the main feed - but I think there technically needs to be one on each item. I tried to see where to (a) put that information in the pipes.yahoo.com interface (but I don't seem to know that very well) and (b) how to pull that info from flickr.
(b) is what could be more complicated, i would think. First, what is the date for a set: the date it was created? The date last modified? The taken on date of the first photo? the taken on date of the last photo? Second, how do you get that value out of flickr?
I can see that flickr itself will tell you the range of taken on dates for the photos in the set - this makes sense as something they could do (pull the info from each picture). For MY uses, the most recent taken on date would work - I imagine that'd be a fair amount of work to pull into yahoo pipes, however.
Posted 14 months ago.
(
permalink
)
|
|
I set all the pubDates on every item to a constant value (by setting y:published.utime to a constant number). If your issues with that service were that the sets were showing up as new every time, this should be solved. Or was it something else?
The idea of the photoset is to be informed when someone adds a set. So it makes sense that they are ordered with the most recently-created sets first. To be updated about photos inside a particular set, then one may subscribe to that particular set, and that's why there are the set feed-links. I'll soon be updating those to point to the upcoming native Flickr photoset feed. Why do you need the sets to be ordered with respect to the most recent taken-on date inside the set?
Posted 14 months ago.
(
permalink
)
|
|
ah, no, I didn't mean to imply the ordering. When I looked at the feed that came out, I only saw one pubdate for the whole xml object. I may have misread things as well. Great to hear they're bringing in that capability natively!
Posted 14 months ago.
(
permalink
)
|
|
No you read well… I added the constant pubDate on your suggestion.
Posted 14 months ago.
(
permalink
)
|
|
hmmm. is the pubdate hard set? it is working now (that service accepted the feed), although all my pubdates say the same thing, 03:42 PDT on the 18th (and I haven't touched these sets in a week or so). Is that time when you saved the feed?
The nicest would be to have the date for each set correspond to either the create date of the set or maybe the date/s of the photos in the set...
Posted 14 months ago.
(
permalink
)
|
 |
Hello ! :3
uhm.. alto, no wonder they call you pipe god or something like that .. haha
i was wondering... would you happen to have at hand the script to embed content from the flickr photosets pipe in my site (i.e. blog), as you explained in
flickr.com/groups/flickrpipes/discuss/72157601282162783/
????
thx and keep up the good work ! (while others like me learn...)
Posted 11 months ago.
(
permalink
)
|
|
“Aparezco en google... ergo.. existo”
Jajaja! Fuerte :)
Hello broken glass, that script would be the same like the one explained in the other discussion… all you need to do is change the pipe URL in the last line: configure the photosets pipe, run it, and "Get as JSON". Then just add the _callback=show_flickr_faves parameter-value pair to the resultant JSON URL, and replace it on the last line.
Tell if me again if it isn't clear.
You are welcome! :)
Posted 11 months ago.
(
permalink
)
|
|
haha !
all set ... :D
thanx !!
Posted 11 months ago.
(
permalink
)
|
|
i tried adding a user input so we could set the thumbnail size but i couldn't :(
hardcoded it into my copycat version of your pipe
pipes.yahoo.com/pipes/pipe.info?_id=JIgOeQB13BGXjJozouNLYQ
Posted 11 months ago.
(
permalink
)
|
|
Once you managed to locate the part where it's being done (which you have)…
http://farm${farm}.static.flickr.com/${server}/${primary}_${secret}_t.jpg
… it is simple.
Break that down into
http://farm${farm}.static.flickr.com/${server}/${primary}_${secret}
_t
.jpg
and join them together again inside a "String builder" and connect it's output to where the string was before.
Test again to see if it still works. It should be the same.
It is.
Then get that "_t" from the input. To make it better you might have the user enter "Square", "Small", "Medium" etc. which you would then pass through a "String replace" to change to "_s", "_t", etc.
Posted 11 months ago.
(
permalink
)
|
|
By mistake I deleted some modules in this Pipe, but I reconstructed it… However may someone who had subscribed to this Pipe’s RSS output pass me the link, so that I make sure that I renamed the input parameters as they were before? Thanks!
Posted 8 months ago.
(
permalink
)
|
|
user_id
feed_links
were the two variables I had
I actually ending up grabbing the source and tweaking things some - this is what I ended up with.
The main difference being that I made there be a pubDate for each set, which allows RSS readers to assemble the feed in the right order.
Originally posted 8 months ago.
(
permalink
)
Kevan Emmott edited this topic 8 months ago.
|
|
Kevan Emmott, cool… that’s the spirit :)
It’s a good idea to use as a set’s pubDate the date its primary photo was posted.
Thanks for the link… so the parameter was named user_id… I just wanted to make sure. I dropped the feed_links in the newer version… I set it to “yes”. Thanks.
Originally posted 8 months ago.
(
permalink
)
alto maltés edited this topic 8 months ago.
|
 |
Thanks for the link to the added dates, I find that very useful. I also liked having the option to drop the feed_links. I know you intended this to subscribe to a set, but I am using it as an RSS to let people know when I post a new set, but I don't necessarily add new photos to a set
Posted 8 months ago.
(
permalink
)
|
|
holman@sbcglobal.net, which link?
You’re right about the feed_links… I’ll put it back.
Posted 8 months ago.
(
permalink
)
|
|
holman@sbcglobal.net, I put it back :)
Posted 8 months ago.
(
permalink
)
|
 |
Thanks for the Great Feed hack. I have a question/comment. When I try to configure this script for my sets I'm getting some weird characters. I'm using russian (cyrillic) letters in the names of my Sets and it seems that those letters are not being properly encoded. Is there anything you can do about it? Any help is appreciated. To reproduce you can try to configure this with my nick - virt_
Thanks again for this great feature!
Posted 7 months ago.
(
permalink
)
|
|
virt_, you are welcome.
Yes, I am aware of the issue. Unfortunately, currently the Yahoo! Pipes regular-expression modules do not handle Unicode well.
However since this particular Pipe only uses regular-expressions to do string-concatenations, you could modify the Pipe to use string-builder modules instead of regular-expression modules. The String-builder module seems to handle Unicode well.
Posted 7 months ago.
(
permalink
)
|
|
virt_, ok, I fixed it! :)
Which means that the My contacts’ photosets Pipe gets automatically fixed too! :)
Originally posted 7 months ago.
(
permalink
)
alto maltés edited this topic 7 months ago.
|
|
Update
Now handles Unicode character encodings correctly.
Posted 7 months ago.
(
permalink
)
|
|
Checked and added it to my RSS feed. Looks great. Works great!
Thank you very much for this and for quick response!
Posted 7 months ago.
(
permalink
)
|
Would you like to comment?
Sign up for a free account, or sign in (if you're already a member).
|
Flickr Pipes /
Discuss
Feed – Subscribe to Flickr Pipes discussion threads
Flickr Blog |
About Flickr |
Terms of Use |
Your Privacy |
Copyright/IP Policy | Report Abuse
|
Deutsch
|
English
|
Español
|
Français
|
|
Italiano
|
Português
Copyright © 2008 Yahoo! Inc. All rights reserved.
Save to Delicious