Google - This app is blocked

[wheeleran]

Hi Lorenzo. i understand this is still beta, but i'm getting the 'This app is blocked' screen when trying to log in to Google. Backed out, then clicked to recognise the attemot in Google account's security section, but no change. In the settings for MagicCalendar are the Encryption and Encryption IV keys; an i supposed to do something with these? MagicCalandar does have "See, edit, share, and permanently delete all the calendars" privileges, but any attempt to log in in Obsidian just gives me the block screen.

[Vaccarini-Lorenzo]

Hi there,
Unfortunately Google allows free-tier application to host a maximum number of 100 users and the application has been on full capacity for a while now.
I'll have to refactor the logic of the plugin to allow every single user to create their own OAuth credentials. I'd love to give you an ETA but I'm unable to.
I wish you a great day,
Lorenzo

[polyinnovator]

" Unfortunately Google allows free-tier application to host a maximum number of 100 users "

Why don't you just crowd fund or kofi/buymeacoffee to pay for more users. I was so excited to try out a new cal plugin for obsd, only to be hit by this ridiculous issue.

Totally get that spending your own money wouldn't make sense, but this is literally basically the only 2 way sync plugin there is. I'm using the new day planner which at least gets me a 1 way sync, but its not the same.

[livejamie]

Bummed I can't toss you a few dollars to use this

[polyinnovator]

Tbh I would too On Tuesday, May 14, 2024 at 04:31:30 AM CDT, Jamie Martin ***@***.***> wrote: Bummed I can't toss you a few dollars to use this — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[Vaccarini-Lorenzo]

Hi guys!
Thank you so much for your feedbacks, they're really appreciated. I'm sorry for the delayed answers but I've been incredibly busy. I plan to continue the development of the project starting in October.
I believe that a feasible solution for this particular issue would be refactoring the plugin to allow single users to provide their own cliendID & secret. I'll keep you posted.
Thank you once again for your feedbacks.
Lorenzo