- nexa - server-nexa.polito.it

R: Released Neubot 0.42
by Andrea Rossetti Sept. 20, 2011

Sept. 20, 2011

[Pm Breve e con typos perché scritto con BlackBerry® -----Original Message----- From: Simone Basso <bassosimone(a)gmail.com> Sender: nexa-bounces(a)server-nexa.polito.it Date: Mon, 19 Sep 2011 18:33:23 To: <nexa(a)server-nexa.polito.it> Subject: [nexa] Released Neubot 0.4.2 Released Neubot 0.4.2 http://www.neubot.org/neubot-0.4.2 Version 0.4.2 is the latest generally-available stable release of Neubot, distributed for Ubuntu >= 10.04, MacOSX >= 10.6 and Windows >= XP SP3. Of course, Neubot 0.4.2 is also available in source format (.tar.gz and .zip). This release contains 143 patches. The diffstat says: 87 files changed, with 3167 lines inserted and 1392 lines deleted. Here are the most relevant changes: o MacOS: automatic updates in the background. This implementation of the automatic updates is very generic, in the sense that is based on the standard UNIX API and does not leverage MacOS specific facilities, such as launchd(8). I have patches to do that but they are not ready for this release and they will go into the next one; o Win32: disable autostart at the end of the install. Because the installer runs with high privileges and so starts Neubot with high privileges too. (Of course Neubot will autostart each time you login on the system and the _only_ difference is that it is not started at the end of the installation.) I have scheduled some work on the Windows installer for the coming weeks. I hope I will be able to find a viable solution for this privileges issue too; o Ubuntu: new GUI, based on PyGtk+ and PyWebKit. The basic idea is to embed WebKit into a Gtk+ window and to point it to Neubot Web UI. So, now you use Neubot's own application instead of opening its Web User Interface into the browser. I think this is more usable and clear. http://www.neubot.org/improving-user-experience-under-ubuntu BTW I have plans to do something similar for MacOS and Windows too; o database: add OS name and Neubot version to results. I've added them because they help data analysis. The version is important because the behavior of the tests may change over time, because of changes in the code base. The operating system is important as well, because every OS implements TCP/IP in a peculiar way; o net: undo the 262144-receive buffer optimization. Using a fixed-size buffer penalizes Linux, which has very advanced buffer management strategies designed for high bandwidth-delay product networks. (Having the version number and the OS name in the database allows to track the effect of this change quite well); o www: if privacy settings are not set, the starting page is privacy.html not index.html. We are modifying our installers to show privacy policy and ask for permission to collect and share/publish. The installer will also refuse to install if you don't give the permission to collect the results. But the work is still in progress, and for now only the MacOS installer is ready. Meanwhile, it will not hurt to land users on privacy.html; o privacy: do not allow nonsense transitions once you have set the permissions. There are two different changes here. 1. Once you have said that your are informed you cannot step back and tell Neubot you're not informed. This is pure common sense. 2. Also, once you've given the permission to collect your results you cannot step back. This is to align with installers, that are being modified to allow installation only if you read the policy and give the permission to collect the results; o speedtest: use just one connection, like bittorrent does. This is the first step to make the two tests more comparable: of course comparing two connections with one _isn't_ fair, especially with high bandwidth-delay products or when there is more average congestion. More work is needed before we can say that the two tests stress the network in the same way. Namely, we need to change speedtest to work on a request-response basis, like bittorrent does. So, this is just the first step in the right direction. (And this is another case where saving the version number in the database would be very helpful to track the effects of the change.) o server: add support for a simple API to assess server state. This API is needed to implement a simple Nagios plugin, which can say whether the server state is OK or not; o nagios-plugin: finalize it. Now the plugin uses the abovementioned server API to assess server status and return something in the (OK, WARNING, ERROR) domain. o more code rationalizations, bug and reliability fixes, unit tests. The release candidates have been tested on Ubuntu 10.04, Windows XP SP3, Windows 7 and MacOSX 10.6. The main testing platform has been my laptop with MacOS 10.6.8. Packages and source archives available here: http://www.neubot.org/download ChangeLog here: https://raw.github.com/neubot/neubot/0.4.2/ChangeLog Commit history here: https://github.com/neubot/neubot/commits/0.4.2 SHA256sums here: https://raw.github.com/neubot/neubot-sha256s/master/0.4.2/SHA256 People that contributed to this release, with patches, testing and/or feedback: Simone Basso Marco Scopesi Alessio Palmero Aprosio Federico Morando Juan Carlos De Martin Matt Mathis Thank you for you attention, Simone <http://www.neubot.org/people#basso> _______________________________________________ nexa mailing list nexa(a)server-nexa.polito.it https://server-nexa.polito.it/cgi-bin/mailman/listinfo/nexa

1 0

Commenti estensione Copyright
by Paolo Brini Sept. 20, 2011

Sept. 20, 2011

4 9

Released Neubot 0.4.2
by Simone Basso Sept. 19, 2011

Sept. 19, 2011

Released Neubot 0.4.2 http://www.neubot.org/neubot-0.4.2 Version 0.4.2 is the latest generally-available stable release of Neubot, distributed for Ubuntu >= 10.04, MacOSX >= 10.6 and Windows >= XP SP3. Of course, Neubot 0.4.2 is also available in source format (.tar.gz and .zip). This release contains 143 patches. The diffstat says: 87 files changed, with 3167 lines inserted and 1392 lines deleted. Here are the most relevant changes: o MacOS: automatic updates in the background. This implementation of the automatic updates is very generic, in the sense that is based on the standard UNIX API and does not leverage MacOS specific facilities, such as launchd(8). I have patches to do that but they are not ready for this release and they will go into the next one; o Win32: disable autostart at the end of the install. Because the installer runs with high privileges and so starts Neubot with high privileges too. (Of course Neubot will autostart each time you login on the system and the _only_ difference is that it is not started at the end of the installation.) I have scheduled some work on the Windows installer for the coming weeks. I hope I will be able to find a viable solution for this privileges issue too; o Ubuntu: new GUI, based on PyGtk+ and PyWebKit. The basic idea is to embed WebKit into a Gtk+ window and to point it to Neubot Web UI. So, now you use Neubot's own application instead of opening its Web User Interface into the browser. I think this is more usable and clear. http://www.neubot.org/improving-user-experience-under-ubuntu BTW I have plans to do something similar for MacOS and Windows too; o database: add OS name and Neubot version to results. I've added them because they help data analysis. The version is important because the behavior of the tests may change over time, because of changes in the code base. The operating system is important as well, because every OS implements TCP/IP in a peculiar way; o net: undo the 262144-receive buffer optimization. Using a fixed-size buffer penalizes Linux, which has very advanced buffer management strategies designed for high bandwidth-delay product networks. (Having the version number and the OS name in the database allows to track the effect of this change quite well); o www: if privacy settings are not set, the starting page is privacy.html not index.html. We are modifying our installers to show privacy policy and ask for permission to collect and share/publish. The installer will also refuse to install if you don't give the permission to collect the results. But the work is still in progress, and for now only the MacOS installer is ready. Meanwhile, it will not hurt to land users on privacy.html; o privacy: do not allow nonsense transitions once you have set the permissions. There are two different changes here. 1. Once you have said that your are informed you cannot step back and tell Neubot you're not informed. This is pure common sense. 2. Also, once you've given the permission to collect your results you cannot step back. This is to align with installers, that are being modified to allow installation only if you read the policy and give the permission to collect the results; o speedtest: use just one connection, like bittorrent does. This is the first step to make the two tests more comparable: of course comparing two connections with one _isn't_ fair, especially with high bandwidth-delay products or when there is more average congestion. More work is needed before we can say that the two tests stress the network in the same way. Namely, we need to change speedtest to work on a request-response basis, like bittorrent does. So, this is just the first step in the right direction. (And this is another case where saving the version number in the database would be very helpful to track the effects of the change.) o server: add support for a simple API to assess server state. This API is needed to implement a simple Nagios plugin, which can say whether the server state is OK or not; o nagios-plugin: finalize it. Now the plugin uses the abovementioned server API to assess server status and return something in the (OK, WARNING, ERROR) domain. o more code rationalizations, bug and reliability fixes, unit tests. The release candidates have been tested on Ubuntu 10.04, Windows XP SP3, Windows 7 and MacOSX 10.6. The main testing platform has been my laptop with MacOS 10.6.8. Packages and source archives available here: http://www.neubot.org/download ChangeLog here: https://raw.github.com/neubot/neubot/0.4.2/ChangeLog Commit history here: https://github.com/neubot/neubot/commits/0.4.2 SHA256sums here: https://raw.github.com/neubot/neubot-sha256s/master/0.4.2/SHA256 People that contributed to this release, with patches, testing and/or feedback: Simone Basso Marco Scopesi Alessio Palmero Aprosio Federico Morando Juan Carlos De Martin Matt Mathis Thank you for you attention, Simone <http://www.neubot.org/people#basso>

1 0

Consultazione AGCom-fase III
by Blengino Sept. 19, 2011

Sept. 19, 2011

Cari tutti, da questo link http://nexa.polito.it/nexafiles/Nexa-Consultazione_AGCOM_2.doc potete scaricare la bozza delle osservazioni allo schema di regolamento della II consultazione AGCom. Abbiamo cercato di inglobare tutti i preziosi suggerimenti del documento condiviso, e di dare una forma accettabile al tutto. Come vedrete vi è ancora molto da fare, ma i tempi sono strettissimi. Entro lunedì dobbiamo finalizzare l'atto che deve esser inviato non oltre il 14 sett. Vi chiediamo di valutarlo e di segnalarci non tanto gli strafalcioni o le imprecisioni di battitura e formattazione, che saranno riviste ed emendate essendo questa comunque una bozza, ma di segnalare eventuali approfondimenti, idee o errori di merito. Il tutto entro domenica. Grazie a tutti. -----Messaggio originale----- Da: Federico Morando [mailto:federico.morando@polito.it] Inviato: mercoledì 7 settembre 2011 14.38 A: Blengino Cc: 'Alessandro Enrico Cogo'; 'Deborah De Angelis'; 'J.C. DE MARTIN'; marco.ricolfi(a)studiotosetto.it Oggetto: Re: R: [nexa] Consultazione AGCom-fase III Caro Carlo, se volete distribuire il file così come me lo hai inviato (in formato DOC scaricabile), potete usare questo link: http://nexa.polito.it/nexafiles/Nexa-Consultazione_AGCOM_2.doc Se, invece, volete avere un GoogleDoc dove il file è anche editabile e commentabile, il link è questo: http://t.co/dYJGHbc Io userei solo una delle due opzioni, a seconda del tipo di commenti/editing che volete generare (la prima opzione è meglio se volete che la gente "prenda conoscenza" ed eventualmente segnali solo cose che gli stanno a cuore; la seconda se volete più commenti e modifiche minute). Per qualsiasi chiarimento, sono in ufficio (ed anche raggiungibile sul cell). Grazie e ciao, Federico On 09/07/2011 11:09 AM, Blengino wrote: > Federico, > come da telefonata, ti mando in allegato la prima bozza delle osservazioni > alla II consultazione che mette insieme le osservazioni raccolte nella fase > I. > Poichè se invio direttamente in lista l'allegato mi viene bloccato, ti > pregherei di uplodare il doc su Googledoc e di mandarmi il link pubblico, > così che possa dare avvio alla "brevissima" fase III di consultazione in > lista per chiudere lunedì. > Stante i tempi brevi, ti prego di farlo il prima possibile. > Grazie mille. > Carlo > > -----Messaggio originale----- > Da: nexa-bounces(a)server-nexa.polito.it > [mailto:nexa-bounces@server-nexa.polito.it] Per conto di Blengino > Inviato: giovedì 11 agosto 2011 19.05 > A: J.C. DE MARTIN; nexa(a)server-nexa.polito.it; > marco.ricolfi(a)studiotosetto.it; federico.morando(a)polito.it > Oggetto: [nexa] Consultazione AGCom-fase II > > Cari tutti, > Innanzi tutto, un grazie a coloro che hanno contribuito con le loro > osservazioni sul doc condiviso. > Con Alessandro, e come da programma, abbiamo dunque deciso di passare alla > fase II. > > Nei prossimi giorni Alessandro si concentrerà su di una premessa che, senza > ripeter le osservazioni contenute nel documento relativo alla prima > consultazione, comunque sintetizzi le criticità generali che permangono. Se > vi vengono dunque illuminazioni estive slegate dal testo normativo, fate > riferimento a lui. > > Io inizierò invece a compattare i vostri emendamenti e le osservazioni in > relazione ai singoli articoli, anche se la tentazione sarebbe, per buona > parte del testo, un sintetico ed efficace "abrogato". Eventuali ulteriori > riflessioni sui singoli articoli mandatele pure a me. > > A fine agosto cercheremo di condividere il tutto, per affinarlo e > finalizzarlo entro la scadenza. > > Ringraziando l'Autorità per l'agevole tempistica prescelta, auguriamo a > tutti buone vacanze !! > > Carlo (anche per Alessandro) > > > _______________________________________________ > nexa mailing list > nexa(a)server-nexa.polito.it > https://server-nexa.polito.it/cgi-bin/mailman/listinfo/nexa >

6 6

Caso Yahoo, host attivo e dubbi
by MANTELERO ALESSANDRO Sept. 18, 2011

Sept. 18, 2011

Ho letto la sentenza, ma la teoria dell'host attivo (almeno in questi casi) mi convince poco. Qui trovate il link al provvedimento... e qualche dubbio: http://goo.gl/D1I06 Buona domenica, Alessandro Mantelero

1 0

Internet Archive adds its 3 millionth scanned book
by Paolo Brini Sept. 18, 2011

Sept. 18, 2011

"The Internet Archive's Book Scanning project just added its three millionth text. Unlike Google Book Search, the Archive only scans public domain works, and, more significantly, places no restrictions on the scans' usage. Another significant difference is the Archive's privacy policy, which, unlike Google, promises not to release your personal information without a court order. " <http://boingboing.net/2011/09/17/internet-archive-adds-its-three-millionth-…> Ciao, Paolo

1 0

Accesso all'informazione e libertà di espressione
by Paolo Brini Sept. 18, 2011

Sept. 18, 2011

2 1

Berlin Symposium on Internet and Society
by a.dicorinto＠uniroma1.it Sept. 17, 2011

Sept. 17, 2011

1 0

Diritto d’autore: British Library appoggia il progetto italiano Arrow per la digitalizzazione delle opere europee
by a.dicorinto＠uniroma1.it Sept. 17, 2011

Sept. 17, 2011

2 1

British firm offered spy software to Egypt
by Paolo Brini Sept. 16, 2011

Sept. 16, 2011

3 6