Audit: Sign in with GitHub

[0x4007]

Incorporate a sign in with GitHub button for increased auth limits. Don't worry about styling, I can handle it.

https://github.com/ubiquity/work.ubq.fi/blob/development/src/home/authentication.ts

We should take the sign in with GitHub implementation I made on work.ubq.fi and authenticate as the user for increased rate limits.

How is authentication being handled now?

Originally posted by @pavlovcik in ubiquity/pay.ubq.fi#164 (comment)

[guha-rahul]

The sign in with Github is already implemented. Can u please explain a little more?

[0x4007]

The sign in with Github is already implemented. Can u please explain a little more?

There's no sign in with GitHub implemented on this project.

[molecula451]

if it's going to be refactor i think it's best to focus energy on ubiquity/pay.ubq.fi#174 and move all these tasks there

[0x4007]

This is only needed in the audit app. So actually this issue will be transferred to that repository once its broken off from this one.

[gentlementlegen]

@pavlovcik this should be taken care of after eventually resolving ubiquity/pay.ubq.fi#172
and actually, once this is merged, calls to GitHub API are extremely low since it would only query the repo information, and not all the comments / issues etc, making this issue low prio.

[0x4007]

Priority 1 normal is our lowest priority!

[gentlementlegen]

Partially solved by #5 for the auth limits, since it would just poke the database and eventually GitHub a very little for repository informations.

[0x4007]

Partially solved by #5 for the auth limits, since it would just poke the database and eventually GitHub a very little for repository informations.

Cool to hear. Meaning it solves the rate limit issue but doesn't include the sign in with GitHub button? This should be fine to get some credit for since #5 is technically a different scope

I also realize that the pricing didn't make it over. @molecula451 would you happen to have a record of the priority and time levels for the issues? Can you re add them so that compensation can be distributed?

[gentlementlegen]

Partially solved by #5 for the auth limits, since it would just poke the database and eventually GitHub a very little for repository informations.

Cool to hear. Meaning it solves the rate limit issue but doesn't include the sign in with GitHub button? This should be fine to get some credit for since #5 is technically a different scope

I also realize that the pricing didn't make it over. @molecula451 would you happen to have a record of the priority and time levels for the issues? Can you re add them so that compensation can be distributed?

Correct, because we don't require any login to access our database, and we have no rate limit. Now the ratio would be one hit to GitHub API per repo audited, so if you audit 5000 repositories within an hour you might hit the API restrictions. Could still be a nice to have, but not very likely to happen is it?

From the GitHub docs REST API

All of these requests count towards your personal rate limit of 5,000 requests per hour. Requests made on your behalf by a GitHub App that is owned by a GitHub Enterprise Cloud organization have a higher rate limit of 15,000 requests per hour.

[molecula451]

I also realize that the pricing didn't make it over. @molecula451 would you happen to have a record of the priority and time levels for the issues? Can you re add them so that compensation can be distributed?

Yes, this was the actual price label:

[molecula451]

i can bump if anything, tho

[ubiquibot]

@FernandVEYRIER the deadline is at 2024-03-05T07:24:10.251Z

[ubiquibot]

+ Evaluating results. Please wait...

[ubiquibot]

[ 30.2 WXDAI ]

@pavlovcik

Contributions Overview

View	Contribution	Count	Reward
Issue	Specification	1	6.6
Issue	Comment	4	23.6

Conversation Incentives

Comment	Formatting	Relevance	Reward
Incorporate a sign in with GitHub button for increased auth limi...	6.6	1	6.6
> The sign in with Github is already implemented. Can u please e...	2.2	0.04	2.2
This is only needed in the audit app. So actually this issue wil...	5	0.105	5
Priority 1 normal is our lowest priority!...	1.4	0.43	1.4
> Partially solved by https://github.com/ubiquity/audit.ubq.fi/i...	15	0.53	15

[ 45.6 WXDAI ]

@FernandVEYRIER

Contributions Overview

View	Contribution	Count	Reward
Issue	Task	1	25
Issue	Comment	3	0
Issue	Comment	3	20.6

Conversation Incentives

Comment	Formatting	Relevance	Reward
@pavlovcik this should be taken care of after eventually resolvi...	-	0.275	-
Partially solved by https://github.com/ubiquity/audit.ubq.fi/iss...	-	0.555	-
> > Partially solved by #5 for the auth limits, since it would j...	- code: count: 1 score: "0" words: 0	0.63	-
@pavlovcik this should be taken care of after eventually resolvi...	5.2	0.275	5.2
Partially solved by https://github.com/ubiquity/audit.ubq.fi/iss...	3.2	0.555	3.2
> > Partially solved by #5 for the auth limits, since it would j...	12.2 code: count: 1 score: "1" words: 0	0.63	12.2

[ 4 WXDAI ]

@molecula451

Contributions Overview

View	Contribution	Count	Reward
Issue	Comment	3	4

Conversation Incentives

Comment	Formatting	Relevance	Reward
if it's going to be refactor i think it's best to focus energy o...	2.7	0.2	2.7
> I also realize that the pricing didn't make it over. @molecula...	0.7	0.715	0.7
i can bump if anything, tho ...	0.6	0.105	0.6

[ 1.5 WXDAI ]

@guha-rahul

Contributions Overview

View	Contribution	Count	Reward
Issue	Comment	1	1.5

Conversation Incentives

Comment	Formatting	Relevance	Reward
The sign in with Github is already implemented. Can u please exp...	1.5	0.21	1.5