> Enforce scope (namespace) requirement, and require external verification (reverse DNS for example).

Who the heck says everyone who publishes a library has a domain? That seems absurd.

brunoborges a month ago | parent | next [-]

Sonatype allows "io.github.<username>" as a valid groupId and has a process to verify ownership. I am sure other providers like GitLab can work on this.

▲

oarsinsync a month ago | parent | prev | next [-]

You can get subdomains for free from a number of places, some of which are more reliable than others.

This exists because domains (historically) used to be expensive by western standards. .com used to be $75/year back in the day.

▲

chadgpt3 a month ago | parent | prev | next [-]

Why don't you? It costs around $20 per year. Every serious computer nerd should have one, and a web server with at least a basic homepage.

▲

whatevaa a month ago | parent [-]

$20 per year on US is not the same value across the world. Would you say $60 per year is ok too, if you adjusted for income? 100$?

Don't count other people money.

▲

lelanthran a month ago | parent [-]

The problem with this argument against, is that it reinforces the point it is arguing against: If a contributor cannot afford the $20/year to publish for a single 12-month period, then they are already a risk - someone could buy their account off them.

A small bar of $20/year is also enough to completely cut-down on contributors who sign up with the intention of publishing malicious packages: they have to pay $20/year for each malicious package they want to publish!

▲

com2kid a month ago | parent [-]

Why should someone need a credit card to contribute to open source? Why should they need to understand DNS?

Heck domain names are ephemeral, forget a deadline by a day and they are snatched up my squatters. They don't provide any extra guarantees. Do we really think a domain requirement is going to stop state level actors that are already stealing 2FA package publishing tokens from major software orgs?

▲

lelanthran a month ago | parent [-]

> Do we really think a domain requirement is going to stop state level actors that are already stealing 2FA package publishing tokens from major software orgs?

Is that your target? Because if so, then nothing will stop them.

	▲	com2kid a month ago \| parent [-]
		The most recent attacks have been incredibly sophisticated, executed against orgs that have taken all the right steps. Requiring domain name verification is not going to do anything when 2FA tokens are being stolen. What it will do is prevent students and people who want to stay anonymous from contributing to open source.

▲

radlad a month ago | parent | prev [-]

And domains can change hands legitimately.

	▲	whatevaa a month ago \| parent [-]
		Or be forgotten to renewed, lost and, depending on registrar, overtaken.