4 ms·

Thanks for pushing out such a site, really interesting and useful. Couple of things, - Seems you are violating their TOS https://twitter.com/logo#naming https

by Bjoern 13y ago

Thanks for pushing out such a site, really interesting and useful. Couple of things, - Seems you are violating their TOS https://twitter.com/logo#naming https://twitter.com/logo#naming > In March 2013 Twitter will shut down the RSS feed - that's > a fact! - and reason why we created this free RSS service. - As of April 13 (today), it seems RSS is still working on the Twitter API, https://api.twitter.com/1/statuses/user_timeline.rss?screen_name=brennhak https://api.twitter.com/1/statuses/user_timeline.rss?screen_... - Finding something on Twitter and RSS/ATOM shutdown despite searching for some time yielded nothing.

evunveot 13y ago
They started doing "blackout tests" [1] last month and are switching it off completely on May 7 [2]. (The public RSS feeds are a part of API v1.) [1] https://dev.twitter.com/blog/api-v1-retirement-update https://dev.twitter.com/blog/api-v1-retirement-update [2] https://dev.twitter.com/blog/api-v1-retirement-final-dates https://dev.twitter.com/blog/api-v1-retirement-final-dates
- Bjoern 13y ago
  Thanks for the links! Very sad to see the ongoing destruction of the openness and usefulness of Twitter.
onosendai 13y ago
I'm not the author, I just though the service might be useful given the impending shutdown of RSS access to Twitter and the continuing demand for it. Yes, they are violating the Twitter TOS regarding naming/branding, but it should be easy to work around it. So far it seems the site hasn't had much exposure, and I'm interested in how Twitter will respond to it if it increases. If they really want to prevent the re-packaging of user's tweets into RSS feeds, and depending on how they're obtained (through API access, plain old HTML skimming, etc..) things could get interesting.
- Bjoern 13y ago
  Just was digging through API v1.1 seems that there is a way to get a JSON (https://dev.twitter.com/docs/api/1.1/get/user.json https://dev.twitter.com/docs/api/1.1/get/user.json) but that needs authentication apparently.

by Bjoern 13y ago

evunveot 13y ago

They started doing "blackout tests" [1] last month and are switching it off completely on May 7 [2]. (The public RSS feeds are a part of API v1.) [1] https://dev.twitter.com/blog/api-v1-retirement-update https://dev.twitter.com/blog/api-v1-retirement-update [2] https://dev.twitter.com/blog/api-v1-retirement-final-dates https://dev.twitter.com/blog/api-v1-retirement-final-dates

Bjoern 13y ago
Thanks for the links! Very sad to see the ongoing destruction of the openness and usefulness of Twitter.

onosendai 13y ago

I'm not the author, I just though the service might be useful given the impending shutdown of RSS access to Twitter and the continuing demand for it. Yes, they are violating the Twitter TOS regarding naming/branding, but it should be easy to work around it. So far it seems the site hasn't had much exposure, and I'm interested in how Twitter will respond to it if it increases. If they really want to prevent the re-packaging of user's tweets into RSS feeds, and depending on how they're obtained (through API access, plain old HTML skimming, etc..) things could get interesting.

Bjoern 13y ago
Just was digging through API v1.1 seems that there is a way to get a JSON (https://dev.twitter.com/docs/api/1.1/get/user.json https://dev.twitter.com/docs/api/1.1/get/user.json) but that needs authentication apparently.