Is it possible to load the profile picture/name of the currently logged in Disqus account in your .NET MAUI application?
if so, how do you do it?
I have been trying to do it for a while now but I keep finding websites that USE Disqus instead of telling how to implement it.
Related
I'm looking for developing a website that should allow my clients to update and edit the contents of the website. Is it better to use CMS or develop an interface?
I've tried working with Wordpress.
Getting a few ideas for developing a Website that allows Client engagement in site activities.
Documentation on the net seems to be VERY scarce. The only option I can think of at the moment
is to have my SPA app break convention and to have the (initial) logged out page be different to the logged in one (eg my app).
My app is built using Durandal 2.0.0.
In one of my OAuth tests app's I've managed to implement this link successfully. But as Durandal does not work in the same way (Server-side controller, & razor views), I'm thoroughly confused in how to achieve what I want to.
I'd like to have my app remain a single page app. But I've got little to no experience with the OAuth SDK
My only requirement is that the user log into my app using his FB account.
I've had an initial stab at this using the FB java script API, and got it working, but after discussions with another developer this side, it doesn't seem like the purpose of the java script API is to facilitate secure application login's? As the way we had it, would allow any user to pass a valid fb userId, then he would be logged into our app. :/
How would I go about achieving this process flow in a Durandal/Web API Single Page App?
User logs in using fb ->
then on the server we get his fb userId ->
retrieve our internal appID
I'm not asking for a complete answer/for someone to do my work....
But any documentation to get me started/less confused would be greatly appreciated.
Here is a sample project which demonstrates how to use OAuth with Durandal and Web API:
DurandalAuth.
However there are some modifications in viewmodels needed, since router changed in Durandal 2.0.0.
I am using ASP.NET and Web Tools 2012.2. I created a Facebook application under ASP.NET MVC 4 Web Application and target of .Net Framework 4.5. I can create an AppId and AppSecret
through https://developers.facebook.com/apps but the application requests a value for Facebook:VerifyToken:User. Exactly how do I create one and get the application to work?
The "Facebook:VerifyToken:User" setting in the project template is optional and is used in the UserRealtimeUpdateController. You only need to set this when your application want to support Facebook Realtime Updates. See this link for more information about the realtime updates: https://developers.facebook.com/docs/reference/api/realtime/
The VerifyToken is set by you when you create a realtime update subscription.
Hope this helps,
Yao
You can use either DotNetOpenAuth or the Facebook C# SDK to authenticate against Facebook and request an access token. Take a look at the FacebookClient in DotNetOpenAuth, I've successfully used this to request an access token. You will need to pass the right scope parameter across for the permissions you need. Could you elaborate on how your app needs to interact with Facebook?
I gave a value for the Facebook:AppNamespace setting (which is supposedly optional according to the literature that I have read as well as stating so on the Facebook form). Once I did this, the problem went away.
I have implemented the sample application provided by DotNetOpenAuth as instructed here.
As you can see below, this is requiring that the user installs this facebook application.
I simply want to allow users to use their facebook login for my vanilla ASP.NET website.
Is there some way to prevent them from having to install a facebook application?
Update: Stackexchange Facebook login doesn't have an "install" button. It simply has a dialog requesting various permissions. This is much preferred in my case.
This will work until Facebook forces everybody to use the "Enhanced Auth Dialog"
You can fix this dialog by going into your advanced application settings:
Changing this setting will cause the dialog to appear as you suggested in your excellent question.
Im new to facebook applications. I recently created a webapp that consisted of html & php. But recently Ive decided that integrating my webapp within facebook would be useful. Any tips on where to start? Ive looked over developers.facebook.com and im confused. It appears they are in the process of updating. Ive come across a few guides but there from a few years ago. This app will run completely within facebook and im probably gonna have to rewrite all the code. Any guides or suggestions?
Thanks!
You didn't specify the programming language you're using but if you're developing asp, start by looking into Facebook c# sdk here: http://facebooksdk.codeplex.com/
If you're using any other language (i.e. php), try looking into respective software dev. kits (i.e. facebook php sdk). They will facilitate your job in comparison to starting raw development all by yourself.
Tim, if you want to get into the business of working with Facebook, you need to know right away that they are always in the process of updating. That being said, you should learn some Facebook terminology so you can do more research and figure out what you want to do.
Applications that run within the Facebook interface are called Canvas Apps. Your application is hosted on your own server, and Facebook simply adds an iframe in their UI that points to your app's URL.
Another way to go to create a webapp that uses your own design, but still utilizes a single sign-on system from Facebook. This used to be called a Connect App but now they don't really have a name for it. Basically, you can use Facebook's authorization system to pull Facebook user data into your own database, which basically eliminates the need for a registration page. The authorization system prompts the user to allow your app to get specific data about them - once they authorize it, your app has access to do whatever the user gave it permission to do.
The best document to wrap your brain around is about authentication: http://developers.facebook.com/docs/authentication/
Give that a whirl, and good luck!