Is it possible to transfer a Flurry app from one user to another user?
Related
I am trying to create a website that checks if the current logged-in user is subscribed to a specific youtube channel. This is meant to restrict the user if they haven't yet. Is something like this even possible?
You would need the user to login via google identity services to be able to access data like that via the api. The api gives you access to the channels the user is subscribed to if the user allows this
I am building an app utilizing the MERN stack (MongoDB, Express.js, React/Redux, Node.js) where there will be three user account types: Client, Company, Admin.
Client account can search and partner with Company accounts where they can submit orders.
Company account will be a paid subscription (via Stripe) where they can complete orders submitted by client accounts.
Admin will be an interface to view all users, orders, etc..
I am trying to determine the best approach for create multiple user account types in Mongo. I assume there will need to be two different registration forms. I'd like a single login form that will determine if an account is client or company and display relevant information based on their role.
Looking for input on the best/most scalable approach for this.
We have a bot service running in MS Azure and a corresponding Teams app. This bot service is used by multiple customers. Requirement is to allow customers to change the bot name/icon that is shown in the Teams chat (please refer image below).
We can change the name and icon by changing it in the Teams App. However, this will require creating a separate Teams app for each customer. Is it possible to control this via the bot service code running in Azure? We want to do it programmatically based on logged-in user's domain. Is there anyway to do it?
Edit: Found a related post
Thanks
Vivek
This is not possible within a single bot - it's set at the level of the the bot registration, in Azure, and so can't be changed tenant by tenant in Teams, for example. You'd need to create a bot for every customer (tenant), or go with a generic name and image. You can of course customize the welcome message, responses from the bot, etc.
I'm currently toying around with the Spotify api to create a mobile app that "matches" people based on their top artists, tracks, and genres.
For this, I need to save the user data (top 50 tracks and artists, from the Personalization API) and fetch them back as needed.
So basically if User A signed in the app with its Spotify account, its data is saved in my DB.
After that, if User B wants to see if he is a match with User A the server will provide information about both User A and User B, for instance, what artist they both like.
There is this point in the TOS about user data:
"Spotify user data can be cached only for operating your SDA. If a Spotify user logs out of your SDA or becomes inactive, you will delete any Spotify Content related to that user stored on your servers. To be clear, you are not permitted to store Spotify Content related to a Spotify user or otherwise request user data if a Spotify user is not using your SDA"
As far as I understand, it's ok to save the user data in an external server/DB as long as I delete that data as soon as the user logs out from my app, is that right?
I'm asking because at the same time there is this restriction stated in the TOS:
"Do not transfer Spotify Content to unauthorized third parties, including (i) directly or indirectly transferring any data (including aggregate, anonymous or derivative data) received from Spotify to, or use such data in connection with, any ad network, ad exchange, data broker, or other advertising or monetization-related toolset, even if a user consents to such transfer or use; or (ii) to another music service that competes with Spotify or the Spotify Service."
I want to send web push notifications to registered users, are there any best practices on how to implement the cases when multiple users have access to the same device and one should not see the message of another user.
Thanks in advance.
A web push notification subscription is tied to the browser, not the device.
What you need to do is, map this id with your registered user when he logs in from a particular browser. Also, you need to remove the subscription id mapping with any other users in the system.
In the case of multiple users using the same browser, the above logic will make sure that at a time, a particular browser subscription id is linked only to a single user.
And when you want to send a notification to a registered user, you can retrieve all push subscription IDs linked to this user in your database, and trigger notifications to those subscription IDs.
And don't forget to unmap a subscription id when the user logs out from a browser. Otherwise, he will continue to receive all notifications even if he has logged out.