github.com signup requires running nonfree software (thus, so does contributing to gitea for some people) #4467

New Issue

GiteaMirror · 2025-11-02T05:51:52-06:00

GiteaMirror commented

2025-11-02 05:51:52 -06:00

Originally created by @ian-kelling on GitHub (Dec 9, 2019).

Repro:

Without running javascript and without being logged in to github, go to https://github.com/join

The page says

"GitHub requires JavaScript enabled during sign up, for our signup captcha. Please enable JavaScript during sign up."

Viewing source, there are various nontrivial obfuscated nonfree javascript
files that the page wants to run, such as
https://github.githubassets.com/assets/frameworks-ef488d77.js
and https://cdn.arkoselabs.com/fc/js/e7231a6fd0dc61598e252fe084a804ef/standard/funcaptcha_api.js

For background on this issue, please read

https://www.gnu.org/philosophy/javascript-trap.en.html

This seems to be more reason to move forward for Gitea to self-host itself, issue #1029

I would have made this a comment there, but its not open to comments from the public.

Originally created by @ian-kelling on GitHub (Dec 9, 2019). Repro: Without running javascript and without being logged in to github, go to https://github.com/join The page says "GitHub requires JavaScript enabled during sign up, for our signup captcha. Please enable JavaScript during sign up." Viewing source, there are various nontrivial obfuscated nonfree javascript files that the page wants to run, such as https://github.githubassets.com/assets/frameworks-ef488d77.js and https://cdn.arkoselabs.com/fc/js/e7231a6fd0dc61598e252fe084a804ef/standard/funcaptcha_api.js For background on this issue, please read https://www.gnu.org/philosophy/javascript-trap.en.html This seems to be more reason to move forward for Gitea to self-host itself, issue #1029 I would have made this a comment there, but its not open to comments from the public.

GiteaMirror added the issue/duplicate label 2025-11-02 05:51:52 -06:00

GiteaMirror closed this issue

2025-11-02 05:51:52 -06:00

GiteaMirror commented

2025-11-02 05:51:53 -06:00

@lunny commented on GitHub (Dec 10, 2019):

The moving is on the process.

@lunny commented on GitHub (Dec 10, 2019): The moving is on the process.

GiteaMirror commented

2025-11-02 05:51:53 -06:00

@techknowlogick commented on GitHub (Dec 10, 2019):

Closing this as #1029 is about the move, and the move is ongoing.

@techknowlogick commented on GitHub (Dec 10, 2019): Closing this as #1029 is about the move, and the move is ongoing.

GiteaMirror commented

2025-11-02 05:51:53 -06:00

@GitMensch commented on GitHub (Jul 8, 2020):

@lunny: I'm asking for an update (here because the other issue has discussion locked) - seems like everything on the todo-issue has been solved but the migration of this repo itself, and previous repos were migrated already.

... so - can we expect the move "in the next weeks" or is there a blocking issue not listed there?

@GitMensch commented on GitHub (Jul 8, 2020): @lunny: I'm asking for an update (here because the other issue has discussion locked) - seems like everything on the todo-issue has been solved but the migration of this repo itself, and previous repos were migrated already. ... so - can we expect the move "in the next weeks" or is there a blocking issue not listed there?

GiteaMirror commented

2025-11-02 05:51:53 -06:00

@lunny commented on GitHub (Jul 9, 2020):

@GitMensch I think all the feautures are ready to move, but it's failed because of network reason. The gitea repository will spend about 80GB disk space.

@lunny commented on GitHub (Jul 9, 2020): @GitMensch I think all the feautures are ready to move, but it's failed because of network reason. The gitea repository will spend about 80GB disk space.

GiteaMirror commented

2025-11-02 05:51:53 -06:00

@jondo commented on GitHub (Jul 9, 2020):

What is taking all that space? Binary blobs? Is a history cleanup necessary?

@jondo commented on GitHub (Jul 9, 2020): What is taking all that space? Binary blobs? Is a history cleanup necessary?

GiteaMirror commented

2025-11-02 05:51:54 -06:00

@lafriks commented on GitHub (Jul 12, 2020):

@jondo mostly binaries that are attached to releases

@lafriks commented on GitHub (Jul 12, 2020): @jondo mostly binaries that are attached to releases

GiteaMirror commented

2025-11-02 05:51:54 -06:00

@jondo commented on GitHub (Jul 12, 2020):

Ah, I understand! The git repo itself is just about 180 MB. What about simply keeping older binaries downloadable here and just copying the most recent ones over?

@jondo commented on GitHub (Jul 12, 2020): Ah, I understand! The git repo itself is just about 180 MB. What about simply keeping older binaries downloadable here and just copying the most recent ones over?

GiteaMirror commented

2025-11-02 05:51:54 -06:00

@GitMensch commented on GitHub (Jul 13, 2020):

I think the suggestion of @jondo is very reasonable, especially when this is all that prevents the move to self-hosting!
@lunny @lafriks What do you think about this? What do you think about reopening either this issue, creating a new one for "the last step to be done" (obviously other then migration is change in documentation, site, and announcement) or reopen discussion at #1029?

@GitMensch commented on GitHub (Jul 13, 2020): I think the suggestion of @jondo is very reasonable, especially when this is all that prevents the move to self-hosting! @lunny @lafriks What do you think about this? What do you think about reopening either this issue, creating a new one for "the last step to be done" (obviously other then migration is change in documentation, site, and announcement) or reopen discussion at #1029?

GiteaMirror commented

2025-11-02 05:51:54 -06:00

@lafriks commented on GitHub (Jul 15, 2020):

We need to merge this PR #11387 and migrate gitea.com to use minio for storing attachments first

@lafriks commented on GitHub (Jul 15, 2020): We need to merge this PR #11387 and migrate gitea.com to use minio for storing attachments first

GiteaMirror commented

2025-11-02 05:51:55 -06:00

@lunny commented on GitHub (Jul 18, 2020):

I also send another PR #12244 to try to resolve the network problem when migrating from github to gitea.com since the total gitea repository will spend about 80GB disk or network.

@lunny commented on GitHub (Jul 18, 2020): I also send another PR #12244 to try to resolve the network problem when migrating from github to gitea.com since the total gitea repository will spend about 80GB disk or network.

GiteaMirror referenced this issue

2025-11-02 13:08:30 -06:00

[PR #4487] [MERGED] Accept 'Data:' in commit graph #17395

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#4467