trying since hours to register an additional account which i intend to become the owner of imported github issues, however i don't get any mail with activation link. do you block any non-mainstream email providers, or is there an issue with the mail server?
if it is the former, it would be helpful if that is clearly stated so people don't waste their time.
registration activation mail not sent #328
A valid receivable email address is required (single-use/throwaway email providers are not supported). Otherwise there are no restrictions.
btw for registration on github no activation/confirmation mail is required, so one can open an account with a bogus email address like president@whitehouse.gov, which i personally find much more comfortable than the mail dance. if you get rid of that annoyance completely, you also automatically solve the registration mail spam issue 298.
@hw i used several accounts that are "valid receivable", one of them even comes with POP3/SMTP account (codeberg account name for that one is github_migration_bot)
btw for registration on github no activation/confirmation mail is required [...]
Not true. Check their ToS, section B ("...you must provide a valid email address..."). Even if this were technically true, both Gitea and the GIT protocol identify owners/users by one of the registered email addresses.
@hw i used several accounts that are "valid receivable", one of them even comes with POP3/SMTP account (codeberg account name for that one is github_migration_bot)
The server for the email address linked to this account does not even have a valid TLS certificate.
so, will i have to open a gmail account with telephone number registration just to get another account? note that the whole dance is only required because the "new migration" feature doesn't provide the option to add an oauth token, but it requires github username and password which would allow someone sniffing it to takeover my entire gh account. so effectively i was forced to write my own github importer.
the result looks like https://codeberg.org/sabotage-linux/butch/issues
@rofl0r
The importer DOES accept tokens as a password.
And you are not forced to to open a gmail account, just don't use thowaway junk mail, temp mail providers.
I can understand that it might be annoying, if it hurts to much, there are alternatives to codeberg.org, notabug.org for example did not need a valid email address when I last tried.
Migration works with API token. The Gitea 1.13 to be deployed soonish and currently tested on https://codeberg-test.org improves user experience by explaining this more clearly, but technically the current production version supports API tokens as well. No need to hand over your credentials.
just don’t use thowaway junk mail, temp mail providers.
i'm using cock.li services since years, it's a reliable mail provider - the only non-standard thing is that you can register an account without telling them your name address credit card and phone number.
anyway, @hw could you please do me the favor and mark the github_migration_bot account as activated so i can finally continue with my migration?
but technically the current production version supports API tokens as well. No need to hand over your credentials.
oh that's great - where can one enter the token?
@rofl0r
You can enter the token instead of the passwort. I think you even have to since IIRC github does no longer allow the api with password auth.
And please do not name the user github_migration_bot. It looks like a global official codeberg account, how about roflOr_github_migration_bot?
do me the favor and mark the github_migration_bot account
No, no junk mail accounts allowed.
cock.li services
marked as abusive on all common blacklists since ages. Not allowed for good reason.
Not allowed for good reason.
alright, i can understand your decision, but i think it would be quite kind to the user if the registration process would fail with a message like "junk mail provider not allowed" instead of showing success but then simply not sending the mail and letting the user in the dark about what's happening (it also means that the chosen username is then effectively trashed).
there are alternatives to codeberg.org, notabug.org for example did not need a valid email address when I last tried.
yes, but they use a CoC - and i chose codeberg exactly because it doesn't have one.
We need a CoC too.
Some things should be obvious but it seems that we need to spell them out.
lack of a CoC doesn't necessarily mean that everybody is behaving like a bunch of mad teenagers. but having a CoC sends a political signal to certain people that like to feel offended and point fingers at others. i found it quite refreshing when linus torvalds told certain annoying persons to just shut up. these times are over though, he's been successfully brought under the liberal heel.
I also use cock.li. The most popular email services these days requires a phone number.
It worked with github for a while but one day they started messing with it. Can't create an account with those emails, then you could create an account but couldn't comment unless you verified your email but github won't send the verification email to those domains.
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
Things related to Codeberg's external communication
More information is needed
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?