@libreoffice i noticed i wasn't able to read your webpage without enabling javascript. but when i view the webpage source, the content of the post is there.

noscript consent was overridden

i then noticed you have this specific element in your HTML content:

<noscript><p><img src="https://metrics.documentfoundation.org/post?idsite=65&rec=1" style="border:0;" alt="" /></p></noscript>

...and i've just noticed at the end of writing this post that you've still managed to add a separate remote URL fetch in the <img src="..." component there. the alt="" is a really bad look, too.

telemetry executing in the js i was forced to allow

and what's more troubling, i found this (admittedly circumstantial) script tag just above that one:

<link rel="pingback" href="https://blog.documentfoundation.org/xmlrpc.php"><script type="text/javascript">
  var _paq = window._paq = window._paq || [];
  _paq.push(["disableCookies"]);
  _paq.push(['trackPageView']);
  _paq.push(['enableLinkTracking']);
  (function() {
    var u="https://metrics.documentfoundation.org/";
    _paq.push(['setTrackerUrl', u+'post']);
    _paq.push(['setSiteId', '65']);
    var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
    g.type='text/javascript'; g.async=true; g.src=u+'metrics.js'; s.parentNode.insertBefore(g,s);
  })();
</script>

who made this decision? what governance structures are accountable for this?

since you're using this precise language in your post:

LibreOffice contains no adverts, does not collect telemetry data

i have to wonder what sequence of events could have induced the need for more telemetry data executing in javascript upon the user's web browser. i presume your server could have simply performed the task of tracking hits as it received my web browser's http request?

i don't think adding a loading spinner for noscript users is acceptable whatsoever. whoever made that decision was fully aware that noscript acts as a user agent for a member of your human user community.

please help me understand this decision you've made on your website, which seems clearly intended to perform javascript telemetry without my consent, and how it may or may not relate to any funding situation you may or may not have.

further concern: threatening language

Maintaining each of these features incurs costs, as each represents a source of revenue that the foundation has chosen not to exploit.

this is a remarkably threatening tone. i would love to assume good intent, but "exploit" is really not a word i consider acceptable when the linux kernel itself has so deeply wounded my trust in open-souce organizations so many times this year.

final concern: interop features are broken, forced to execute plugin code for any degree of document automation

i experienced immense difficulty identifying how to extract data from an xlsx spreadsheet via the command line a year back. the documentation was spread across several pages, and some of the necessary info was on a separate website from red hat. furthermore, the functionality to retrieve data from any sheet except the first sheet seemed to be unimplemented and/or broken--i couldn't tell.

is there any API? backwards compatibility? user guarantees?

eventually, i installed a plugin to export information from the second page of the datasheet (i was exporting AMD's freely published instruction cycle latencies from their spreadsheet for my personal use in kernel development). this of course requires executing someone else's code upon my machine, in order to support a basic task that i should have been able to perform using a trusted software like libreoffice to interpret proprietary and corporate-driven formats for greater interoperability.

particularly when you use terms like "exploit", and yet on the other hand, possibly the 2nd most important functionality i could possibly demand from an open source office software (extracting text from word docs is #1, csv from xlsx is #2) is not only broken, but undocumented, and the documentation that is there is wrong.....

.......it makes me feel unsafe. much like your website did when it refused to display your own post, until i did an img src="..." load, then another reload with javascript to remove the noscript wall, then executed the javascript telemetry you forced me to accept.

please remove the incredibly manipulative tracking features from your website. i can't make you document anything or support any API you don't care to.