I have been using the recommended API; https://github.com/Inumedia/SlackAPI however there is a problem, some channels created as public and then made private don't appear either as channels or groups. Supposedly the answer to this is to use the new Conversations API that allows access to all channels/groups through the same methods. The problem is that the c# api doesn't support this. Does anyone know any other c# api that does, or are there any plans this semi-official one will support it at any time soon?
Related
We are migrating from BotFramework-Webchat v3 to v4. Usually we send a message from the chat through the directline object created from v3 BotChat using the directline.postActivity function. However in our v4 implementation there were issues with the behavior of messages shown in the chat window when posting activities like this.
It seems that sending messages through the webchat redux store as shown in this example is the recommended approach.
I am wondering what is the difference between these two usages? It seems something is different between v3 and v4 versions and I am having difficulty finding references in the documentation about this. Should directline.postActivity be avoided completely?
It isn't documented anywhere, but best practice is what is demonstrated via the samples, by use of the Web Chat redux store and its list of available actions.
Essentially, Web Chat v4 is built on top of BotFramework-DirectlineJS which does use observables. Web Chat then translates the Direct Line observables into its own methods for consumption internally and by the user.
As you noted, it is possible to use the Direct Line observables in Web Chat but it is neither the best method nor the best practice to do so. Primarily, because Web Chat wasn't specifically designed around their use, except internally. It can work, but it opens you up to potentially curious behavior.
Is there a way to scan website to detect not documented public/non-public web api methods?
I'm developing a tool where I use non public API, i.e. API protected by public/private key.
I suppose their documentation is not updated well and there are more methods than described in documentation.
I wondered whether it is possible to discover non documented api methods that might already exist.
p.s. I understand consequences of using non-documented api..
When searching in Yammer it uses an /api/v2/search endpoint like this:
https://www.yammer.com/api/v2/search/models?search=test&start=0&size=20&model_types=threads&_network=xxxxxxx&relevance=DEFAULT
Compared to the v1 search endpoint this returns more data. We need this data. And we successfully tested using this v2 endpoint.
Now the question: Is this v2 search endpoint safe to use? Is it "official"? Maybe somebody from Yammer reads along - on their Help page it says:
We encourage you to post all programming questions to StackOverflow
with a #yammer hashtag
So here we are. Any help is appreciated.
The Yammer v2 search API endpoint is not yet officially supported for third-party use. This is because we anticipate the need to make changes to it as we build it out. There are no plans to lock developers out of experimenting with the v2 search API. However, when developing any important functionality against this API, automated testing should be used to detect any unannounced breaking changes that we make while we continue to build it out.
Currently, I have been tasked to utilize the Google People API to ask for a user's basic Google information along with their public phone numbers. So far the results have been positive.
The solution my team and I have incorporated the Google People API integration in has the capacity to be utilized across thousands of domains. As a result, my question is simply, How can my team members and I ensure that any our clients that utilize our solution with their own particular domain get our new functionality built with the Google People API?
Keep in mind, our clients have the flexibility to have http/https and any subdomain on their site. Entering each domain possibility for our client base one by one would not be an easy task. I'm seriously hoping there is a solution around the single, explicit origin entries.
Thank you for your time and help.
Warning:
You must remember that if this is source code you are giving your clients that you are not allowed to release your client id and client secret. This includes plugins and scripts.
On November 5th 2014 Google made some changes to the APIs terms of Service.
Asking developers to make reasonable efforts to keep their private
keys private and not embed them in open source projects.
So if your clients could view the code of your application and see your client id and secret you should not be giving it to them.
Read more about this issue Can I really not ship open source with Client ID?
Recommendation:
The best solution for you will be to instruct your users now to create there own project on Google Developer Console and create their own JS origins.
You may just have to provide your own wrapper around the target API where you authorize the client request yourself and then do the request from Google using your own credentials.
Hello I am currently writing a native SoundCloud application for OSX. In order to write that application I need an object oriented wrapper that gives me the SoundCloud data in form of objects. Now I have several questions regarding the api:
Users are allowed to forbid access to their songs via third party applications, I guess this a protection to avoid that the songs are downloaded, are there made any exceptions for third party developers?
SoundCloud itself is not only using the public api but also some other private api's, am I allowed to use them if I arrange it with you(with the api-team)? (The reason why I am asking that is that the public api is not reflecting all data for example the me/activities endpoint does not reflect the user that reposted a song.)
If no, will you allow it in the future?
With private api's I mean endpoints that are hosted under the url api-v2.soundcloud.com
Thank you in advance for an answer.
Artists can forbid access to tracks for third party apps which was the reason why I didn't get any tracks for the playlist.