I have website had built by using ASP.NET c#, my website contains page called my tweets page to display all my tweets from my account on twitter.
I seen many ways but all ways need authentication step , so it bad solution, I am searching about way do what I need, without need authentication step.
Summary:
I am looking to get posts from timeline as data or Rss to make customization for it in my website ,without need authentication step.
If I understand correctly you want to display your tweets on you asp.net page.
You can do this by simply creating a widget and loading in on your page. this is a very simple process involving simple html and java script. Twitter will take care of the rest.
Below is the link
embedded-timelines
no authentication is required.
One small correction, you can display a maximum of 20 tweets at once, after that user needs to click on load more to get the some more appended below.
Related
I've been following this question to retrieve the twitter feed for a particular user Authenticate and request users timeline twitter api 1.1 which is working as expected, the issue I now have is trying to style it to make it look like the twitter feed, the reason we are doing this on the server is because we have a database with all our tweets in so instead of making calls to twitter we have decided to call our database and pull them through. This was implemented and followed through just encase twitter decided to update there API which may result in our feed working (management didn't want to take that chance.)
I have spent some time today trying to find a possible solution to see if this has been done already, I'm aware people have provided server side code to retrieve the tweets but I can't find an example of passing the tweets to the view and displaying them.
I am confused about this upcoming Twitter API 1.1 change and how to re-implement functionality like that that used to be provided by jquery widgets like http://tweet.seaofclouds.com/ and http://thomasbillenstein.com/jTweetsAnywhere/.
I have been able to get linq-to-twitter to do a search using the ApplicationOnlyAuthorizer to at least get most of the information into a GridView, but this will re-use the same tokens (the ones belonging to the application) over and over, and will very quickly burn through 450 requests in 15 minutes when deployed to a live site with hundreds/thousands of active users...
In addition, for display I'd rather be able to re-use one of the basic jquery plugins out there, so it seems I'd have to point the jquery ajax call to a local page method or web service to make the server-side call for me...then if I were using linq-to-twitter I'd have to mash together the search results into an anonymous object and JSON serialize it back to the browser...right?
In addition, to solve the rate-limiting issue, it seems like Twitter would like me to make these search requests on behalf of my users, but that will require sending them through the oAuth authorization workflow, and then having to store their tokens somewhere to use every time they load a page that shows the "twitter feed". Right?
Finally, part of the functionality built into the existing application is the ability to store a list of tweet ids and twitter user ids and strip those out of the results (if they are offensive, etc).
My brain tells me that there is no way that a simple task such as "show me all tweets with #whatever in them, except for tweet ids 1111212, and 1356346" will require everything I describe above...
What am I missing here?
Edit to Clarify Question
If all queries to Twitter's 1.1 search API must be authenticated, and using ApplicationOnly oAuth authentication is not an option due to rate-limiting, and we don't want to force users through oAuth to capture their tokens, how are we expected to show lists of tweets from the search API in an auto-update jquery-like fashion?
The only option I've found is Embedded Timelines (unless you want to build your own server-side solution with caching, etc):
https://dev.twitter.com/docs/embedded-timelines
I am trying to find a way to retrieve my own private playlists from my own personal YouTube account via a server side web app built in ASP.NET (C#). Based on the research that I have done, the consensus seems to be that my app needs to authenticate against my account with Oauth 2.0. I want my website to show a list of videos from a few playlists that I have set as hidden, and I want the list to show on a public page. For this reason, I obviously do not want to enter in my youtube account details every time that I browse the page.
I have looked and looked and there does not seem to be any clear way to do this. Some people have suggested going through the Oauth 2.0 authentication flow once, then use the code that it returns in the redirect URL to generate a refresh token, and use that token in your application; another suggestion I have read is to use an API service account. There does not seem to be any working example code available anywhere.
Has anyone had to do this same thing and have you been successful setting it up? Google's own API client library documentation is abysmal, especially for the .NET libraries.
If the playlists are hidden you won't be able to access them without logging in.
If the playlists are public you can always query for them through the YouTube API without having to pass your credentials.
I'm having problems displaying a Facebook feed on a webpage. The purpose is to display the feed of a Facebook Page (http://www.facebook.com/kvaernerasa) on an external page, but I'm missing something.
First of all, I'm using Facebook's own "generator" to create the activity feed box:
http://developers.facebook.com/docs/reference/plugins/activity/
It asks for a domain (http://www.kvaerner.com)...and then what?! I want the feed for a Page, so there is no app id. How will it know what feed I'm asking for? I also need the feed to be displayed without requiring that the users are logged in.
I've managed to display the RSS feed (not styled), but would prefer to use Facebook's own plugin. What am I missing here?
Is the Like Box, as mentioned by TommyBs, the only other option? How have other sites implemented this?
"The Activity Feed plugin shows users what their friends are doing on your site through likes and comments" That's the description from FB. To me that means it doesn't show native facebook page feeds, just information relating to the pages on your site so I don't think it's what you're after
I think what you want is the like-box
https://developers.facebook.com/docs/reference/plugins/like-box/
I have two applications, say app. A and app. B. App A. sends form data (using the post method) to app B. B however, is a web application and uses forms authentication. The post data is send to a webpage (viewdocument.aspx) which is secured by forms authentication. But when the data is send to viewdocument, the login page is displayed because the user isn't authenticated.
The point is, I want the post data to be read by viewdocument. How can I do this?
You can allow all users to access your viewdocument page (by setting authorization in your web.config), get the values of the post in your page load and then, manually do:
if (!User.Identity.IsAuthenticated)
FormsAuthentication.RedirectToLoginPage();
//Else continue with page display
This way, you will protected the display of your page but be able to send data to the page with any user.
I hope it will help
If your web app is only for accept data use web-services.
I think you want to consider separating out the two process - accepting data from another web site, and displaying data to a user. This way the you get nice separation of logic which can improve maintainability. And I'm not sure how you are going to go POSTing data from one website to another as POST should go back to the original webpage. I would do as #Kane suggested in his comment and use a service to accept the incoming data. This could be built to accept the current data, but would also be easily extensible if you ever need to receive data from other sites. Your page for displaying the data would then be a lot more simple and clearer for developers to work on.