[Tails-dev] stats on upgrade time
Hi, intrigeri: our design doc Thanks (: Wordlife, Spencer ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] stats on upgrade time
Spencer wrote (01 Feb 2016 18:02:18 GMT) : > I must know what is being requested, sent, how, and why. Is there > documentation on > this [I couldn't quickly find any] or should I capture a VM session? In general, our design doc is the best entry point to understand how Tails works behind the hood: https://tails.boum.org/contribute/design/incremental_upgrades/ ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] stats on upgrade time
Hi, sajolida: You cannot disable the security check for open security issues or upgrades. Not from within Tails? Should I roll my own and adjust the relevant package content beforehand? it's worth spending time on I agree d: Knowledge provides value. I must know what is being requested, sent, how, and why. Is there documentation on this [I couldn't quickly find any] or should I capture a VM session? create a ticket. Maybe. Wordlife, Spencer ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] stats on upgrade time
Spencer: >> sajolida: >> HTTP requests made on UDFs >> (upgrade description files) > > How can one prevent participation in this, in addition to not connecting to > the internet? You can disable all networking from the Greeter. You cannot disable the security check for open security issues or upgrades. Someone else suggested me making these opt-in/opt-out. I personally don't think it's worth spending time on this but if other people want to have a discussion about this possibility, why not create a ticket. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] stats on upgrade time
Hi, > > sajolida: > HTTP requests made on UDFs > (upgrade description files) > How can one prevent participation in this, in addition to not connecting to the internet? Where is the relevant file located and can it be removed or altered? Wordlife, Spencer ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] stats on upgrade time
Hi, Adam Burns: Uniquely identify each Tails image to assess and profile their usage frequencies as per above? I think that is called spying :) Wordlife, Spencer ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] stats on upgrade time
Adam Burns: > On 25/11/15 11:10, sajolida wrote: >> But there's always a pretty long tail of people with quite outdated >> versions. If we look, on the day before each release, at the number of >> people that are still not running the latest version: >> >> - Before 1.5: 19% >> - Before 1.6: 24% (we had a shorter cycle due to 1.5.1 here) >> - Before 1.7: 20% > > My guess would be that Tails usage cases, in terms of boot and shutdown > frequencies would vary wildy, from daily continual desktop use to very > occasional needs-only booting an image for specific projects or topics. I'd guess that, maybe, these people use a DVD as Tails device and cannot easily upgrade signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] stats on upgrade time
Hi Sajolida, Nice graph! On 25/11/15 11:10, sajolida wrote: > But there's always a pretty long tail of people with quite outdated > versions. If we look, on the day before each release, at the number of > people that are still not running the latest version: > > - Before 1.5: 19% > - Before 1.6: 24% (we had a shorter cycle due to 1.5.1 here) > - Before 1.7: 20% My guess would be that Tails usage cases, in terms of boot and shutdown frequencies would vary wildy, from daily continual desktop use to very occasional needs-only booting an image for specific projects or topics. > I'd like to continue working on this to: > > 1. Have a nice script that I can share with more people. > 2. Make is easier to take decision when doing migrations (like Icedove). > 3. See if it's worth shipping IUK for more than one version to the next. > 4. In the future, see how our improvements improve this situation >(installation assistant, full-self upgrades, etc.). > > Tell me if you have any other idea of how to make these numbers speak or > what this would be useful for. Uniquely identify each Tails image to assess and profile their usage frequencies as per above? ;-) But seriously, cool stats. Shine, Adam. signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] stats on upgrade time
Hi, sajolida wrote (25 Nov 2015 10:10:20 GMT) : > The other day I did some statistics on the HTTP requests made on UDFs > (upgrade description files) such as [1]. This give us an idea of which > versions of Tails are running at a given point in time. Here are some > initial results in attachment. Thanks! (And: yay! I bet the results would have been worse, by far, before we had incremental upgrades.) Cheers, -- intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] stats on upgrade time
Hi, The other day I did some statistics on the HTTP requests made on UDFs (upgrade description files) such as [1]. This give us an idea of which versions of Tails are running at a given point in time. Here are some initial results in attachment. My first interpretation of this is that people are upgrading quite fast (faster than what I expected). For example: - 1.5 was released on 20150811 - 1 day later, 38% of boots were from 1.5 - 1 week later, 63% - 2 weeks later, 71% So it seems like a good share of our user base are regular or daily users. But there's always a pretty long tail of people with quite outdated versions. If we look, on the day before each release, at the number of people that are still not running the latest version: - Before 1.5: 19% - Before 1.6: 24% (we had a shorter cycle due to 1.5.1 here) - Before 1.7: 20% I'd like to continue working on this to: 1. Have a nice script that I can share with more people. 2. Make is easier to take decision when doing migrations (like Icedove). 3. See if it's worth shipping IUK for more than one version to the next. 4. In the future, see how our improvements improve this situation (installation assistant, full-self upgrades, etc.). Tell me if you have any other idea of how to make these numbers speak or what this would be useful for. [1] https://tails.boum.org/upgrade/v1/Tails/1.7/i386/stable/upgrades.yml ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
