Does anybody know if there's any way of using standard Facebook Messenger features like quick replies, buttons or templates from Facebook Channel (Beta) via Programmable API?
As it is right now it seems too limited to be of any use beyond simple text conversations; no prefilled answers, no links to actions or products...
Are there any (short term) plans to support it? (just being able to send a json like in Facebook own API would be more than enough https://developers.facebook.com/docs/messenger-platform/reference/buttons/quick-replies)
Right now, you are right that the integration is relatively simple.
What you want to look out for is the Twilio Messaging Content API which is currently in pilot. The Content API is intended to make rich messaging across any of the channels that Twilio offers easier. The Content API will wrap each of the channels, making it straightforward to add buttons, actions or prefills to messages over channels that support it, with fallbacks for simpler channels (like our old friend SMS). The API is in pilot right now, but you can register your interest and request access here.
Related
I was wondering, is it possible for us users to know if a website uses server-side tracking?
For example, tracking to send events to Facebook, Google Tag Manager, etc.
Are there any indicators or tools we can use to find this out?
I am not talking about the public graph api, i am asking is it technically possible to consume facebook's private api that facebook official apps use, and benifit from login/sign up and such features?
Like if i reverse engineered messenger or facebook app and mimic their communication with their API, whould i be able to build a working client?
Thank you.
There are existing projects that have already done the same.
Take a look at the works of dequis e.g. purple-facebook. He has also written tutorials on reverse-engineering the APIs of Facebook Messenger and WhatsApp.
Take a look at the source code of the Facebook protocol plugin of Miranda NG. They reverse-engineered the API used by the desktop web frontend of Facebook.
They exist for years. None of them have been sued so far. However, hiding your identity is recommended if you plan to do such things. Also you may want to open-source your project and host it on multiple sites. Corporate arrogance of tech companies is at very high levels nowadays.
Yes, it is theoretically possible.
However, remember that you will be easily sued if Facebook do not agree with what you're trying to do. For example, if you're trying to use their own private Intellectual Property without their permission, or if you violate their Terms of Service agreements (reverse-engineering is going to be in there without a doubt), then they can legally sue.
Facebook have public APIs with documentation which is what is intended to be used by developers. If you decide to ignore it and go digging into things which you do not own, nor have consent to access, you're going to land yourself into trouble.
I don't mean to be a kill-joy, I'm just saying how it is from a realistic point-of-view.
I've found a few really old answers that do not work. I am building a website for my church. What I want to do is have a feed that shows events from Facebook, that way when the lady that does our social media adds an event it will automatically post them to our website. This will keep the website easy to maintain. Besides paying for a plugin, what is the best way to go about this?
Yes, I know you can embed events. But I am trying to keep it as easy as possible for people at my church who are not really techie or know how to design websites. Please help.
I am using squarespace and the website is ccodtruth.org
I'm creating a website and I would like for users to be able to log in with more common accounts like Google+, Facebook, Twitter, LinkedIn, etc. How would I achieve this? Is there any language that makes it easier to achieve this?
The companies you mentioned, Facebook, Linkedin, Twitter, etc. have API's ready-made to help you achieve this. Visit this link to look at facebook's
https://developers.facebook.com/docs/facebook-login
They also have some rules that apply (how many requests per minute, etc.) and may want you to pay if you exceed the limits they set forth.
As for the language: Javascript if probably your best bet for connecting with API's. There are other languages that will allow you to do this as well, but if you run into problems along the way, you will find more people who can help you if you are using Javascript because it is the most common.
Jquery (a Javascript library) will enable you to use AJAX to connect with API's, but this is just one example of the many options you will have available to you if you use Javascript.
No special language needed. You should simply use the "API's" of each social network. They all come with good documentation.
Else if you don't wanna put your hands in the engine, you could also use an automated solution like social login and registration tools
I want to build a mobile application that allows end users to sign up and participate in events (like parties, seminars, conferences etc..). Instead of building a CMS from scratch for an administrator to manage events, is it possible to use Facebook Events as the CMS? Then my mobile application will pull information about these events via the Facebook API.
Any one know if it's better for me to build the CMS from scratch or to use FB events? And what are things I have to consider in making this decision?
Let's say events are authored by users of the system, and if we go the FB CMS method, then users MUST have a Facebook account.
This is certainly possible with the events Facebook api. If you wanted all the events associated with an account you own, you could embed an access token into your application. If you want people to accept your event or host the event under their own account you would need to prompt users for permissions to manage events on their behalf.
It's pretty subjective question whether this is a good idea and it depends on what you are trying to achieve. The biggest upside is that its already built for you and designed to scale and wouldn't require servers, etc. The biggest downside I see is that Facebook changes their API and its not always the most reliable (see the always growing bug list they keep). Also, users may need an account depending on how you decide to implement the functionality.