Official extensions site is not available in google

The official sub-domain extensions.libreoffice.org does not appear in the search results anywhere when I search for any extension. For e.g. google for “TexMaths libreoffice extension” and you get templates-arm subdomain.
If you click on the link, you get “Your connection is not private” message. Please fix it.

Bug reports are off-topic here. Then, reports regarding LibreOffice site itself should be on Redmine. But then - how do you imagine TDF to “fix” wrong results of Google search???

For me templates-arm on 3rd (7) pos from my mobile,
updateexte on pos 6 (21) and
extensions on 10th (28) pos.
EDIT: I used “LibreOffice extension Texmath” and added numbers for your “Texmath LibreOffice extension” in ()
.
So the files are available for google.
The link to extensions leads me to an alpabetical list, and TeXMath will be on the following page, so not anything current…
As I did this from my mobile I will not complain on arm-results first, but I will compare later with my desktop.

as a workaround :

also https://updateexte.libreoffice.org/en/extensions/show/show?commentsstart334=20&start=0
indeed weird

How to Report Bugs in LibreOffice - The Document Foundation Wiki #Not_all_bugs_go_to_Bugzilla
Redmine - The Document Foundation Wiki

The issue has remained unacknowledged for a month.

1 Like

… maybe because that’s not for TDF?

If you visit https://templates-arm.libreoffice.org/ you get a message “Attackers might be trying to steal your information”.
Not a TDF issue?

Are you a troll? Again: it’s Google who gave you a wrong search result. And now you request TDF to make that wrong Google result to work as if that was correct?

And no, I don’t see that “Attackers might be trying to steal your information” visiting that link, I get “DNS_PROBE_FINISHED_NXDOMAIN”.

And also: I get correct results using e.g. Duck-Duck-Go instead of Google. So - did you file a request to Google finally?

definitely is.

maybe some hope moving to Kiwi IRC #tdf-infra

Same for me. But maybe the browser of @shantanuo tries to get encryption for the subdomain (https), fails and issues the warning for http without s.

May be easier than steering google to fix their results, as someone already wrote (completly right to my experience):

It may be easier (but had OP even tried to ask Google? Or was it “I will require you to do the work, because I think that it’s easier to nag you than the real trouble-makers?”). But even easier is do nothing, because that’s simply not a problem at all. And in some time, Google will fix their search results themselves.