New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feed can't be found for search.twitter.com query #31

Closed
sffeds opened this Issue Aug 12, 2014 · 6 comments

Comments

Projects
None yet
6 participants
@sffeds

sffeds commented Aug 12, 2014

I have set up an RSS feed that's designed to pull specific hashtags from Twitter. I'm trying to query specified hashtags, but get an error message when trying to update the feed:
"A feed could not be found at http://search.twitter.com/search.atom?q=%23PracticeCompassion. This does not appear to be a valid RSS or Atom feed."

I've tried to update all hashtag query feeds, and the same error message is displayed for all. Please help!

@talgalili

This comment has been minimized.

Show comment
Hide comment
@talgalili

talgalili Aug 12, 2014

When I click your link I get:
The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.

When I click your link I get:
The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.

@radgeek

This comment has been minimized.

Show comment
Hide comment
@radgeek

radgeek Aug 12, 2014

Owner

Hi sffeds,

Unfortunately, I fear the problem that you're running into is probably on Twitter's side. When Twitter introduced version 1.1 of their API they made an executive decision to require authentication for all requests (https://dev.twitter.com/docs/api/1.1/overview#Authentication_required_on_all_endpoints) and also discontinued support for RSS and Atom formats for their results (https://dev.twitter.com/docs/api/1.1/overview#JSON_support_only).

I think both of these moves were a mistake, but in any case, as a result it is very difficult for a general feed consuming client like FeedWordPress to access or make use of Twitter's API data. (Essentially, you need to write a custom Twitter app in order to access data from Twitter programmatically, which will handle the requirements of OAuth authentication and also interpret Twitter's custom JSON format.) Unless Twitter reverses their decision about the API, any future use of Twitter's data streams would require considerable custom programming as an add-on to FeedWordPress.

Owner

radgeek commented Aug 12, 2014

Hi sffeds,

Unfortunately, I fear the problem that you're running into is probably on Twitter's side. When Twitter introduced version 1.1 of their API they made an executive decision to require authentication for all requests (https://dev.twitter.com/docs/api/1.1/overview#Authentication_required_on_all_endpoints) and also discontinued support for RSS and Atom formats for their results (https://dev.twitter.com/docs/api/1.1/overview#JSON_support_only).

I think both of these moves were a mistake, but in any case, as a result it is very difficult for a general feed consuming client like FeedWordPress to access or make use of Twitter's API data. (Essentially, you need to write a custom Twitter app in order to access data from Twitter programmatically, which will handle the requirements of OAuth authentication and also interpret Twitter's custom JSON format.) Unless Twitter reverses their decision about the API, any future use of Twitter's data streams would require considerable custom programming as an add-on to FeedWordPress.

@radgeek radgeek closed this Aug 12, 2014

@sffeds

This comment has been minimized.

Show comment
Hide comment
@sffeds

sffeds Aug 14, 2014

Charles, thank you very much for the follow-up. I figured as much, and your
confirmation is helpful. Cheers,

Anna Fedorova
San Francisco, CA
aabelfedorova@gmail.com

On Tue, Aug 12, 2014 at 7:34 AM, Charles Johnson notifications@github.com
wrote:

Hi sffeds,

Unfortunately, I fear the problem that you're running into is probably on
Twitter's side. When Twitter introduced version 1.1 of their API they made
an executive decision to require authentication for all requests (
https://dev.twitter.com/docs/api/1.1/overview#Authentication_required_on_all_endpoints)
and also discontinued support for RSS and Atom formats for their results (
https://dev.twitter.com/docs/api/1.1/overview#JSON_support_only).

I think both of these moves were a mistake, but in any case, as a result
it is very difficult for a general feed consuming client like FeedWordPress
to access or make use of Twitter's API data. (Essentially, you need to
write a custom Twitter app in order to access data from Twitter
programmatically, which will handle the requirements of OAuth
authentication and also interpret Twitter's custom JSON format.) Unless
Twitter reverses their decision about the API, any future use of Twitter's
data streams would require considerable custom programming as an add-on to
FeedWordPress.


Reply to this email directly or view it on GitHub
#31 (comment)
.

sffeds commented Aug 14, 2014

Charles, thank you very much for the follow-up. I figured as much, and your
confirmation is helpful. Cheers,

Anna Fedorova
San Francisco, CA
aabelfedorova@gmail.com

On Tue, Aug 12, 2014 at 7:34 AM, Charles Johnson notifications@github.com
wrote:

Hi sffeds,

Unfortunately, I fear the problem that you're running into is probably on
Twitter's side. When Twitter introduced version 1.1 of their API they made
an executive decision to require authentication for all requests (
https://dev.twitter.com/docs/api/1.1/overview#Authentication_required_on_all_endpoints)
and also discontinued support for RSS and Atom formats for their results (
https://dev.twitter.com/docs/api/1.1/overview#JSON_support_only).

I think both of these moves were a mistake, but in any case, as a result
it is very difficult for a general feed consuming client like FeedWordPress
to access or make use of Twitter's API data. (Essentially, you need to
write a custom Twitter app in order to access data from Twitter
programmatically, which will handle the requirements of OAuth
authentication and also interpret Twitter's custom JSON format.) Unless
Twitter reverses their decision about the API, any future use of Twitter's
data streams would require considerable custom programming as an add-on to
FeedWordPress.


Reply to this email directly or view it on GitHub
#31 (comment)
.

@perlarenee

This comment has been minimized.

Show comment
Hide comment
@perlarenee

perlarenee Aug 24, 2014

HI. I was able to use google scripts (as described here: http://www.labnol.org/internet/twitter-rss-feed/28149/) to create an rss feed from twitter. However the url is pretty long and feedwordpress has (of course) a limit to new feel urls that is too short to accommodate it.
Could you point me in the direction of where i can adjust the length of the url that's allowed? This should let me feed in twitter without building a separate app (fingers crossed).
Thanks

HI. I was able to use google scripts (as described here: http://www.labnol.org/internet/twitter-rss-feed/28149/) to create an rss feed from twitter. However the url is pretty long and feedwordpress has (of course) a limit to new feel urls that is too short to accommodate it.
Could you point me in the direction of where i can adjust the length of the url that's allowed? This should let me feed in twitter without building a separate app (fingers crossed).
Thanks

@cogdog

This comment has been minimized.

Show comment
Hide comment
@cogdog

cogdog Sep 27, 2014

I've used the Labnol approach for at least 6 FWP powered sites this year and have yet to run into a url length issue.

I've done some end arounds for feed URLs where I curl it locally on my server via a cron script, and rewrite it to a local RSS file with a more compact url

cogdog commented Sep 27, 2014

I've used the Labnol approach for at least 6 FWP powered sites this year and have yet to run into a url length issue.

I've done some end arounds for feed URLs where I curl it locally on my server via a cron script, and rewrite it to a local RSS file with a more compact url

@sabastore

This comment has been minimized.

Show comment
Hide comment
@sabastore

sabastore Dec 20, 2014

hi . i have tagging plugin that have a problem with feedwordpress that not tagging any post was sending with feedworpress .

i use this action to save the tags : save_post but not working . but any post sending without feedwordpress my tagging plugin has work how i can solve this problem ?

hi . i have tagging plugin that have a problem with feedwordpress that not tagging any post was sending with feedworpress .

i use this action to save the tags : save_post but not working . but any post sending without feedwordpress my tagging plugin has work how i can solve this problem ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment