In Web.Whatsapp you can chat with your mobile phone contacts using wifi, even when your phone is not online. However when I first looked in to how a webapp like whatsapp 'posts' your send message (or receive incoming) I did not notice any form of outgoing requests, posts / get requests etc on my chrome / firefox developer tool.
The developer in me would like to know how whatsapp sends my messages to the server without me seeing that in the network area. If whatsapp interacts to the server on a different way i would love to know whether that part is visible just like in 'network'.
other site where I can not see network interaction is for example:
youtube when posting an comment or giving a like
Related
I'm building a web application that performs an analysis based on the inputs a user enters. I want to allow the user to send this analysis, which will be 2-3 sentences max, to one or more of their Facebook friends through the messenger platform.
At first I thought the Send Dialog was the way to go, but it appears I can't pre-populate the message field at all (source).
Next I tried integrating the Messenger Platform but this appears to target businesses that want to connect their site to a Facebook Page and setup a chat bot, which seems far too complex for my use case.
Is there anyway I can allow the user to send a private message to one or more of their Facebook friends or is this not possible for a specific reason (e.g. prevent spam, security concerns)?
This SO question here appears similar to my question.
There's no way to do this unfortunately. Makes sense, however, as apps could spam people's imessenger if it was possible.
The best alternative is to use the Send Dialog component.
I am trying to create an application that will basically be a Linux command line messenger app just for Facebook chat. When you connect to facebook chat using the XMPProtocol, you can send instant messages to all of your friends but you can only see the messages from the friends that appear online. If an offline friend sends you a message, you do not see it. I have tested this with various chat programs (like pidgin) that are using XMPP to connect to facebook chat.
There is an iPhone app called "Messenger" that allows you to send and receive instant messages even when your friends appear to be offline. How is this possible? Do you have to use some other protocol? I tried making a research about this, and while there were many references about XMPP basically having this limit, there was no reference about how you solve this problem. I'd appreciate any clue regarding the direction I should look (may that be just the name of a protocol, an open source project that has this feature etc).
chat and inbox are two faces of the same Facebook backend ...so i mean you can read message sent by your Facebook friends by Graph Api http GET as this ... https://graph.facebook.com/me/inbox?access_token=xxxxxx
I am having a strange problem while making app requests. I understand that when an app request is made through my app, it also puts a notification in the top saying so and so has sent a request from this app. Now, while I can successfully make the request, the bookmark count goes up but I do no get a notification at all. Is there something i could be missing? I'm following instructions from this blog post on Facebook developer site - http://developers.facebook.com/blog/post/464/. I am new to Facebook development so if it's something simple, please point me in the right direction.
Thank You.
I've had issues with this in the past but it looks like Facebook have very recently acknowledged this and brought about correcting the issue.
http://developers.facebook.com/blog/post/540/
App to User Requests now display messages
Previously, when apps sent notifications to users (available by posting a request to the apprequests connection of the User Graph object, as documented in Social Channels), the bookmark counters were incremented, but the message included with the notification was not shown. As of this week, if you send an app to user notification, we will also display the notification message in the apps or games dashboards. This provides app developers a more effective way to communicate application-level updates to users. Note that the ticker count is now shown in bookmarks, hovercards and, for games, in the games ticker. As a result of this change, your users may see an increased number of notification messages from your application.
I have a web app, which runs locally, to interface with Facebook. That is, my app would write to the current user's Facebook wall. It worked for me using Firefox 3.6 and Chrome 10, but I have one test user who said it didn't work for him, and he didn't even get to the [Allow] and [Not Allow] screen, and yes, he was using Firefox as well. What could prevent Facebook from processing the request from an identical app (same code)?
and would anyone want to give it a try?
Are you using popups to show the "[Allow] [Not allow] screen"? May be your test user "just" forget to enable the popups on facebook domain. The problem is, my clients experience that, 90% of visitors not allow popups, so the auth process just stops, and no error message has been generated.
I'm trying to understand this concept but I don't get it yet. I'm new to mobile connections.
How do mobile apps and/or clients connect to the internet, if they do? if not, then, how do they serve real time data from remote servers (like twitter, fb) etc..?
I've heard that mobile apps don't require internet connection but I'm confused because I don't know how they get the data from the servers of twitter or fb or any application.
For example m.facebook.com is a site so it'll only work with some type of connection on a mobile, but with the app.. what happends (how do all of a sudden you don't need internet connection to serve the data from their servers)????
Think of a Web browser. It's an app that issues HTTP requests over the 'Net and interprets the response by rendering HTML and images, running scripts, etc. Now, there's nothing magical about the browser; it's just a program with HTTP capability.
Any other app can do the same. Except it does not have to interpret the response like the browser does. An app can just as easily issue HTTP requests and do stuff to responses. That's how Facebook, Twitter etc. client work. They normally work, however, not with user-facing parts of the target site, but with software-facing bits (called "The API").
Not all mobile apps require or use the Internet. Most games, for example, don't. But the apps that interact with websites, like Facebook, do.