4 ms·

The analytics seem pretty benign. "We send events to our Amplitude instance to be aware of the number of people who use MeiliSearch. We only send the platform

The analytics seem pretty benign. "We send events to our Amplitude instance to be aware of the number of people who use MeiliSearch. We only send the platform on which the server runs once by day. No other information is sent. If you do not want us to send events, you can disable these analytics by using the MEILI_NO_ANALYTICS env variable."

seemslegit 7y ago
The practice itself is malignant, either explicitly ask upon first run or require a MEILI_YES_ANALYTICS env variable to enable it.
- turdnagel 7y ago
  That would require configuration. This is zero-config.
  - computerex 7y ago
    It'd still be zero-config to provide it's primary function. I don't think anyone would say anything against MeiliSearch or not consider it zero-config had they decided to enable analytics off an env var rather than having analytics be sent by default.
    - deleted 7y ago
      [deleted]
    - qdequelen 7y ago
      I would like to clarify that by analytics we are only talking about 1 ping per day that sends a hash that allows us to uniquely identify a user. The privacy of the users is kept. It just serves us to know if our work is being used.
      - seemslegit 7y ago
        > I would like to clarify that by analytics we are only talking about 1 ping per day that sends a hash that allows us to uniquely identify a user. This is already pretty invasive - it discloses activity, number of machines deployed, IP address which identifies location and often organizations and individuals (and which is considered protected personal data per the GDPR afaik). > The privacy of the users is kept. No it isn't, see above - even as the authors you don't get to decide what data does or doesn't infringe upon the users privacy. > It just serves us to know if our work is being used. This is irrelevant, if you want to condition the use of your work on being let known where and how it is being used then license it accordingly and abide by the applicable laws.

seemslegit 7y ago

The practice itself is malignant, either explicitly ask upon first run or require a MEILI_YES_ANALYTICS env variable to enable it.

turdnagel 7y ago
That would require configuration. This is zero-config.
- computerex 7y ago
  It'd still be zero-config to provide it's primary function. I don't think anyone would say anything against MeiliSearch or not consider it zero-config had they decided to enable analytics off an env var rather than having analytics be sent by default.
  - deleted 7y ago
    [deleted]
  - qdequelen 7y ago
    I would like to clarify that by analytics we are only talking about 1 ping per day that sends a hash that allows us to uniquely identify a user. The privacy of the users is kept. It just serves us to know if our work is being used.
    - seemslegit 7y ago
      > I would like to clarify that by analytics we are only talking about 1 ping per day that sends a hash that allows us to uniquely identify a user. This is already pretty invasive - it discloses activity, number of machines deployed, IP address which identifies location and often organizations and individuals (and which is considered protected personal data per the GDPR afaik). > The privacy of the users is kept. No it isn't, see above - even as the authors you don't get to decide what data does or doesn't infringe upon the users privacy. > It just serves us to know if our work is being used. This is irrelevant, if you want to condition the use of your work on being let known where and how it is being used then license it accordingly and abide by the applicable laws.