When browsing an unrelated project’s documentation, there was a a link to the libsoup project using the following URL:
https://developer.gnome.org/libsoup/stable(not linkified)
This page performs a redirect (301) to an obsolete libsoup domain:
https://www.libsoup.org/(not linkified)
Which appears to be have been picked up by an unrelated third-party.
I assume this is not expected and maybe someone can adjust the link to redirect to (what I assume is) the proper home for libsoup:
Thanks for reporting this issue!
I’ve unlisted this topic, so only intended people will try accessing the third party link https://www.libsoup.org/ (which sounds fishy to me).
/cc @averi
GNOME recently failed to renew libsoup.org, the legitimate previous home of the libsoup documentation. I don’t know why. It was subsequently purchased by a third party and now it seems to be some sort of spam domain.
Unfortunately regaining control of domains is usually expensive.
CC @pgriffis who was previously operating libsoup.org
Um, I guess we need to change https://developer.gnome.org to redirect to the new domain rather than the old one.
Also, I think we should have a process in GNOME for handling external websites registered to a GNOME project. It impacts GNOME finally, when a domain is taken over by a malicious third party, so GNOME should have some level of clarity on the ownership, renewal dates etc.
IIUC, it’s not a huge amount per year. So, I guess if the registered domain owner doesn’t feel like renewing, GNOME can plan and execute what needs to be done in a reasonable time frame in advance.
From what I’ve seen, registered domain owners tend to feel that they’re paying out of their pockets every month / year for no good reason currently, after having paid the bills for a really long time, which is perfectly understandable.
Some clarity here would benefit everyone involved.
Direct libsoup.org references which need to be updated.
I don’t think there’s any need for this topic to be confidential. Would be helpful to have some page to reference for why this has happened.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.