-
-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add telegram auth to frontend #1107
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1107 +/- ##
==========================================
+ Coverage 47.91% 48.45% +0.53%
==========================================
Files 136 135 -1
Lines 2980 3042 +62
Branches 667 680 +13
==========================================
+ Hits 1428 1474 +46
- Misses 1542 1558 +16
Partials 10 10
Continue to review full report at Codecov.
|
Pull Request Test Coverage Report for Build 1350074803
💛 - Coveralls |
@Ksinia thank you for your contribution! btw, the code looks good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @Ksinia,
I'd propose a visual design like this
Telegram is a third-party auth provider and I'd expect it in the line with others. Another reason we can't put the full name of the provider on the tabs.
@akellbl4 default mock render wrapper for tests don't set up state and fail because of that, would you be so kind as to look into it? The wrapper needs to be rewritten to inject state as well as other places will benefit from it as well. |
@Ksinia can I pray to you so that you may please finish this feature? |
I wonder, what is your use case and why is one more auth method that important to you? As you probably know, there are many other auth methods currently, and to me TG auth seems like an exotic way to authenticate into remark42. |
Telegram is popular among my target audience, and personally I feel more comfortable giving my or users' data to Telegram as opposed to Google. GitHub is not used by non-developers. Twitter is silly with its account policies. Facebook I don't use, so can't create the integration. And it's one of the worst privacy offenders anyway. So Telegram is the best option really. And I have Google and GitHub active already. |
I'm not really sure what data you giving to google/fb/github in this particular case. Auth works in the opposite way and does not communicate with auth providers outside of the basic oauth(2) flow. In fact, this is google giving users' data (very basic data) to remark42. I mean, remark42 expects users with existing accounts on one of the popular places, and all those places know about the user is known regardless of remark42 usage. btw, if such "anti-social login" is important, you may consider email auth |
yeah, but configuring an email server is kinda hard. it's on my to-do list, but feels like a big deal :)
I guess I misspoke. more accurately I should say I'm reluctant to impose a requirement on my users to have an account with such a service. I appreciate the freedom not to. and also it's a question of which services I depend on (with my personal account they control) to keep my site functioning, comment attribution consistent, etc. I have more trust in the sanity of Telegram than alternatives. and besides there's extra utility: users will be able to subscribe to comment threads with THEIR Telegram accounts, right? Also since we're having a conversation, I was wondering if there's any admin dashboard in Remark42 which I somehow haven't discovered yet? Can all comments be exported as JSON? how? |
see https://github.com/umputun/remark42/wiki/Admin-UI
see API docs: https://remark42.com/docs/contributing/api/ |
Bumps [nanoid](https://github.com/ai/nanoid) from 3.1.23 to 3.2.0. - [Release notes](https://github.com/ai/nanoid/releases) - [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md) - [Commits](ai/nanoid@3.1.23...3.2.0) --- updated-dependencies: - dependency-name: nanoid dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
- get rid of redux store in favor of local state - add tests for telegram happy path - lift auth handling on Auth level
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx a lot!
Cool! Thanks a lot! When do those changes make it to the docker image? They haven't yet, as far as I can tell. |
the image was built automatically. each commit/merge to master triggers the build of a new :master image |
Ok, then please advise. I did docker-compose pull, and :master image is specified in the .yml, but for me the old image has then loaded with docker-compose up. What should I do differently? |
well, something is not right with your compose I guess. I just did this:
as you can see this is a very fresh version built on 2022/02/09 |
check the docks please, here, see telegram section |
I have that. I'm receiving notifications to my Telegram channel, that part works. Auth does not |
yeah, the same here. Just added a bot and allowed tg auth on https://remark42.com/demo/ and nothing good happened |
The current master image has build info |
i have forces rebuild and deployed new :master, seems to work |
actually, it does work, but telegram ui is confusing as hell. @paskal - I think we need to add to docs "press Because I pressed it before I have missed the button the second time |
have you followed the instruction and clicked the link above first? And after this "Start" in tg client? |
let's keep this PR discussion about tg auth issues |
Come to think of it, the |
Fixes #707.