Subsequent discussion of this matter has focused on finding an acceptable way to receive a ping from new installs.
That's because sending, receiving, and tracking pings are the goals of the new feature. Little or nothing has been said about how to track the latest version, or how to help the user install the latest version. That's because those aren't goals of the "automatic update feature". Therefore, I propose to scrap the "update" part and simply implement a ping feature instead. Here is a DRAFT: """Hello, user. This is a message from the Leo developers. We have no idea how many people use Leo. Click here to send us a ping. The exact content of your transmission will be "HTTP GET /leo/newinstall/linux/python3.14", which as you can see includes information about your OS and python version. and the receiver has been configured to forget your IP address but remember the date and time and the information you sent us. You can send different information if you like by editing ping.leo, blah blah. We really appreciate it!""" This will be easier to implement. Most of the work will be on the server-side. It will also be more transparent. That's a VERY important quality. Will many folks abstain from participation? Yes. That's their choice. And I think that, unfortunately for us, it TRUMPS our need to know how many people use Leo. I hope that this helps. Cheers, --Dave On Friday, August 9, 2013 9:13:09 AM UTC-5, dufriz wrote: > > Couldn't you include an automatic update feature into the program, which > will signal the presence of an instance of Leo being used? > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
