© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
> Huh? But the data is just part of the GET request. Is that really so heavy?
I suppose we can just drop data serverside (gah, going to have to learn php...), but there's another concern I'd forgotten about which is that limiting submission to once per week also makes the stats much more accurate (unless you sacrifice anonymity by including a unique identifier of some sort, which is very bad.). If you check on launch then each user is counted once per launch, if you check on an interval then people who leave the app open less are counted less. Perhaps Sparkle should just *always* limit the submission rate? It seems like it'd be a win for everyone.
> If weekly is good enough for the OS, most users would probably find it okay for their IM client.
1.2.6 was broken in ways that impact other users as well; it was pretty important to minimize its exposure to the world by ensuring that everyone got the 1.2.7 update asap.
> I don't really want to do that; my thinking is that you can add the header to your project if you need it, but with the caveat that I may
> mess you up at any time.
Break on updates with just copying the header, or no breakage but no future fixes if we copy the implementation too. I *think* we'd probably choose the latter; with any luck the version comparison algorithm is quite stable by this point.