Rainmeter Gmail WebParser failing - rainmeter

Rainmeter Gmail path pattern is like so
https://[your Gmail user name]:­[your Gmail password]#gmail.google.com/­gmail/­feed/atom
yet i put my credentials in specified locations in RainMeter (all themes are the same end result for me) and I am getting a fatal error. Does this have to do with special characters in the password field? I've tried encoding them myself such as space is %20 and so on. any ideas why the feed is not coming through

I think I'm "a bit" late, but I will answer anyway. From my experience, you need to create a password for app (in this case, the web parser) from Gmail control panel. How to do this here. After that, you should be done.

Related

No access to partner - Information could not be retrieved

Here is my full error:
Information could not be retrieved. Please contact iandevice to verify that your account has been properly set up. You may need to add the developer email address as a home member in the Google Home app settings.
I have seen several similar questions, but their solution did not help me. I've followed this link to setup: https://developers.google.com/nest/device-access/get-started but got the error when authorizing my account.
My email address is a personal gmail account. I have checked that my email address in the device access console (Top Right) is the same account that is linked to my nest. I have tried several solutions like re-creating the whole GCM project, credentials, etc, or trying with another gmail account.
I have also ensured that my account is added in my Google Home App, tried adding another account and trying but it's the same. Completely lost here after trying everything, does anyone have a solution to this? Thank you.
Just to add on, I have also checked in the OAuth consent screen that I have the same email address listed under email and developer's email. Also tried deleting the whole home and creating a new one, and link my nest to that h ome

Username formatting issue when using Spotify API + RSpotify gem

I'm running into a strange issue with the Spotify API, specifically the Playlist search (using RSpotify::Playlist.find()). I'm providing a playlist ID and the owner's ID, but in some cases the owner's username has characters that require escaping.
This user for example: https://open.spotify.com/user/andy%3F%21
Their username is andy?!, which, when escaped, turns to andy%3F%21. However, when I try and retrieve one his playlists using the Playlist search, I'm getting a 404 error, Invalid username. I've triple checked, and I'm definitely providing the escaped character version of the username (using CGI.escape).
I also tried going to the Spotify Web API Console and andy%3F%21 works correctly there. Is this some bug with the RSpotify gem?

Is there a way to change a Google Account name/email?

I have ran into a problematic situation, which I really hope I can get help with.
I'm working on Jive Software solutions and we have a product that integrates Google Drive and Gmail.
This integration product was once part of a startup that was acquired by Jive and as such, the Google api project we are using for the integration belongs to a Google Account of a specific person which no longer works in Jive (we do have the credentials for the account though).
The problem is, that we want this account to be ours, i.e, a Jive software one.
So, one option I have, is to create a new account and replace the api account I'm using in the code to use the new one. This is bad, as it will break all the current authenticated clients, and will force them to take the oauth process all over again.
The other option I see, is to convert the existing Google account we are using to a jivesoftware one, so it will not be associated to any specific person but it will still be the same account.
Specifically I'm interesting in changing the Name and Email of this account.
Any suggestions of how we can achieve that?
A third option could be moving the api project to owned by another google account, but I couldn't find such an option in the UI, any clue?
There is no way to change a gmail address. You can forward all email to a new address with the name and email address you would like though.
This way you access all the email from an account that is a Jive software one but it is being forwarded from the old one still. However no one directly accesses the old one.
Check out https://support.google.com/mail/answer/10957?hl=en for more info.
According to the documentation, if you use Gmail with your Google Account, it's not currently possible to change your Gmail username after you've registered. with your username being the full email address you used to create your account. You can, however, change your nick name by going to https://myaccount.google.com and clicking Personal Info.

Is there a way to generate a login token for a Magento admin_user?

We have merchants logged in to a system, from which we want to link them to our Magento instance with some kind of admin token that will log them in directly without them having to manually login.
I see the rp_token field in the admin_user table but that appears to be related to a password reset, which probably isn't what we want.
Have done a bit of searching, found this thread which is related but is dealing with secret keys specifically (which will probably be my second challenge to resolve after resolving this one).
I'm guessing this isn't supported in core, but maybe there's a good extension out there to do it?
Or if not, what would be the best approach to implement? I'm guessing there is probably an event I could hook to look at a GET or POST param (which maybe could be a hash of the username and hashed password), then bypass the normal login() method which relies on username and plain text password.
That feels like it could be a little risky though? Any thoughts?
That feels like it could be a little risky though? Any thoughts?
This is extremely risky, but it can be done safely. I can speak on a similar issue I had in developing QuarkBar, an administration bar for Magento that is set to release this weekend.
So to show the bar, I need to verify the admin is logged in. Unfortunately that's hard to do on the frontend module, since there are two separate sessions. So to get around that I've created a quarkbar_session table. I use OpenSSL to store a secure crypt key once an admin is logged in, that I then check for on each request and match it to a cookie. If it matches, the admin is verified.
It's a little different from what you want of course, since I first set the key when the admin is logged in (it's an observer event). But it should get you started.
Source (NOT ready for production, use it for ideas): https://github.com/zschuessler/QuarkBar/tree/master/app/code/community/Zaclee/QuarkBar
Also, note that I'm storing the secure key so that I can access the admin backend. The solutions in your link say to disable it. You don't have to, check out QuarkBar for implementation.

Why do websites ask me to enter email address and password again

I was just looking for a todolist service over the net. I encountered this tadalist site http://tadalist.com/. Now I was making an account for myself. On this page it asked me to enter email address again and password again. Many sites where I have created an account this thing is done of asking the user to re-enter details.
I don't get the purpose of specifically asking the user to enter email address or the password or any other field.
I can always copy paste and get through this field's duplicate. Why do they have such a thing. As I see it we need to do client side validation for correct entries which is really unnecessary operations as I see it. Why is it done? Pretty sure there's good enough reason for it.
its to make sure that you don't have typo in your password or email address.
imagine that you had a typo on your password, you won't be able to login to the site anymore, unless you reset your password.
its same for email. if you make a typo in your email address, potentially your details can be sent to another email address.
its not good idea to copy and paste in this kind of situation. its better to type them again to make sure they are entered correctly.
I'm pretty sure the idea behind making you repeat emails is to reduce input errors. When you input your email, you might make a typing error. Forcing you to slow down and look again at what you typed will presumably lower typos, even if you don't retype and just copy and paste. For passwords, you can't see what you type, so retyping will definitely help there.

Resources