Note, just so people do not misunderstand. This is done by some developers on Debian, not the Debian project itself. Just because they contribute or develop on Debian does not mean they cannot do whatever they want outside the project. The official Debian domain is https://www.debian.org/ while this project is on https://inference.debian.net/ where just debian.net doesn’t even resolve in Firefox and I get a warning (but ignoring issue and proceeding will redirect to debian.org). Edit: BTW debian.net redirect directly now. I assume it was a temporary issue or they fixed it when seeing the problems in the logs.
My point is, this is not official Debian project, it’s just some developers outside the project provide a service.
Thanks for updating the title! I guess the author of the article got “fooled” by to. I just discovered this by accident. Now the debian.net redirects directly without the prior issue. Maybe they discovered this in their log and updated it quickly or it was a temporary issue with the certification.
Note, just so people do not misunderstand. This is done by some developers on Debian, not the Debian project itself. Just because they contribute or develop on Debian does not mean they cannot do whatever they want outside the project. The official Debian domain is https://www.debian.org/ while this project is on https://inference.debian.net/ where just debian.net doesn’t even resolve in Firefox and I get a warning (but ignoring issue and proceeding will redirect to debian.org). Edit: BTW debian.net redirect directly now. I assume it was a temporary issue or they fixed it when seeing the problems in the logs.
My point is, this is not official Debian project, it’s just some developers outside the project provide a service.
Thank you, the way this article is worded made it sound like an official one. Will leave this up but I made a note in the title.
Thanks for updating the title! I guess the author of the article got “fooled” by to. I just discovered this by accident. Now the debian.net redirects directly without the prior issue. Maybe they discovered this in their log and updated it quickly or it was a temporary issue with the certification.
Edit: To provide more context: https://docs.debian.net/scope.html