[freenet-dev] Feedback wanted: Browser picking policy on Windows
Hey all I'm looking for feedback regarding browser picking policy on Windows. At the moment, we do: Maintain a list of registry paths and common program locations of various browsers. These are prioritized according to whether they support incognito mode and how their security is rated in general. The first found browser in this list is launched. If no known browser is found, we fall back to whatever system default the user has. My suggestion: Instead we rely solely on the system default. Windows XP, Vista and 7 all have systemwide protocol defaults that can be changed via the control panel. Most browsers ask the user if they want to change their browser default until they either accept or dismisses the suggestion. On this basis, I believe we should accept the user's choice of browser by running Freenet in whatever browser the user has as default. Mind you that Chrome, FireFox and IE all have incognito modes now. Worst-case scenario is that the user has some sucky version of IE as default, but we *still* warn about IE in fproxy. My view is that it is more important to integrate properly with the user's desktop, accept his choice of browser, and ease ourselves of most of the browser-list maintenance, rather than insisting on choosing a browser for the user. Comments? - Zero3
[freenet-dev] Encouraging contributions and community development
Ian Clarke skrev: > Normally stuff only gets done with > Freenet when someone goes ahead and does it. Sitting around waiting > for permission rarely gets anything done. I couldn't agree more. Maybe we should figure out how to improve this bad habbit? I think we would get a lot more positive support, feedback and code back from the community if we could create a more... pleasant atmosphere... Perhaps we culd try to kind of move away from our current (IMHO!) harsh-tone-everyone-on-his-own-ish style (ala the Linux Kernel mailing list) towards a more encouraging-welcoming-open-community style (ala the Ubuntu forums)? :) - Zero3
[freenet-dev] Encouraging contributions and community development
Ian Clarke skrev: Normally stuff only gets done with Freenet when someone goes ahead and does it. Sitting around waiting for permission rarely gets anything done. I couldn't agree more. Maybe we should figure out how to improve this bad habbit? I think we would get a lot more positive support, feedback and code back from the community if we could create a more... pleasant atmosphere... Perhaps we culd try to kind of move away from our current (IMHO!) harsh-tone-everyone-on-his-own-ish style (ala the Linux Kernel mailing list) towards a more encouraging-welcoming-open-community style (ala the Ubuntu forums)? :) - Zero3 ___ Devl mailing list Devl@freenetproject.org http://osprey.vm.bytemark.co.uk/cgi-bin/mailman/listinfo/devl
[freenet-dev] Feedback wanted: Browser picking policy on Windows
Hey all I'm looking for feedback regarding browser picking policy on Windows. At the moment, we do: Maintain a list of registry paths and common program locations of various browsers. These are prioritized according to whether they support incognito mode and how their security is rated in general. The first found browser in this list is launched. If no known browser is found, we fall back to whatever system default the user has. My suggestion: Instead we rely solely on the system default. Windows XP, Vista and 7 all have systemwide protocol defaults that can be changed via the control panel. Most browsers ask the user if they want to change their browser default until they either accept or dismisses the suggestion. On this basis, I believe we should accept the user's choice of browser by running Freenet in whatever browser the user has as default. Mind you that Chrome, FireFox and IE all have incognito modes now. Worst-case scenario is that the user has some sucky version of IE as default, but we *still* warn about IE in fproxy. My view is that it is more important to integrate properly with the user's desktop, accept his choice of browser, and ease ourselves of most of the browser-list maintenance, rather than insisting on choosing a browser for the user. Comments? - Zero3 ___ Devl mailing list Devl@freenetproject.org http://osprey.vm.bytemark.co.uk/cgi-bin/mailman/listinfo/devl
[freenet-dev] Some (very) preliminary mock-ups of new UI
Ian Clarke skrev: > Feedback is welcome of course. I think it's a very good starting point :). Random thoughts: - Make a security level icon (like a wireless signal tray applet) showing your security status based on, for example, your darknet-opennet peer ratio. - Implement notifications like "freesite updated" in a sidebar or something. IMHO quite important. - Make some of the bookmarks available at the front page in one way or another. Chances are that the user wants to go straight to one of them. especially the indexes. - Show the version/build numbers in the status drop-down. Quite important for any kind of troubleshooting. - When Freenet is updating itself, show it in the status bar instead of a traditional notification. - Make the "f" in the "freenet" above the search box uppercase. Like the news header. - Zero3
[freenet-dev] Some (very) preliminary mock-ups of new UI
Cl?ment Vollet skrev: > One question though : will the new UI handle the download/upload list, and if > not, why? Ohh, like an AJAX-powered sidebar showing current download/uploads and their progresses? *drools* :D - Zero3
Re: [freenet-dev] Some (very) preliminary mock-ups of new UI
Clément Vollet skrev: One question though : will the new UI handle the download/upload list, and if not, why? Ohh, like an AJAX-powered sidebar showing current download/uploads and their progresses? *drools* :D - Zero3 ___ Devl mailing list Devl@freenetproject.org http://osprey.vm.bytemark.co.uk/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] Some (very) preliminary mock-ups of new UI
Ian Clarke skrev: Feedback is welcome of course. I think it's a very good starting point :). Random thoughts: - Make a security level icon (like a wireless signal tray applet) showing your security status based on, for example, your darknet-opennet peer ratio. - Implement notifications like freesite updated in a sidebar or something. IMHO quite important. - Make some of the bookmarks available at the front page in one way or another. Chances are that the user wants to go straight to one of them. especially the indexes. - Show the version/build numbers in the status drop-down. Quite important for any kind of troubleshooting. - When Freenet is updating itself, show it in the status bar instead of a traditional notification. - Make the f in the freenet above the search box uppercase. Like the news header. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://osprey.vm.bytemark.co.uk/cgi-bin/mailman/listinfo/devl
[freenet-dev] Deletion of content on old wiki
Should we delete content on the old wiki as we move and/or deprecate it? Or do we mark it as "checked" somehow? - Zero3
[freenet-dev] Deletion of content on old wiki
Should we delete content on the old wiki as we move and/or deprecate it? Or do we mark it as checked somehow? - Zero3 ___ Devl mailing list Devl@freenetproject.org http://osprey.vm.bytemark.co.uk/cgi-bin/mailman/listinfo/devl
[freenet-dev] What do we want to host ourselves?
Matthew Toseland skrev: > What do we want to host ourselves? > Clearly we don't want to host anything that can't be upgraded reasonably > easily. I.e. not Wikka. > > We already outsource our git repository (Github), and file downloads (Google > Code). > > The server currently runs: > - Mailing lists (Mailman); this could possibly be outsourced free. > - Several websites with and without SSL. This could be done on any php host, > but we need multiple IP addresses. > - MANTIS. This is quite heavy. > - Our current wiki Wikka (NOT PACKAGED, has to be manually kept up to date). > It will soon run: > - Two MediaWiki wiki's (doc-fr and our new wiki migrated from sourceforge). > This is reasonably easy to set up and upgrade, we can use the debian package > with multiple instances. > - Possibly Lurker, although there is an argument for entirely outsourcing > mailing list archives, or just relying on the very basic support built in to > mantis. > > A side-issue is whether we want help (volunteers) with system administration, > and whether we can trust people who come forward. Do we have any policy on > who should have root access? If you want to help then mail me ... Do we really want to host any of the above ourselves? IMHO we should outsource all these generic tasks. Our core expertise is developing the Freenet, not hosting websites/wikis/maillists/... on the internet. - Zero3
Re: [freenet-dev] What do we want to host ourselves?
Matthew Toseland skrev: What do we want to host ourselves? Clearly we don't want to host anything that can't be upgraded reasonably easily. I.e. not Wikka. We already outsource our git repository (Github), and file downloads (Google Code). The server currently runs: - Mailing lists (Mailman); this could possibly be outsourced free. - Several websites with and without SSL. This could be done on any php host, but we need multiple IP addresses. - MANTIS. This is quite heavy. - Our current wiki Wikka (NOT PACKAGED, has to be manually kept up to date). It will soon run: - Two MediaWiki wiki's (doc-fr and our new wiki migrated from sourceforge). This is reasonably easy to set up and upgrade, we can use the debian package with multiple instances. - Possibly Lurker, although there is an argument for entirely outsourcing mailing list archives, or just relying on the very basic support built in to mantis. A side-issue is whether we want help (volunteers) with system administration, and whether we can trust people who come forward. Do we have any policy on who should have root access? If you want to help then mail me ... Do we really want to host any of the above ourselves? IMHO we should outsource all these generic tasks. Our core expertise is developing the Freenet, not hosting websites/wikis/maillists/... on the internet. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://osprey.vm.bytemark.co.uk/cgi-bin/mailman/listinfo/devl
[freenet-dev] Uservoice update
Matthew Toseland skrev: > 3) Add a "pause" feature (188 votes) > > This might actually be partly due to the frequently fixed and re-broken > "Freenet doesn't restart after I change IP address / my laptop sleeps / etc" > bug. We need to fix that ASAP. > > It is also closely related to the general fact that it takes quite some time > for a node to get up to speed on opennet after it's been down for a while. I > have several ideas about how to improve that. We need to make Freenet more > low-uptime-friendly, even if that means using unreasonable levels of data > redundancy. > > It is also closely related to the system tray icon. We have one on Windows, > we will soon have one on Mac, once we have both I will write one for Linux. > > But the specific demand is that we have some means for the node to "pause" > its connections, so that it can get them back quickly. There has been much > debate on this on IRC, lists and the bug tracker, it is probably possible and > is related to some others ... > > Other options include just cutting the bandwidth limit or turning off the > client layer etc. If we can optimize start and stop, maybe a "pause" feature isn't even needed? Starting and stopping the service is already quite speedy. Sounds like the main problem is getting back into the network. > 4) use the port 80,443,53,1863 for comunication (171 votes) > > Remains remarkably popular! Note that UserVoice is easily spamable... Might not be as many users as you think. - Zero3
Re: [freenet-dev] Uservoice update
Matthew Toseland skrev: 3) Add a pause feature (188 votes) This might actually be partly due to the frequently fixed and re-broken Freenet doesn't restart after I change IP address / my laptop sleeps / etc bug. We need to fix that ASAP. It is also closely related to the general fact that it takes quite some time for a node to get up to speed on opennet after it's been down for a while. I have several ideas about how to improve that. We need to make Freenet more low-uptime-friendly, even if that means using unreasonable levels of data redundancy. It is also closely related to the system tray icon. We have one on Windows, we will soon have one on Mac, once we have both I will write one for Linux. But the specific demand is that we have some means for the node to pause its connections, so that it can get them back quickly. There has been much debate on this on IRC, lists and the bug tracker, it is probably possible and is related to some others ... Other options include just cutting the bandwidth limit or turning off the client layer etc. If we can optimize start and stop, maybe a pause feature isn't even needed? Starting and stopping the service is already quite speedy. Sounds like the main problem is getting back into the network. 4) use the port 80,443,53,1863 for comunication (171 votes) Remains remarkably popular! Note that UserVoice is easily spamable... Might not be as many users as you think. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Fwd: [Freenet 0003693]: Put before in XML indexes
He deleted it again: 2010-01-11 23:54 Mike Bush Note Added: 0006463 2010-01-12 00:03 Mike Bush Note Deleted: 0006463 ;) - Zero3 Matthew Toseland skrev: > What happened here? I can't see this note! > > > > > Emne: > [Freenet 0003693]: Put before in XML indexes > Fra: > Mantis Bug Tracker > Dato: > Mon, 11 Jan 2010 23:54:11 + > Til: > toad at amphibian.dyndns.org > > Til: > toad at amphibian.dyndns.org > > > A NOTE has been added to this issue. > == > https://bugs.freenetproject.org/view.php?id=3693 > == > Reported By:Matthew John Toseland (Toad) > Assigned To: > == > Project:Freenet > Issue ID: 3693 > Category: spider/librarian > Reproducibility:have not tried > Severity: minor > Priority: normal > Status: new > Target Version: 0.8.0 > == > Date Submitted: 2009-11-10 13:00 UTC > Last Modified: 2010-01-11 23:54 UTC > == > Summary:Put before in XML indexes > Description: > This would allow us to only parse once, saving *a lot* of disk > reads/writes/encrypts/decrypts. We will need to be back compatible in > parsing for a while, which can be best accomplished by a version number > change in the main document (index.xml). > == > Relationships ID Summary > -- > child of0003694 Decompress and parse in one action > == > > -- > (0006463) Mike Bush (reporter) - 2010-01-11 23:54 > https://bugs.freenetproject.org/view.php?id=3693#c6463 > -- > Doing it this way round would prevent the ability to produce partial > results, I'm in favour of scrapping them in the XMLIndex though since it's > not available in this version of the Library interface and the speed/memory > usage improvement is obviously much more important. The parser can be much > simpler without that provision too. > > If no one has started it, you can assign it to me. > > Issue History > Date ModifiedUsername FieldChange > == > 2009-11-10 13:00 Matthew John Toseland (Toad)New Issue > > > 2009-11-10 13:00 Matthew John Toseland (Toad)milestone => 0.8 > > > 2009-11-10 13:00 Matthew John Toseland (Toad)svn-revision => > > > 2009-11-10 13:33 Matthew John Toseland (Toad)Relationship added child of > 0003694 > 2009-11-19 08:18 Juiceman Issue Monitored: Juiceman > 2010-01-11 23:54 Mike Bush Note Added: 0006463 > == > > > > > > ___ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Opera Unite versus Freenet
Matthew Toseland skrev: > On Saturday 16 January 2010 15:19:32 David ?Bombe? Roden wrote: >> On Thursday 14 January 2010 17:18:31 Matthew Toseland wrote: >> >>> Content of Evil was uploaded from a dial-up modem for several years! >> A-HA! So you admit to being CofE? :) > > LOL, if I told you that I'd have to kill you. And no, I'm not CofE. Really. > As you'll easily conclude by going to read it (it's mirrored on 0.7). He said > he used a modem to upload it. /me looks suspiciously at Matthew :P - Zero3
Re: [freenet-dev] Fwd: [Freenet 0003693]: Put keywords before files in XML indexes
He deleted it again: 2010-01-11 23:54 Mike Bush Note Added: 0006463 2010-01-12 00:03 Mike Bush Note Deleted: 0006463 ;) - Zero3 Matthew Toseland skrev: What happened here? I can't see this note! Emne: [Freenet 0003693]: Put keywords before files in XML indexes Fra: Mantis Bug Tracker nore...@freenetproject.org Dato: Mon, 11 Jan 2010 23:54:11 + Til: t...@amphibian.dyndns.org Til: t...@amphibian.dyndns.org A NOTE has been added to this issue. == https://bugs.freenetproject.org/view.php?id=3693 == Reported By:Matthew John Toseland (Toad) Assigned To: == Project:Freenet Issue ID: 3693 Category: spider/librarian Reproducibility:have not tried Severity: minor Priority: normal Status: new Target Version: 0.8.0 == Date Submitted: 2009-11-10 13:00 UTC Last Modified: 2010-01-11 23:54 UTC == Summary:Put keywords before files in XML indexes Description: This would allow us to only parse once, saving *a lot* of disk reads/writes/encrypts/decrypts. We will need to be back compatible in parsing for a while, which can be best accomplished by a version number change in the main document (index.xml). == Relationships ID Summary -- child of0003694 Decompress and parse in one action == -- (0006463) Mike Bush (reporter) - 2010-01-11 23:54 https://bugs.freenetproject.org/view.php?id=3693#c6463 -- Doing it this way round would prevent the ability to produce partial results, I'm in favour of scrapping them in the XMLIndex though since it's not available in this version of the Library interface and the speed/memory usage improvement is obviously much more important. The parser can be much simpler without that provision too. If no one has started it, you can assign it to me. Issue History Date ModifiedUsername FieldChange == 2009-11-10 13:00 Matthew John Toseland (Toad)New Issue 2009-11-10 13:00 Matthew John Toseland (Toad)milestone = 0.8 2009-11-10 13:00 Matthew John Toseland (Toad)svn-revision = 2009-11-10 13:33 Matthew John Toseland (Toad)Relationship added child of 0003694 2009-11-19 08:18 Juiceman Issue Monitored: Juiceman 2010-01-11 23:54 Mike Bush Note Added: 0006463 == ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] False Kaspersky positives on Windows
With the help from ermanno, I've tracked down the reasons for failed Windows installs with Kaspersky. He was able to confirm that Kaspersky (at least on XP) falsely detects the installer as PDM.Worm.P2P.generic. Googling this reveals that it's a common bad heuristic that catches all kinds of things (for example: Adobe's Flash Player uninstaller). On top of my head, I see two posibilities: 1) Kaspersky finds the node code and realizes that this is indeed some kind of P2P. 2) Kaspersky freaks out over the local port scan the installer does to find a free fproxy and fcp port. I'm not sure which is most likely. What do we do now? Contact Kaspersky and ask them to fix their stuff? Or just directly warn users not to use Freenet with Kaspersky? - Zero3
[freenet-dev] False Kaspersky positives on Windows
With the help from ermanno, I've tracked down the reasons for failed Windows installs with Kaspersky. He was able to confirm that Kaspersky (at least on XP) falsely detects the installer as PDM.Worm.P2P.generic. Googling this reveals that it's a common bad heuristic that catches all kinds of things (for example: Adobe's Flash Player uninstaller). On top of my head, I see two posibilities: 1) Kaspersky finds the node code and realizes that this is indeed some kind of P2P. 2) Kaspersky freaks out over the local port scan the installer does to find a free fproxy and fcp port. I'm not sure which is most likely. What do we do now? Contact Kaspersky and ask them to fix their stuff? Or just directly warn users not to use Freenet with Kaspersky? - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Some feedback from a hostile environment
Matthew Toseland skrev: > On Monday 09 November 2009 15:31:51 Zero3 wrote: >> Matthew Toseland wrote: >>> Our friend has also localised the wininstaller (this is subject to >>> technical issues Zero3 hopefully will be able to resolve), and jSite (I >>> will deal with this soon). >> Yah. If anyone has a Windows setup with a cyrillic/chinese/japanese/... >> locale, I'd be grateful if they would do a little testing for me. > > Come on folks, there must be someone with a non-ascii-based Windows? :| I'd like to re-post a suggestion I made earlier: Add something like a "How to help" menu entry on the website where devs can post small things they need tested by the public. For example, on top of my head, I need: - Someone to test with Windows 7 - Someone to test with any 64-bit Windows - Someone to test with a cyrillic/chinese/japanese version of Windows - Someone to test with Kaspersky antivirus - ... Chances are that most people don't read these mailing lists (nor the bug tracker), but would be happy to help if there only was an easy way to get started. Such page would (IMHO) be a great way to get in contact with these people, and these people would have a very easy way of get started with Freenet development. In the end, it might even get us more long-term devs. - Zero3
[freenet-dev] Detecting the language in the installer
Matthew Toseland skrev: > On Saturday 21 November 2009 23:15:05 Matthew Toseland wrote: >> On Sunday 08 November 2009 11:09:54 Zero3 wrote: >>> Matthew Toseland wrote: >>>> I will make fproxy accept the windows locales. Should they be preceded >>>> with a prefix like WINDOWS0409? >>> Cool. Whatever you want :). The 4 chars alone are fine with me too. >> Done. Put "WINDOWS" in the node.l10n config, and it should Just Work. >> must be the language code, it must have four hexadecimal digits as per >> the table you mentioned. I put the codes in in upper case but it compares >> case-insensitively. >> > Is this done? > > > > > ___ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl Not yet. I've been AFK for a little while because of studies. It's a quick fix. I will do it as soon as I get back. Submitted here: https://bugs.freenetproject.org/view.php?id=3787 - Zero3
[freenet-dev] Uninstall survey still broken was Re: [wininstaller beta] Testing on Windows + Uninstall survey
Matthew Toseland skrev:
> On Saturday 03 October 2009 03:41:45 Zero3 wrote:
>> Matthew Toseland wrote:
>>> On Monday 24 August 2009 17:03:21 Zero3 wrote:
>>>> Matthew Toseland skrev:
>>>>> On Friday 21 August 2009 20:12:39 Zero3 wrote:
>>>>>> Matthew Toseland skrev:
>>>>>>> Here's another one:
>>>>>>>
>>>>>>> I accidentally built the installer with the beta branch. The tray icon
>>>>>>> worked, but when I uninstalled, and told it to do the survey, the
>>>>>>> survey failed (as usual), but control panel hung. Ideas? I think it
>>>>>>> might be waiting for firefox to close, but this is very bad behaviour,
>>>>>>> as there may be other stuff in firefox?
>>>>>>>
>>>>>>> I don't think this is specific to the beta branch - we wait for firefox
>>>>>>> (or whatever browser) to close before closing control panel.
>>>>>> Nop, it will not wait for the browser to close. It will exit right after
>>>>>> launching:
>>>>>>
>>>>>> [CODE]
>>>>>> If (_DoSurvey)
>>>>>> {
>>>>>> Run, http://freenetproject.org/uninstall.html, , UseErrorLevel
>>>>>> }
>>>>>>
>>>>>> Exit()
>>>>>> [/CODE]
>>>>>>
>>>>>> (The execute-and-wait-for-it-to-finish command is called "RunWait" as
>>>>>> opposed to the "Run" used here which will continue right away)
>>>>>>
>>>>>> Are you sure that freenetuninstaller.exe is running while the control
>>>>>> panel hangs?
>>>>> I don't know. I do know that control panel hangs until the browser exists.
>>>> Odd. Maybe it also considers processes spawned by the uninstaller as
>>>> part of the uninstaller itself, and does not return control to the
>>>> control panel until all of these have terminated. Would make sense, as
>>>> uninstallers often continue in other processes than the originally
>>>> executed one (the wininstaller uninstaller included).
>>>>
>>>> Nevertheless, this is a design choice by Microsoft. If they want to
>>>> freeze out the user while any part of an uninstaller is running, I
>>>> shouldn't try to (and probably can't) get around it.
>>> There must be a way to detach it.
>> There might be. No idea how much hacking it would take though. IMHO I
>> don't think the minor usability issue is worth the hack.
>>
>> On Vista I am able to close the control panel, although not start a new
>> uninstall before the browser is closed.
>>
>>>> A possible workaround could be to add a message to the survey completion
>>>> page simply asking the user to close the window.
>>> Unfortunately it's broken atm.
>> Any update on this? Please at least remove the survey from
>> http://freenetproject.org/uninstall.html and replace it with a
>> "Temporary out of order" message or something. We are seriously wasting
>> people's time right now.
>
> Google might fix it. After all they're a multibillion dollar company whose
> services have been used by everyone...
>
> But they haven't, and they've had years!
>
> Is it possible there's something wrong with *how we use google spreadsheets
> surveys*, not with google's tools themselves?
No matter what, we are completely wasting people's time by leaving it as
it is. Please, please, remove it.
- Zero3
Re: [freenet-dev] Uninstall survey still broken was Re: [wininstaller beta] Testing on Windows + Uninstall survey
Matthew Toseland skrev:
On Saturday 03 October 2009 03:41:45 Zero3 wrote:
Matthew Toseland wrote:
On Monday 24 August 2009 17:03:21 Zero3 wrote:
Matthew Toseland skrev:
On Friday 21 August 2009 20:12:39 Zero3 wrote:
Matthew Toseland skrev:
Here's another one:
I accidentally built the installer with the beta branch. The tray icon
worked, but when I uninstalled, and told it to do the survey, the
survey failed (as usual), but control panel hung. Ideas? I think it
might be waiting for firefox to close, but this is very bad behaviour,
as there may be other stuff in firefox?
I don't think this is specific to the beta branch - we wait for firefox
(or whatever browser) to close before closing control panel.
Nop, it will not wait for the browser to close. It will exit right after
launching:
[CODE]
If (_DoSurvey)
{
Run, http://freenetproject.org/uninstall.html, , UseErrorLevel
}
Exit()
[/CODE]
(The execute-and-wait-for-it-to-finish command is called RunWait as
opposed to the Run used here which will continue right away)
Are you sure that freenetuninstaller.exe is running while the control
panel hangs?
I don't know. I do know that control panel hangs until the browser exists.
Odd. Maybe it also considers processes spawned by the uninstaller as
part of the uninstaller itself, and does not return control to the
control panel until all of these have terminated. Would make sense, as
uninstallers often continue in other processes than the originally
executed one (the wininstaller uninstaller included).
Nevertheless, this is a design choice by Microsoft. If they want to
freeze out the user while any part of an uninstaller is running, I
shouldn't try to (and probably can't) get around it.
There must be a way to detach it.
There might be. No idea how much hacking it would take though. IMHO I
don't think the minor usability issue is worth the hack.
On Vista I am able to close the control panel, although not start a new
uninstall before the browser is closed.
A possible workaround could be to add a message to the survey completion
page simply asking the user to close the window.
Unfortunately it's broken atm.
Any update on this? Please at least remove the survey from
http://freenetproject.org/uninstall.html and replace it with a
Temporary out of order message or something. We are seriously wasting
people's time right now.
Google might fix it. After all they're a multibillion dollar company whose
services have been used by everyone...
But they haven't, and they've had years!
Is it possible there's something wrong with *how we use google spreadsheets
surveys*, not with google's tools themselves?
No matter what, we are completely wasting people's time by leaving it as
it is. Please, please, remove it.
- Zero3
___
Devl mailing list
Devl@freenetproject.org
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] Detecting the language in the installer
Matthew Toseland skrev: On Saturday 21 November 2009 23:15:05 Matthew Toseland wrote: On Sunday 08 November 2009 11:09:54 Zero3 wrote: Matthew Toseland wrote: I will make fproxy accept the windows locales. Should they be preceded with a prefix like WINDOWS0409? Cool. Whatever you want :). The 4 chars alone are fine with me too. Done. Put WINDOWS in the node.l10n config, and it should Just Work. must be the language code, it must have four hexadecimal digits as per the table you mentioned. I put the codes in in upper case but it compares case-insensitively. Is this done? ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl Not yet. I've been AFK for a little while because of studies. It's a quick fix. I will do it as soon as I get back. Submitted here: https://bugs.freenetproject.org/view.php?id=3787 - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] Some feedback from a hostile environment
Matthew Toseland skrev: On Monday 09 November 2009 15:31:51 Zero3 wrote: Matthew Toseland wrote: Our friend has also localised the wininstaller (this is subject to technical issues Zero3 hopefully will be able to resolve), and jSite (I will deal with this soon). Yah. If anyone has a Windows setup with a cyrillic/chinese/japanese/... locale, I'd be grateful if they would do a little testing for me. Come on folks, there must be someone with a non-ascii-based Windows? :| I'd like to re-post a suggestion I made earlier: Add something like a How to help menu entry on the website where devs can post small things they need tested by the public. For example, on top of my head, I need: - Someone to test with Windows 7 - Someone to test with any 64-bit Windows - Someone to test with a cyrillic/chinese/japanese version of Windows - Someone to test with Kaspersky antivirus - ... Chances are that most people don't read these mailing lists (nor the bug tracker), but would be happy to help if there only was an easy way to get started. Such page would (IMHO) be a great way to get in contact with these people, and these people would have a very easy way of get started with Freenet development. In the end, it might even get us more long-term devs. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Yet more Windows install failures (2)
Ximin Luo skrev: > Another one here, this time a "CreateService failed - Access is denied" > > https://bugs.freenetproject.org/view.php?id=3773 Cheers. Thanks for forwarding. I'm on it - see the report. - Zero3
Re: [freenet-dev] Yet more Windows install failures (2)
Ximin Luo skrev: Another one here, this time a CreateService failed - Access is denied https://bugs.freenetproject.org/view.php?id=3773 Cheers. Thanks for forwarding. I'm on it - see the report. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] New wiki
Ian Clarke skrev: > On Mon, Jan 4, 2010 at 10:57 AM, Christian Funder Sommerlund (Zero3) > mailto:lists at zero3.dk>> wrote: > > Ian Clarke skrev: > > Well, the obvious thing would be to host it on Emu, I was under the > > vague impression that this was the plan but I must confess that I > wasn't > > paying close attention to that discussion. > > FYI: One of the main reason we are switching is that we are trying to > get rid of Emu to save the cost and maintenance. > > > Right, but realistically I don't think that is going to happen any time > soon, given how long we've been talking about it and how little progress > has been made. It certainly won't happen until we move things like the wiki and bugtracker off Emu, no ;). (My two eurocents are that Mediawiki and SF are not the optimal solutions, but a far better one than doing nothing and holding back our overall hosting roadmap. So if this is the choice made, I will support it and do my part in getting the best out of it.) - Zero3
[freenet-dev] New wiki
Ian Clarke skrev: > Well, the obvious thing would be to host it on Emu, I was under the > vague impression that this was the plan but I must confess that I wasn't > paying close attention to that discussion. FYI: One of the main reason we are switching is that we are trying to get rid of Emu to save the cost and maintenance. - Zero3
[freenet-dev] Yet more Windows install failures
Matthew Toseland skrev: > One theory for this is that icacls.exe is 64-bit on win64 and therefore isn't > a valid win32 app when called from 32-bit wrapper or AHK code. However, why > do we need to call icacls.exe at all in the new installer, given that we > don't create a user? And even if it fails, so what, why should that break > anything else? Yes, that is most likely the reason. IIRC NetworkService (the user account we now use) doesn't by default have read-write access to our files. Can someone verify on XP/Vista/Win7? If icacls fails, the installer will continue anyway. However, since the node didn't work, chances are that we did indeed need to apply the permissions. > Another theory is that there is difficulty in detecting the JVM on win64. One > solution is to let it pick it up from the registry, see my other mail - it > will only pick up the 32-bit version, but that is okay, the 64-bit version > isn't autoupdated and may not be terribly reliable... However, in the below > log, it was attempted to hard-code the path to the 64-bit java exe (which > works for other people). I'm not so sure: [22:46:01] It only has one line: STATUS | wrapper | 2010/01/03 15:03:54 | Freenet background service installed. This means that the service installation succeeded (or at least the wrapper thinks so), but it was never attempted started. This means that the Windows start.exe fails, which the mentioned "didn't respond to signal" errors confirm. This means that Service_Start() in src_freenethelpers/FreenetStart.ahk fails to start the service before the 120 second timeout kicks in and throws that error. It would be interesting to know if the service actually has been created, as the wrapper claims. If it has, I need to look into why Service_Start() fails. Of course this could be caused by the lack of proper permissions because icacls failed... We should figure that out first. > Thoughts? This is a blocker: Freenet must install reliably on 80% of win64 > systems before releasing 0.8.0! We need a 64-bit tester then... It's kind of hard to develop something for a system you neither own nor has access to in one way or another. > Also, Freenet must install reliably on Windows 7 before releasing 0.8.0. > Right now the installer doesn't support it. It's true that it's not officially supported, but I've seen both successful and failed Win7 installs. Again, I need a tester before I can start tracking down bugs. - Zero3
[freenet-dev] Detect Java location from registry rather than path
Matthew Toseland skrev: > We can improve the wrapper's reliability on Windows (especially 64-bit) by > finding Java from the registry rather than the path: > > wrapper.java.command=java > = Use system path > wrapper.java.command= > = (ON WINDOWS ONLY) Use registry and put into WRAPPER_JAVA_HOME. > > http://wrapper.tanukisoftware.org/doc/english/prop-java-command.html I agree. https://bugs.freenetproject.org/view.php?id=3766 - Zero3
Re: [freenet-dev] Detect Java location from registry rather than path
Matthew Toseland skrev: We can improve the wrapper's reliability on Windows (especially 64-bit) by finding Java from the registry rather than the path: wrapper.java.command=java = Use system path wrapper.java.command= = (ON WINDOWS ONLY) Use registry and put into WRAPPER_JAVA_HOME. http://wrapper.tanukisoftware.org/doc/english/prop-java-command.html I agree. https://bugs.freenetproject.org/view.php?id=3766 - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] Yet more Windows install failures
Matthew Toseland skrev: One theory for this is that icacls.exe is 64-bit on win64 and therefore isn't a valid win32 app when called from 32-bit wrapper or AHK code. However, why do we need to call icacls.exe at all in the new installer, given that we don't create a user? And even if it fails, so what, why should that break anything else? Yes, that is most likely the reason. IIRC NetworkService (the user account we now use) doesn't by default have read-write access to our files. Can someone verify on XP/Vista/Win7? If icacls fails, the installer will continue anyway. However, since the node didn't work, chances are that we did indeed need to apply the permissions. Another theory is that there is difficulty in detecting the JVM on win64. One solution is to let it pick it up from the registry, see my other mail - it will only pick up the 32-bit version, but that is okay, the 64-bit version isn't autoupdated and may not be terribly reliable... However, in the below log, it was attempted to hard-code the path to the 64-bit java exe (which works for other people). I'm not so sure: [22:46:01] qwebirc20693 It only has one line: STATUS | wrapper | 2010/01/03 15:03:54 | Freenet background service installed. This means that the service installation succeeded (or at least the wrapper thinks so), but it was never attempted started. This means that the Windows start.exe fails, which the mentioned didn't respond to signal errors confirm. This means that Service_Start() in src_freenethelpers/FreenetStart.ahk fails to start the service before the 120 second timeout kicks in and throws that error. It would be interesting to know if the service actually has been created, as the wrapper claims. If it has, I need to look into why Service_Start() fails. Of course this could be caused by the lack of proper permissions because icacls failed... We should figure that out first. Thoughts? This is a blocker: Freenet must install reliably on 80% of win64 systems before releasing 0.8.0! We need a 64-bit tester then... It's kind of hard to develop something for a system you neither own nor has access to in one way or another. Also, Freenet must install reliably on Windows 7 before releasing 0.8.0. Right now the installer doesn't support it. It's true that it's not officially supported, but I've seen both successful and failed Win7 installs. Again, I need a tester before I can start tracking down bugs. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] New wiki
Ian Clarke skrev: Well, the obvious thing would be to host it on Emu, I was under the vague impression that this was the plan but I must confess that I wasn't paying close attention to that discussion. FYI: One of the main reason we are switching is that we are trying to get rid of Emu to save the cost and maintenance. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] New wiki
Ian Clarke skrev: On Mon, Jan 4, 2010 at 10:57 AM, Christian Funder Sommerlund (Zero3) li...@zero3.dk mailto:li...@zero3.dk wrote: Ian Clarke skrev: Well, the obvious thing would be to host it on Emu, I was under the vague impression that this was the plan but I must confess that I wasn't paying close attention to that discussion. FYI: One of the main reason we are switching is that we are trying to get rid of Emu to save the cost and maintenance. Right, but realistically I don't think that is going to happen any time soon, given how long we've been talking about it and how little progress has been made. It certainly won't happen until we move things like the wiki and bugtracker off Emu, no ;). (My two eurocents are that Mediawiki and SF are not the optimal solutions, but a far better one than doing nothing and holding back our overall hosting roadmap. So if this is the choice made, I will support it and do my part in getting the best out of it.) - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Blog comments on difficulties uninstalling Freenet
(This is about the Linux installer) - Zero3 Ian Clarke skrev: > This guy raises concerns about uninstalling Freenet: > > > http://truefalsebollox.blogspot.com/2009/11/freenet-users-watch-your-back.html > > Ian. > > -- > Ian Clarke > CEO, Uprizer Labs > Email: ian at uprizer.com <mailto:ian at uprizer.com> > Ph: +1 512 422 3588 > > > > > ___ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] Blog comments on difficulties uninstalling Freenet
(This is about the Linux installer) - Zero3 Ian Clarke skrev: This guy raises concerns about uninstalling Freenet: http://truefalsebollox.blogspot.com/2009/11/freenet-users-watch-your-back.html Ian. -- Ian Clarke CEO, Uprizer Labs Email: i...@uprizer.com mailto:i...@uprizer.com Ph: +1 512 422 3588 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Freenet tray icon
Hey Thanks for the feedback :). ~200 context switches per second (or whatever interval we are talking about here) does sound like a lot in light of how little work the tray icon has when idling. This is not a problem at all for modern CPUs though. Note that Chrome - one of the lightest browsers available - in that screenshot triggers 10x this number (not meant as an excuse, but rather to illustrate how small a number we are talking about). What the tray icon actually does when idle is to check the service status and look for a killfile every 5 seconds. I suspect that the cause of these context switches are the timer for these check. I'm not entirely sure how the timers are implemented in Autohotkey (the language the tray manager is coded in), but chances are that the implementation is less-than-ideal for our purpose. Nevertheless, we are (IMHO) talking very fine details here. In the perfect world, with unlimited time, it might be worth looking into. But in the real world, there are so many more important things to work at than worrying about a couple of hundred context switches :). - Zero3 Ian Clarke skrev: > My wife made the following discovery about the Windows Freenet tray icon: > > -- Forwarded message -- > From: *Janie Mehew* <...> > Date: Fri, Dec 4, 2009 at 11:33 AM > Subject: Freenet tray icon - forward to mailing list > To: Ian Clarke mailto:ian.clarke at gmail.com>> > > > Hi, > > I have noticed that the freenet tray icon seems to be using more > resources than it needs to. If I open process explorer, and sort the > entries by CSwitch Delta, the freenettray.exe program is always in the > top 5-10. On my computer it seems to be around 200 per update interval. > This indicates that the tray icon is using more CPU than it probably > needs to. For an explanation, see here: > > http://blogs.technet.com/sysinternals/archive/2004/04/27/452830.aspx > > By comparison, my product's tray icon polls our service over RPC every > few seconds, and never seems to have a CSwitch delta higher than 5. > > I've attached a screenshot of process explorer. > > Janie > > > > -- > Ian Clarke > CEO, Uprizer Labs > Email: ian at uprizer.com <mailto:ian at uprizer.com> > Ph: +1 512 422 3588 > > > > > > > ___ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] Freenet tray icon
Hey Thanks for the feedback :). ~200 context switches per second (or whatever interval we are talking about here) does sound like a lot in light of how little work the tray icon has when idling. This is not a problem at all for modern CPUs though. Note that Chrome - one of the lightest browsers available - in that screenshot triggers 10x this number (not meant as an excuse, but rather to illustrate how small a number we are talking about). What the tray icon actually does when idle is to check the service status and look for a killfile every 5 seconds. I suspect that the cause of these context switches are the timer for these check. I'm not entirely sure how the timers are implemented in Autohotkey (the language the tray manager is coded in), but chances are that the implementation is less-than-ideal for our purpose. Nevertheless, we are (IMHO) talking very fine details here. In the perfect world, with unlimited time, it might be worth looking into. But in the real world, there are so many more important things to work at than worrying about a couple of hundred context switches :). - Zero3 Ian Clarke skrev: My wife made the following discovery about the Windows Freenet tray icon: -- Forwarded message -- From: *Janie Mehew* ... Date: Fri, Dec 4, 2009 at 11:33 AM Subject: Freenet tray icon - forward to mailing list To: Ian Clarke ian.cla...@gmail.com mailto:ian.cla...@gmail.com Hi, I have noticed that the freenet tray icon seems to be using more resources than it needs to. If I open process explorer, and sort the entries by CSwitch Delta, the freenettray.exe program is always in the top 5-10. On my computer it seems to be around 200 per update interval. This indicates that the tray icon is using more CPU than it probably needs to. For an explanation, see here: http://blogs.technet.com/sysinternals/archive/2004/04/27/452830.aspx By comparison, my product's tray icon polls our service over RPC every few seconds, and never seems to have a CSwitch delta higher than 5. I've attached a screenshot of process explorer. Janie -- Ian Clarke CEO, Uprizer Labs Email: i...@uprizer.com mailto:i...@uprizer.com Ph: +1 512 422 3588 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Web-pushing very important for 0.8.0?
Evan Daniel skrev: > On Tue, Nov 24, 2009 at 2:32 PM, Matthew Toseland > wrote: >>> I see 4 basic options. First, we could wait for GWT to support XHTML. >> Not a good option IMHO, although timing and priorities re merging and >> enabling web-pushing are debatable... > > I assume Google hasn't commented on a time frame for XHTML support? > I'm inclined to agree that we shouldn't wait on some unscheduled thing > that may or may not happen. If http://code.google.com/p/google-web-toolkit/issues/detail?id=710 is the issue you are talking about, then "Not currently feasible." :/ - Zero3
Re: [freenet-dev] Web-pushing very important for 0.8.0?
Evan Daniel skrev: On Tue, Nov 24, 2009 at 2:32 PM, Matthew Toseland t...@amphibian.dyndns.org wrote: I see 4 basic options. First, we could wait for GWT to support XHTML. Not a good option IMHO, although timing and priorities re merging and enabling web-pushing are debatable... I assume Google hasn't commented on a time frame for XHTML support? I'm inclined to agree that we shouldn't wait on some unscheduled thing that may or may not happen. If http://code.google.com/p/google-web-toolkit/issues/detail?id=710 is the issue you are talking about, then Not currently feasible. :/ - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] ground-up GUI redesign
Ian Clarke skrev: > I think our current problem is that despite our best efforts, the > current UI is built "from the code forward", rather than "from the user > back", and as such I think it is fundamentally flawed. Despite how much > we try, I think it is very difficult for us to put ourselves in the > shoes of an ordinary Freenet user, we are already too immersed in the > concepts and jargon of Freenet. One of the main issues (IMHO) is that modifying the current GUI is nearly impossible as a contributing user. There are no theme templates available to easily play around with. Last I heard was that you have to actually recompile Freenet if you want to make any GUI changes besides smallish CSS hacks :/. I think we have a long standing bug report somewhere about the implementation of a theming engine... - Zero3 (who is now writing from a new mail account)
Re: [freenet-dev] ground-up GUI redesign
Ian Clarke skrev: I think our current problem is that despite our best efforts, the current UI is built from the code forward, rather than from the user back, and as such I think it is fundamentally flawed. Despite how much we try, I think it is very difficult for us to put ourselves in the shoes of an ordinary Freenet user, we are already too immersed in the concepts and jargon of Freenet. One of the main issues (IMHO) is that modifying the current GUI is nearly impossible as a contributing user. There are no theme templates available to easily play around with. Last I heard was that you have to actually recompile Freenet if you want to make any GUI changes besides smallish CSS hacks :/. I think we have a long standing bug report somewhere about the implementation of a theming engine... - Zero3 (who is now writing from a new mail account) ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] selecting browser for Launch Freenet from systray
Matthew Toseland wrote: > On Tuesday 17 November 2009 07:20:03 Zero3 wrote: >> Matthew Toseland wrote: >>> On Sunday 15 November 2009 01:14:54 Ed Tomlinson wrote: >>>> On Saturday 14 November 2009 16:02:11 Matthew Toseland wrote: >>>>> On Saturday 14 November 2009 17:19:15 Ed Tomlinson wrote: >>>>>> Hi, >>>>>> >>>>>> For a test I installed freenet on a windows 7 box. All went well. The >>>>>> new installation process is pretty simple. One small bone to pick. The >>>>>> first use wizard tells you NOT to use the same browser for freenet as >>>>>> you use normally - fine. However there does not seem to be a way to >>>>>> configure 'Launch Freenet' from the systray to use your prefered >>>>>> browser. I want to set it to use chrome... >>>>> It *does* use Chrome if available, in incognito mode. Ask Zero3 why it >>>>> isn't working. >>>>>> This should be easy but it does not seem to be... >>>> Think the problem is that I installed chrome after freenet and it _is_ >>>> what I want freenet to use. I see no option to tell freenet to switch to >>>> it. >>> That is odd, I thought it detected it in the launcher at launch time? Have >>> you filed a bug about this? >> It does. If you read his previous reply, you will see that Microsoft >> changed the registry path for uninstall entries in 64-bit Win7 (and >> possibly 64-bit Vista/XP too?). Which means the launcher won't find >> Chrome on these systems... >> >> I need to figure out which versions that use the changed path, and >> change the launcher for these versions. > > Looks like that's simply due to installing a 32-bit Chrome on a 64-bit > Windows... Hmm. Maybe. But that would mean that our own uninstallation entry would be "relocated" on those systems as well. Which means uninstallation might not work as predicted. In any way, I need to sort out exactly what happens - and when it happens. - Zero3
[freenet-dev] selecting browser for Launch Freenet from systray
Matthew Toseland wrote: > On Sunday 15 November 2009 01:14:54 Ed Tomlinson wrote: >> On Saturday 14 November 2009 16:02:11 Matthew Toseland wrote: >>> On Saturday 14 November 2009 17:19:15 Ed Tomlinson wrote: >>>> Hi, >>>> >>>> For a test I installed freenet on a windows 7 box. All went well. The >>>> new installation process is pretty simple. One small bone to pick. The >>>> first use wizard tells you NOT to use the same browser for freenet as you >>>> use normally - fine. However there does not seem to be a way to configure >>>> 'Launch Freenet' from the systray to use your prefered browser. I want to >>>> set it to use chrome... >>> It *does* use Chrome if available, in incognito mode. Ask Zero3 why it >>> isn't working. >>>> This should be easy but it does not seem to be... >> Think the problem is that I installed chrome after freenet and it _is_ what >> I want freenet to use. I see no option to tell freenet to switch to it. > > That is odd, I thought it detected it in the launcher at launch time? Have > you filed a bug about this? It does. If you read his previous reply, you will see that Microsoft changed the registry path for uninstall entries in 64-bit Win7 (and possibly 64-bit Vista/XP too?). Which means the launcher won't find Chrome on these systems... I need to figure out which versions that use the changed path, and change the launcher for these versions. - Zero3
Re: [freenet-dev] selecting browser for Launch Freenet from systray
Matthew Toseland wrote: On Tuesday 17 November 2009 07:20:03 Zero3 wrote: Matthew Toseland wrote: On Sunday 15 November 2009 01:14:54 Ed Tomlinson wrote: On Saturday 14 November 2009 16:02:11 Matthew Toseland wrote: On Saturday 14 November 2009 17:19:15 Ed Tomlinson wrote: Hi, For a test I installed freenet on a windows 7 box. All went well. The new installation process is pretty simple. One small bone to pick. The first use wizard tells you NOT to use the same browser for freenet as you use normally - fine. However there does not seem to be a way to configure 'Launch Freenet' from the systray to use your prefered browser. I want to set it to use chrome... It *does* use Chrome if available, in incognito mode. Ask Zero3 why it isn't working. This should be easy but it does not seem to be... Think the problem is that I installed chrome after freenet and it _is_ what I want freenet to use. I see no option to tell freenet to switch to it. That is odd, I thought it detected it in the launcher at launch time? Have you filed a bug about this? It does. If you read his previous reply, you will see that Microsoft changed the registry path for uninstall entries in 64-bit Win7 (and possibly 64-bit Vista/XP too?). Which means the launcher won't find Chrome on these systems... I need to figure out which versions that use the changed path, and change the launcher for these versions. Looks like that's simply due to installing a 32-bit Chrome on a 64-bit Windows... Hmm. Maybe. But that would mean that our own uninstallation entry would be relocated on those systems as well. Which means uninstallation might not work as predicted. In any way, I need to sort out exactly what happens - and when it happens. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] selecting browser for Launch Freenet from systray
Matthew Toseland wrote: On Sunday 15 November 2009 01:14:54 Ed Tomlinson wrote: On Saturday 14 November 2009 16:02:11 Matthew Toseland wrote: On Saturday 14 November 2009 17:19:15 Ed Tomlinson wrote: Hi, For a test I installed freenet on a windows 7 box. All went well. The new installation process is pretty simple. One small bone to pick. The first use wizard tells you NOT to use the same browser for freenet as you use normally - fine. However there does not seem to be a way to configure 'Launch Freenet' from the systray to use your prefered browser. I want to set it to use chrome... It *does* use Chrome if available, in incognito mode. Ask Zero3 why it isn't working. This should be easy but it does not seem to be... Think the problem is that I installed chrome after freenet and it _is_ what I want freenet to use. I see no option to tell freenet to switch to it. That is odd, I thought it detected it in the launcher at launch time? Have you filed a bug about this? It does. If you read his previous reply, you will see that Microsoft changed the registry path for uninstall entries in 64-bit Win7 (and possibly 64-bit Vista/XP too?). Which means the launcher won't find Chrome on these systems... I need to figure out which versions that use the changed path, and change the launcher for these versions. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] selecting browser for Launch Freenet from systray
Ed Tomlinson wrote: > On Saturday 14 November 2009 21:19:43 Zero3 wrote: >> Ed Tomlinson wrote: >> If you install Chrome, the launcher should pick it up at next launch. More specifically, it will look for the registry string "InstallLocation" under "HKEY_CURRENT_USER, Software\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome". Can you check if you have that key? >> Does not exist. I installed the 64 bit version. The uninstall entry is at: > HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432\Microsoft\Windows\CurrentVersion\Unistall\Google Chrome Argh. Why on earth did they change that? Is that true for all versions of 64-bit Windows? Win7? Vista? (XP?). >> I'm surprised you were able to install on Win7. I haven't tested the installer on Win7 myself yet, and I've seen reports of installations failures on Win7. It just worked out of the box? > > Aside from the chrome issue it worked as expected. Cool :o. - Zero3
[freenet-dev] selecting browser for Launch Freenet from systray
Ed Tomlinson wrote: > On Saturday 14 November 2009 16:02:11 Matthew Toseland wrote: >> On Saturday 14 November 2009 17:19:15 Ed Tomlinson wrote: >>> Hi, >>> >>> For a test I installed freenet on a windows 7 box. All went well. The new >>> installation process is pretty simple. One small bone to pick. The first >>> use wizard tells you NOT to use the same browser for freenet as you use >>> normally - fine. However there does not seem to be a way to configure >>> 'Launch Freenet' from the systray to use your prefered browser. I want to >>> set it to use chrome... >> It *does* use Chrome if available, in incognito mode. Ask Zero3 why it isn't >> working. >>> This should be easy but it does not seem to be... > > Think the problem is that I installed chrome after freenet and it _is_ what I > want freenet to use. I see no option to tell freenet to switch to it. Thanks for the feedback :) Here is the deal: At the moment, there is a great difference in security between the major browsers. Especially their incognito mode support. For that reason, the launcher will dictate the choice of browser for the user by trying to find the most secure one available on every launch. If you install Chrome, the launcher should pick it up at next launch. More specifically, it will look for the registry string "InstallLocation" under "HKEY_CURRENT_USER, Software\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome". Can you check if you have that key? The fproxy message is a bit old. It was made at a time where the plan was to install a secondary browser/browser profile for the user, and use that one solely for Freenet. As browsers in the meantime have started to incorporate incognito modes, we are moving towards using those instead (and IMHO, it is a much better solution. Last time we tried the profile stuff - with FireFox - we failed miserably). I'm surprised you were able to install on Win7. I haven't tested the installer on Win7 myself yet, and I've seen reports of installations failures on Win7. It just worked out of the box? - Zero3
Re: [freenet-dev] selecting browser for Launch Freenet from systray
Ed Tomlinson wrote: On Saturday 14 November 2009 21:19:43 Zero3 wrote: Ed Tomlinson wrote: If you install Chrome, the launcher should pick it up at next launch. More specifically, it will look for the registry string InstallLocation under HKEY_CURRENT_USER, Software\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome. Can you check if you have that key? Does not exist. I installed the 64 bit version. The uninstall entry is at: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432\Microsoft\Windows\CurrentVersion\Unistall\Google Chrome Argh. Why on earth did they change that? Is that true for all versions of 64-bit Windows? Win7? Vista? (XP?). I'm surprised you were able to install on Win7. I haven't tested the installer on Win7 myself yet, and I've seen reports of installations failures on Win7. It just worked out of the box? Aside from the chrome issue it worked as expected. Cool :o. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] selecting browser for Launch Freenet from systray
Ed Tomlinson wrote: On Saturday 14 November 2009 16:02:11 Matthew Toseland wrote: On Saturday 14 November 2009 17:19:15 Ed Tomlinson wrote: Hi, For a test I installed freenet on a windows 7 box. All went well. The new installation process is pretty simple. One small bone to pick. The first use wizard tells you NOT to use the same browser for freenet as you use normally - fine. However there does not seem to be a way to configure 'Launch Freenet' from the systray to use your prefered browser. I want to set it to use chrome... It *does* use Chrome if available, in incognito mode. Ask Zero3 why it isn't working. This should be easy but it does not seem to be... Think the problem is that I installed chrome after freenet and it _is_ what I want freenet to use. I see no option to tell freenet to switch to it. Thanks for the feedback :) Here is the deal: At the moment, there is a great difference in security between the major browsers. Especially their incognito mode support. For that reason, the launcher will dictate the choice of browser for the user by trying to find the most secure one available on every launch. If you install Chrome, the launcher should pick it up at next launch. More specifically, it will look for the registry string InstallLocation under HKEY_CURRENT_USER, Software\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome. Can you check if you have that key? The fproxy message is a bit old. It was made at a time where the plan was to install a secondary browser/browser profile for the user, and use that one solely for Freenet. As browsers in the meantime have started to incorporate incognito modes, we are moving towards using those instead (and IMHO, it is a much better solution. Last time we tried the profile stuff - with FireFox - we failed miserably). I'm surprised you were able to install on Win7. I haven't tested the installer on Win7 myself yet, and I've seen reports of installations failures on Win7. It just worked out of the box? - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Website downloads page feedback
Matthew Toseland wrote: > On Tuesday 10 November 2009 23:12:03 Zero3 wrote: >> Feedback for the website downloads page: >> >> "We strongly recommend you use the links on the start menu to shut down >> Freenet when you play computer games, and start it back up afterwards. >> We will implement a system tray icon for this in future." >> >> This is implemented now. >> >> "Freenet works best with Windows XP Professional. Freenet will run on >> Vista and Windows 7 but the uninstaller is not perfect on those systems." >> >> The wininstaller works smoothly on both XP and Vista now the beta has >> been rolled out. >> >> Windows 7 is *not* supported at this time. I've seen several Win7 bug >> reports, so until I have time to look at Win7 support we should >> discourage using Freenet on Win7. >> >> "You can access Freenet later on via the Browse Freenet icon on the >> desktop and your start menu. If the browser window isn't opened, " >> >> On Windows, the main method of accessing Freenet is now via the tray >> menu. Alternatively the start menu. We don't add a desktop shortcut by >> default any more. >> >> " for example because you used the headless installer" >> >> Most people won't know what a "headless installer" is. >> >> "Recommended: 1GHz or more processor with 512MB RAM or more (especially >> if using Windows XP)" >> >> As opposed to? Win2k? Vista? Win7? >> >> "Windows users can upgrade to the latest-stable Freenet release by >> clicking on "update.cmd" in the Freenet directory." >> >> On Windows, this is now implemented in the tray manager. > > So we probably need to split it up by OS? Or maybe not ... > > We do need to mention that on 64-bit Windows we use a 32-bit JVM which may > not be auto-updated, since this trips people up from time to time? Until Linux and Mac has tray support, I guess we should split it up. Yea, if that is the case (i can't figure out what is up and down with this 32-bit vs. 64-bit stuff), we should mention that people with 64-bit Windows without Java will be offered to install a 32-bit Java. - Zero3
[freenet-dev] Website downloads page feedback
Feedback for the website downloads page: "We strongly recommend you use the links on the start menu to shut down Freenet when you play computer games, and start it back up afterwards. We will implement a system tray icon for this in future." This is implemented now. "Freenet works best with Windows XP Professional. Freenet will run on Vista and Windows 7 but the uninstaller is not perfect on those systems." The wininstaller works smoothly on both XP and Vista now the beta has been rolled out. Windows 7 is *not* supported at this time. I've seen several Win7 bug reports, so until I have time to look at Win7 support we should discourage using Freenet on Win7. "You can access Freenet later on via the Browse Freenet icon on the desktop and your start menu. If the browser window isn't opened, " On Windows, the main method of accessing Freenet is now via the tray menu. Alternatively the start menu. We don't add a desktop shortcut by default any more. " for example because you used the headless installer" Most people won't know what a "headless installer" is. "Recommended: 1GHz or more processor with 512MB RAM or more (especially if using Windows XP)" As opposed to? Win2k? Vista? Win7? "Windows users can upgrade to the latest-stable Freenet release by clicking on "update.cmd" in the Freenet directory." On Windows, this is now implemented in the tray manager. - Zero3
Re: [freenet-dev] Website downloads page feedback
Matthew Toseland wrote: On Tuesday 10 November 2009 23:12:03 Zero3 wrote: Feedback for the website downloads page: We strongly recommend you use the links on the start menu to shut down Freenet when you play computer games, and start it back up afterwards. We will implement a system tray icon for this in future. This is implemented now. Freenet works best with Windows XP Professional. Freenet will run on Vista and Windows 7 but the uninstaller is not perfect on those systems. The wininstaller works smoothly on both XP and Vista now the beta has been rolled out. Windows 7 is *not* supported at this time. I've seen several Win7 bug reports, so until I have time to look at Win7 support we should discourage using Freenet on Win7. You can access Freenet later on via the Browse Freenet icon on the desktop and your start menu. If the browser window isn't opened, On Windows, the main method of accessing Freenet is now via the tray menu. Alternatively the start menu. We don't add a desktop shortcut by default any more. for example because you used the headless installer Most people won't know what a headless installer is. Recommended: 1GHz or more processor with 512MB RAM or more (especially if using Windows XP) As opposed to? Win2k? Vista? Win7? Windows users can upgrade to the latest-stable Freenet release by clicking on update.cmd in the Freenet directory. On Windows, this is now implemented in the tray manager. So we probably need to split it up by OS? Or maybe not ... We do need to mention that on 64-bit Windows we use a 32-bit JVM which may not be auto-updated, since this trips people up from time to time? Until Linux and Mac has tray support, I guess we should split it up. Yea, if that is the case (i can't figure out what is up and down with this 32-bit vs. 64-bit stuff), we should mention that people with 64-bit Windows without Java will be offered to install a 32-bit Java. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Some feedback from a hostile environment
Matthew Toseland wrote: > https://bugs.freenetproject.org/view.php?id=3697 > Zero3, any chance of writing the total system memory to a file in the > wininstaller in the near future? No problem. 1) I assume we are talking about physical memory here? 2) Do we look at total memory available or memory currently free? 3) Exactly what should it write, and where? 4) Shall I implement this in the installer (only set once) or the launcher? (set every time user launches Freenet via our shortcuts) 5) Would it be a good idea to deny installation if the user doesn't meet the minimum requirements? - Zero3
Re: [freenet-dev] Some feedback from a hostile environment
Matthew Toseland wrote: https://bugs.freenetproject.org/view.php?id=3697 Zero3, any chance of writing the total system memory to a file in the wininstaller in the near future? No problem. 1) I assume we are talking about physical memory here? 2) Do we look at total memory available or memory currently free? 3) Exactly what should it write, and where? 4) Shall I implement this in the installer (only set once) or the launcher? (set every time user launches Freenet via our shortcuts) 5) Would it be a good idea to deny installation if the user doesn't meet the minimum requirements? - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Website downloads page feedback
Feedback for the website downloads page: We strongly recommend you use the links on the start menu to shut down Freenet when you play computer games, and start it back up afterwards. We will implement a system tray icon for this in future. This is implemented now. Freenet works best with Windows XP Professional. Freenet will run on Vista and Windows 7 but the uninstaller is not perfect on those systems. The wininstaller works smoothly on both XP and Vista now the beta has been rolled out. Windows 7 is *not* supported at this time. I've seen several Win7 bug reports, so until I have time to look at Win7 support we should discourage using Freenet on Win7. You can access Freenet later on via the Browse Freenet icon on the desktop and your start menu. If the browser window isn't opened, On Windows, the main method of accessing Freenet is now via the tray menu. Alternatively the start menu. We don't add a desktop shortcut by default any more. for example because you used the headless installer Most people won't know what a headless installer is. Recommended: 1GHz or more processor with 512MB RAM or more (especially if using Windows XP) As opposed to? Win2k? Vista? Win7? Windows users can upgrade to the latest-stable Freenet release by clicking on update.cmd in the Freenet directory. On Windows, this is now implemented in the tray manager. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Some feedback from a hostile environment
Matthew Toseland wrote: > Our friend has also localised the wininstaller (this is subject to technical > issues Zero3 hopefully will be able to resolve), and jSite (I will deal with > this soon). Yah. If anyone has a Windows setup with a cyrillic/chinese/japanese/... locale, I'd be grateful if they would do a little testing for me. - Zero3
Re: [freenet-dev] Some feedback from a hostile environment
Matthew Toseland wrote: Our friend has also localised the wininstaller (this is subject to technical issues Zero3 hopefully will be able to resolve), and jSite (I will deal with this soon). Yah. If anyone has a Windows setup with a cyrillic/chinese/japanese/... locale, I'd be grateful if they would do a little testing for me. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Detecting the language in the installer
Matthew Toseland wrote: > I will make fproxy accept the windows locales. Should they be preceded with a > prefix like WINDOWS0409? Cool. Whatever you want :). The 4 chars alone are fine with me too. - Zero3
Re: [freenet-dev] Detecting the language in the installer
Matthew Toseland wrote: I will make fproxy accept the windows locales. Should they be preceded with a prefix like WINDOWS0409? Cool. Whatever you want :). The 4 chars alone are fine with me too. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Detecting the language in the installer
Matthew Toseland wrote: > Does autodetecting the language from the OS work in the wininstaller now? If > not, what do we need to do to make it work? What kind of language codes will > Windows return us? Autodetecting has always worked in the wininstaller, but the setting passed on to fproxy has been more or less guesswork. At the moment the localized name of the language will be passed on via freenet.ini. This is highly unsuitable and will only work in some lucky cases. Windows gives us a Windows locale code consisting of 4 hexadecimal characters (see http://www.autohotkey.com/docs/misc/Languages.htm). To make it work, fproxy should either accept these Windows locale codes or someone should build a mapping file that can map these codes to something else. - Zero3
Re: [freenet-dev] Detecting the language in the installer
Matthew Toseland wrote: Does autodetecting the language from the OS work in the wininstaller now? If not, what do we need to do to make it work? What kind of language codes will Windows return us? Autodetecting has always worked in the wininstaller, but the setting passed on to fproxy has been more or less guesswork. At the moment the localized name of the language will be passed on via freenet.ini. This is highly unsuitable and will only work in some lucky cases. Windows gives us a Windows locale code consisting of 4 hexadecimal characters (see http://www.autohotkey.com/docs/misc/Languages.htm). To make it work, fproxy should either accept these Windows locale codes or someone should build a mapping file that can map these codes to something else. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] [FYI] Sun Java SE 5.0 EOL today.
Ian Clarke wrote: > That being said, I think the key question is still: what do we gain by > dropping 1.5 compatibility? IMHO, for what it's worth: I'm not qualified to tell exactly what kind of new stuff 1.6 introduced, but I don't think we should fall behind upstream. If 1.5 is now end-of-life, we should already have moved to 1.6, which has been out since late 2006. I don't think supporting a minority of users with hopelessly outdated systems justifies holding back development. - Zero
Re: [freenet-dev] [FYI] Sun Java SE 5.0 EOL today.
Ian Clarke wrote: That being said, I think the key question is still: what do we gain by dropping 1.5 compatibility? IMHO, for what it's worth: I'm not qualified to tell exactly what kind of new stuff 1.6 introduced, but I don't think we should fall behind upstream. If 1.5 is now end-of-life, we should already have moved to 1.6, which has been out since late 2006. I don't think supporting a minority of users with hopelessly outdated systems justifies holding back development. - Zero ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Freenet Summer of Code wrap-up
Matthew Toseland wrote: > Apologies for being the absolute last wrap-up! This year went really well, we > had 5 students, and they all (more or less) deserved their passes. We had a > much stronger selection process than in the first 2 years, requiring some > demonstration in the form of code: a new feature or a bugfix. So even though > most of the students were completely new to us, mostly they did pretty well. > One of our students had a work conflict, but this was resolved satisfactorily. > > For the Googlers reading this, Freenet is an anonymous peer to peer system > with support for forums, browsing the internal web, filesharing etc, with a > focus on security and the option of running in "darknet" or friend-to-friend > mode. It is intended (at least by me) for people in hostile environments > (China, Iran etc) to express themselves freely, but it is currently mostly > used in the West by geeks, filesharers, etc. > > infinity0 and mikeb worked together on a new searching plugin, which we have > now deployed. infinity0's work was primarily on a new index format (which > works, but the spider needs more work), and on distributed indexing (which > doesn't yet), and mikeb mainly worked on improving the user interface and > adding essential features (simple non-infringing page ranking algorithm, > booleans, phrase matches etc). kurmi worked on new filtering code for various > formats, particularly a vastly improved CSS filter, which needed considerable > work to sort out all the parsing perversities but is now merged (Freenet has > to be very careful not to send anything to the browser that might give the > user's IP away via a web-bug). ljb worked on more friend-to-friend > functionality, his work is included in current builds. sashee worked on > making the web interface more dynamic, including solving a long-running > problem with image loading blocking the browser (freenet has quite high > latency!), using Google Web Toolkit; this branch has not yet been merged, but hopefully will be inside the next 6 months or so, it needs some tuning and debugging for slow browsers. > > Some of our students achieved less than expected IMHO but in more cases there > was a lot more work involved in the project than I expected, and the students > did really well. I have talked to most of them in the last month, well after > the programme was finished, and hopefully some of them will continue to > contribute at least occasionally. Best year yet, many thanks to Google! /me *claps* - Zero3
[freenet-dev] Update on getting rid of emu
bo-le wrote: > Am Samstag, 31. Oktober 2009 17:28:38 schrieb Zero3: >> Matthew Toseland wrote: >>> On Friday 30 October 2009 17:10:02 Zero3 wrote: >>>> Matthew Toseland wrote: >>>>> If this line of reasoning is correct, we need to choose an >>>>> end-user-oriented issue tracker or forums system (either way ideally >>>>> gratis and hosted) to complement Uservoice. Suggestions? >>>> It would make sense to find a tracker that both users and devs can use. >>>> Saves the overhead of moving things from e.g. a forums system to a bug >>>> tracker. >>> Is it possible? Is Trac something that end users can use? >> I don't think Trac is the perfect solution (not as it is right now, at >> least), but it seems much better than our current solution (Mantis + >> Wikka Wakka). >> >> Pidgin (see http://developer.pidgin.im/) has an interesting >> implementation directly into their website. The bar at the top contains >> easy access to some of the most used features: Wiki (starts here), >> Timeline (aka "what's new?"), Roadmap and Search. It is possible to >> create other things like "New ticket" and "Browse source" it seems, if >> you look at the official trac site (http://trac.edgewall.org/). >> >> I don't have any personal experience with Trac though. Perhaps someone >> else around here has, and can give us some recommendations? >> > this may fit our needs better then trac: http://basieproject.org/ A third option is Google Project Hosting (we are already using some Google-thingy for downloads I think?). Example here: http://code.google.com/p/support/issues/list The interface seems quite simple, and has both bug tracker and wiki. I'm quite fond of the "starring" of bugs. It's basically the possibility for users to mark the bugs they are specially interested in, which also gives the developers the possibility to focus on the most popular bugs. This might be able to supercede uservoice too (which is quite prone to spam as no user verification of votes are done). - Zero3
Re: [freenet-dev] Update on getting rid of emu
bo-le wrote: Am Samstag, 31. Oktober 2009 17:28:38 schrieb Zero3: Matthew Toseland wrote: On Friday 30 October 2009 17:10:02 Zero3 wrote: Matthew Toseland wrote: If this line of reasoning is correct, we need to choose an end-user-oriented issue tracker or forums system (either way ideally gratis and hosted) to complement Uservoice. Suggestions? It would make sense to find a tracker that both users and devs can use. Saves the overhead of moving things from e.g. a forums system to a bug tracker. Is it possible? Is Trac something that end users can use? I don't think Trac is the perfect solution (not as it is right now, at least), but it seems much better than our current solution (Mantis + Wikka Wakka). Pidgin (see http://developer.pidgin.im/) has an interesting implementation directly into their website. The bar at the top contains easy access to some of the most used features: Wiki (starts here), Timeline (aka what's new?), Roadmap and Search. It is possible to create other things like New ticket and Browse source it seems, if you look at the official trac site (http://trac.edgewall.org/). I don't have any personal experience with Trac though. Perhaps someone else around here has, and can give us some recommendations? this may fit our needs better then trac: http://basieproject.org/ A third option is Google Project Hosting (we are already using some Google-thingy for downloads I think?). Example here: http://code.google.com/p/support/issues/list The interface seems quite simple, and has both bug tracker and wiki. I'm quite fond of the starring of bugs. It's basically the possibility for users to mark the bugs they are specially interested in, which also gives the developers the possibility to focus on the most popular bugs. This might be able to supercede uservoice too (which is quite prone to spam as no user verification of votes are done). - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] Freenet Summer of Code wrap-up
Matthew Toseland wrote: Apologies for being the absolute last wrap-up! This year went really well, we had 5 students, and they all (more or less) deserved their passes. We had a much stronger selection process than in the first 2 years, requiring some demonstration in the form of code: a new feature or a bugfix. So even though most of the students were completely new to us, mostly they did pretty well. One of our students had a work conflict, but this was resolved satisfactorily. For the Googlers reading this, Freenet is an anonymous peer to peer system with support for forums, browsing the internal web, filesharing etc, with a focus on security and the option of running in darknet or friend-to-friend mode. It is intended (at least by me) for people in hostile environments (China, Iran etc) to express themselves freely, but it is currently mostly used in the West by geeks, filesharers, etc. infinity0 and mikeb worked together on a new searching plugin, which we have now deployed. infinity0's work was primarily on a new index format (which works, but the spider needs more work), and on distributed indexing (which doesn't yet), and mikeb mainly worked on improving the user interface and adding essential features (simple non-infringing page ranking algorithm, booleans, phrase matches etc). kurmi worked on new filtering code for various formats, particularly a vastly improved CSS filter, which needed considerable work to sort out all the parsing perversities but is now merged (Freenet has to be very careful not to send anything to the browser that might give the user's IP away via a web-bug). ljb worked on more friend-to-friend functionality, his work is included in current builds. sashee worked on making the web interface more dynamic, including solving a long-running problem with image loading blocking the browser (freenet has quite high latency!), using Google Web Toolkit; this branch has not yet been merged, but hopefully will be inside the next 6 months or so, it needs some tuning and debugging for slow browsers. Some of our students achieved less than expected IMHO but in more cases there was a lot more work involved in the project than I expected, and the students did really well. I have talked to most of them in the last month, well after the programme was finished, and hopefully some of them will continue to contribute at least occasionally. Best year yet, many thanks to Google! /me *claps* - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Update on getting rid of emu
Matthew Toseland wrote: > On Friday 30 October 2009 17:10:02 Zero3 wrote: >> Matthew Toseland wrote: >>> If this line of reasoning is correct, we need to choose an >>> end-user-oriented issue tracker or forums system (either way ideally gratis >>> and hosted) to complement Uservoice. Suggestions? >> It would make sense to find a tracker that both users and devs can use. >> Saves the overhead of moving things from e.g. a forums system to a bug >> tracker. > > Is it possible? Is Trac something that end users can use? I don't think Trac is the perfect solution (not as it is right now, at least), but it seems much better than our current solution (Mantis + Wikka Wakka). Pidgin (see http://developer.pidgin.im/) has an interesting implementation directly into their website. The bar at the top contains easy access to some of the most used features: Wiki (starts here), Timeline (aka "what's new?"), Roadmap and Search. It is possible to create other things like "New ticket" and "Browse source" it seems, if you look at the official trac site (http://trac.edgewall.org/). I don't have any personal experience with Trac though. Perhaps someone else around here has, and can give us some recommendations? - Zero3
Re: [freenet-dev] Update on getting rid of emu
Matthew Toseland wrote: On Friday 30 October 2009 17:10:02 Zero3 wrote: Matthew Toseland wrote: If this line of reasoning is correct, we need to choose an end-user-oriented issue tracker or forums system (either way ideally gratis and hosted) to complement Uservoice. Suggestions? It would make sense to find a tracker that both users and devs can use. Saves the overhead of moving things from e.g. a forums system to a bug tracker. Is it possible? Is Trac something that end users can use? I don't think Trac is the perfect solution (not as it is right now, at least), but it seems much better than our current solution (Mantis + Wikka Wakka). Pidgin (see http://developer.pidgin.im/) has an interesting implementation directly into their website. The bar at the top contains easy access to some of the most used features: Wiki (starts here), Timeline (aka what's new?), Roadmap and Search. It is possible to create other things like New ticket and Browse source it seems, if you look at the official trac site (http://trac.edgewall.org/). I don't have any personal experience with Trac though. Perhaps someone else around here has, and can give us some recommendations? - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Update on getting rid of emu
Matthew Toseland wrote: > We need to migrate the Wikka wiki to MediaWiki, because the latter is > standard and we will be able to host it externally. E.g. sourceforge Hosted > Apps allows for data import for MediaWiki. The wiki isn't really kept enough up-to-date, is it? I personally think the idea of something more integrated (like Trac) would be awesome. MediaWiki seems a bit over-do for Freenet? > BUG TRACKER: > - Dev intelligence i.e. stuff people have said. If these are corroborated > quickly they should be acted upon, else they should be closed. Something integrated (same user account, for starters) might help motivating people to put this stuff in the wiki as well. > If we keep the bug tracker: > - We need to find somewhere to host MANTIS. Probably we will have to pay for > this. > - We need to keep it up to date ourselves, which is somewhat involved. It may > not be as bad as nextgens implies though. > - Minimum immediate work. I personally think Mantis is *very* bad usability-wise. Trac, Launchpad, and many other bug trackers are much easier to use. If we even have to pay just to keep that thing running, I'd say find something else. > If we don't keep the bug tracker: > - We can use any hosted bug tracker anywhere. E.g. Sourceforge Hosted Apps > includes both Mantis and Trac. We will likely be able to avoid any fixed > monthly payments. > - We can use any bug tracker: Mantis, Trac, etc. See below. > - We will need to do a "spring clean": Keep the current bug tracker up for a > while but read-only, *manually* migrate any important bugs and issues to the > new tracker. > - This will be significant work. > - It will involve going over the bugs, dumping those which are out of date, > abandoned etc, and rewriting those bugs and feature issues that are still > valid. Trac's wiki functionality may be useful for this, although it loses > the ability to link bugs formally. > - It may be a useful exercise in terms of prioritising and de-junking. > > However, we have 20 weeks left of funding, so we have to ask whether spending > a week de-junking is worth it? If it comes down to costing us ?40-?80 per month... It quickly runs up. I'm up for giving a hand and doing 5 'a day of the de-junking and moving. I'm sure there are more people around willing to give a hand. > An important related point: Relatively few end-users use the current bug > tracker. It is on the Contribute menu on the website, but the main reason > IMHO is it is not very newbie friendly. Uservoice is a reasonable solution > for end-user feature suggestions and gauging public opinion, but because it > does not force users to register their email addresses, it is worthless for > solving individual reproducible bugs. It might reasonably be argued that we > should have a separate issue tracker or forums system for end-user bug > reports. Also, it may make sense for the developer-oriented bug tracker to be > open source, whereas it matters less for the end-user tracker, because 1) > end-users care less, and 2) long term stuff with detailed implementation > notes is likely to be on the developer-oriented bug tracker. Again, let's find something more user-friendly than Mantis :/ > > If this line of reasoning is correct, we need to choose an end-user-oriented > issue tracker or forums system (either way ideally gratis and hosted) to > complement Uservoice. Suggestions? It would make sense to find a tracker that both users and devs can use. Saves the overhead of moving things from e.g. a forums system to a bug tracker. - Zero3
[freenet-dev] Depency on emu
Speaking of servers, how is our depency on emu looking? There was some discussion a while ago to move things off emu to save the monthly expense? - Zero3 Matthew Toseland wrote: > On Tuesday 20 October 2009 04:46:10 Ian Clarke wrote: >> I reported this bug a few days ago: >> >> https://bugs.freenetproject.org/view.php?id=3604 >> >> Read it for the details, but basically I'm seeing an intermittent >> problem where Webstart can't download the installer. Is anyone else >> seeing it? > > Reproduced the bug, fixed it by pointing the JWS installer to Google Code. > Which means that we now only use the mirror network for update.sh / > update.cmd. The freenet.jnlp itself is served from emu directly, so the JNLP > still says it's downloading from checksums.freenetproject.org. > > > > > ___ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Depency on emu
Speaking of servers, how is our depency on emu looking? There was some discussion a while ago to move things off emu to save the monthly expense? - Zero3 Matthew Toseland wrote: On Tuesday 20 October 2009 04:46:10 Ian Clarke wrote: I reported this bug a few days ago: https://bugs.freenetproject.org/view.php?id=3604 Read it for the details, but basically I'm seeing an intermittent problem where Webstart can't download the installer. Is anyone else seeing it? Reproduced the bug, fixed it by pointing the JWS installer to Google Code. Which means that we now only use the mirror network for update.sh / update.cmd. The freenet.jnlp itself is served from emu directly, so the JNLP still says it's downloading from checksums.freenetproject.org. ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Improving text on wizard was Re: test install on Windows 7
On Sat, 24 Oct 2009 20:19:34 +0100, Matthew Toseland wrote: >> > If we are browsing in incognito mode, we have a shorter warning: >> >> IMHO: Don't bother the user when he is doing the right thing. He is safe, >> so let him in without questions. 1 click saved. > > Problem is it is hard to impossible to reliably detect when he is doing the > *wrong* thing. Until we have a custom browser with non-localhost url's, we > need the user to be aware of the issue? If the incognito flag is passed, I think we can safely assume that we are actually in incognito mode and not show any message. With the exception of the current Chrome bug of course. When Chrome is fixed and FF 1.6 is out, we can cover quite some ground. We still have the separate IE warning, don't we? - Zero3
Re: [freenet-dev] Improving text on wizard was Re: test install on Windows 7
On Sat, 24 Oct 2009 20:19:34 +0100, Matthew Toseland t...@amphibian.dyndns.org wrote: If we are browsing in incognito mode, we have a shorter warning: IMHO: Don't bother the user when he is doing the right thing. He is safe, so let him in without questions. 1 click saved. Problem is it is hard to impossible to reliably detect when he is doing the *wrong* thing. Until we have a custom browser with non-localhost url's, we need the user to be aware of the issue? If the incognito flag is passed, I think we can safely assume that we are actually in incognito mode and not show any message. With the exception of the current Chrome bug of course. When Chrome is fixed and FF 1.6 is out, we can cover quite some ground. We still have the separate IE warning, don't we? - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] test install on Windows 7
On Fri, 23 Oct 2009 18:25:17 -0500, Ian Clarke wrote: > On Fri, Oct 23, 2009 at 5:10 PM, zero3 wrote: >> But. Was that with the current version (the one from the website) or with >> the beta? I'm very surprised if the current version works on Win7 :o. >> Can't >> complain though... > > It was with the one currently on the website, and it appeared to work > exactly as intended so far as I can tell. :o. I can't complain though :) - Zero3
[freenet-dev] New wininstaller
On Sat, 24 Oct 2009 00:56:49 +0100, Matthew Toseland wrote: > On Friday 23 October 2009 23:54:36 Matthew Toseland wrote: >> On Friday 23 October 2009 23:27:34 zero3 wrote: >> > >> > Awesomeness! >> > >> > Did the merge succeed without issues? Any problematic conflicts? >> >> Several files had issues, I sided with the beta branch. >> > >> > The reason for the "Browse Freenet" to "Launch Freenet" rename in the >> > first >> > place, was that Freenet is starting to do much other stuff than >> > "browsing >> > [websites]". Mail, forums, IM, file sharing. "Browse" sounds a bit >> > misleading as a common verb for that. Maybe something completely >> > different? >> >> Open Freenet? >> > >> > I'm responsible for turning the incognito flag back on. I really think >> > the >> > block should be placed in Freenet (by simply checking the user-agent), >> > as >> > the block can then easily be removed on a new build when Google have >> > fixed >> > Chrome. If it's placed in the launcher, we can't push the update to >> > enable >> > it again later on, as we depend on people updating their helper >> > executables >> > themselves. Which they probably won't (it's possible via the new tray >> > manager though). >> >> Hmmm, okay. It is disabled in fproxy at the moment, so I will reinstate >> the change you made, but I will add comments on both sides. >> > Done. Any thoughts on Launch Freenet vs Open Freenet? We do tell the user > that it will run in the background anyway, so maybe launch is okay? Roger that. Either works for me. I don't really have an opinion on which is best. The Danish translation for either of them would be the same, actually. - Zero3
[freenet-dev] Improving text on wizard was Re: test install on Windows 7
On Fri, 23 Oct 2009 23:51:56 +0100, Matthew Toseland wrote: > WELCOME SCREEN: IMHO: Remove it. If needed, add a "Configure manually" button in the corner of the rest of the wizard pages. 1 click saved. > If we are browsing in incognito mode, we have a shorter warning: IMHO: Don't bother the user when he is doing the right thing. He is safe, so let him in without questions. 1 click saved. > Unfortunately starting Chrome with the incognito flag does not reliably > ensure the window is opened in incognito mode - if Chrome is already > running, it will open it in a non-incognito window/tab. So at the moment > this is turned off. So afaics we are waiting for Google to fix it? Firefox > is likely to have similar issues based on my experience with profiles, > although it may be possible to work around that with -no-remote. Does FF3.5 > have an equivalent of incognito mode? We are indeed waiting for Google to fix it. I'm keeping an eye on their bug tracker. Regarding FF, we are awaiting a command line option to use private browsing which will be implemented in 3.6 (https://developer.mozilla.org/en/Command_Line_Options#-private). > AUTO UPDATE AND PLUGINS IMHO: Default to autoupdate without asking (on Windows and Mac - should be off on Linux when installed from a package). Nodes will quickly be locked out of the network if they don't update, rendering their nodes useless. 1 click saved. > WELCOME: IMHO: Remove this page and show it as some kind of status message on the fproxy main page. 1 click saved. - Zero3
Re: [freenet-dev] Improving text on wizard was Re: test install on Windows 7
On Fri, 23 Oct 2009 23:51:56 +0100, Matthew Toseland t...@amphibian.dyndns.org wrote: WELCOME SCREEN: IMHO: Remove it. If needed, add a Configure manually button in the corner of the rest of the wizard pages. 1 click saved. If we are browsing in incognito mode, we have a shorter warning: IMHO: Don't bother the user when he is doing the right thing. He is safe, so let him in without questions. 1 click saved. Unfortunately starting Chrome with the incognito flag does not reliably ensure the window is opened in incognito mode - if Chrome is already running, it will open it in a non-incognito window/tab. So at the moment this is turned off. So afaics we are waiting for Google to fix it? Firefox is likely to have similar issues based on my experience with profiles, although it may be possible to work around that with -no-remote. Does FF3.5 have an equivalent of incognito mode? We are indeed waiting for Google to fix it. I'm keeping an eye on their bug tracker. Regarding FF, we are awaiting a command line option to use private browsing which will be implemented in 3.6 (https://developer.mozilla.org/en/Command_Line_Options#-private). AUTO UPDATE AND PLUGINS IMHO: Default to autoupdate without asking (on Windows and Mac - should be off on Linux when installed from a package). Nodes will quickly be locked out of the network if they don't update, rendering their nodes useless. 1 click saved. WELCOME: IMHO: Remove this page and show it as some kind of status message on the fproxy main page. 1 click saved. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] New wininstaller
On Sat, 24 Oct 2009 00:56:49 +0100, Matthew Toseland t...@amphibian.dyndns.org wrote: On Friday 23 October 2009 23:54:36 Matthew Toseland wrote: On Friday 23 October 2009 23:27:34 zero3 wrote: Awesomeness! Did the merge succeed without issues? Any problematic conflicts? Several files had issues, I sided with the beta branch. The reason for the Browse Freenet to Launch Freenet rename in the first place, was that Freenet is starting to do much other stuff than browsing [websites]. Mail, forums, IM, file sharing. Browse sounds a bit misleading as a common verb for that. Maybe something completely different? Open Freenet? I'm responsible for turning the incognito flag back on. I really think the block should be placed in Freenet (by simply checking the user-agent), as the block can then easily be removed on a new build when Google have fixed Chrome. If it's placed in the launcher, we can't push the update to enable it again later on, as we depend on people updating their helper executables themselves. Which they probably won't (it's possible via the new tray manager though). Hmmm, okay. It is disabled in fproxy at the moment, so I will reinstate the change you made, but I will add comments on both sides. Done. Any thoughts on Launch Freenet vs Open Freenet? We do tell the user that it will run in the background anyway, so maybe launch is okay? Roger that. Either works for me. I don't really have an opinion on which is best. The Danish translation for either of them would be the same, actually. - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] test install on Windows 7
On Fri, 23 Oct 2009 18:25:17 -0500, Ian Clarke i...@locut.us wrote: On Fri, Oct 23, 2009 at 5:10 PM, zero3 ze...@zerosplayground.dk wrote: But. Was that with the current version (the one from the website) or with the beta? I'm very surprised if the current version works on Win7 :o. Can't complain though... It was with the one currently on the website, and it appeared to work exactly as intended so far as I can tell. :o. I can't complain though :) - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] New wininstaller
Awesomeness! Did the merge succeed without issues? Any problematic conflicts? The reason for the "Browse Freenet" to "Launch Freenet" rename in the first place, was that Freenet is starting to do much other stuff than "browsing [websites]". Mail, forums, IM, file sharing. "Browse" sounds a bit misleading as a common verb for that. Maybe something completely different? I'm responsible for turning the incognito flag back on. I really think the block should be placed in Freenet (by simply checking the user-agent), as the block can then easily be removed on a new build when Google have fixed Chrome. If it's placed in the launcher, we can't push the update to enable it again later on, as we depend on people updating their helper executables themselves. Which they probably won't (it's possible via the new tray manager though). - Zero3 On Fri, 23 Oct 2009 20:56:23 +0100, Matthew Toseland wrote: > I have merged the beta branch of the wininstaller, in accordance with > instructions from Juiceman and Zero3. The main changes in this branch are > that it doesn't create a custom user to run Freenet in (which caused many > problems for many users installing it due to password policies, anti-virus > software, and things we don't understand), and that it has a system tray > icon, from where the user can conveniently (provided his system tray isn't > hopelessly cluttered already) start or stop or browse Freenet. > > In testing, it works, and so does Freenet. However there are a number of > issues we need to deal with: > - "Launch Freenet after installation" - Freenet will run anyway, launching > it means browsing it, maybe we should change "Launch Freenet" here and in > the system tray menu to "Browse Freenet"? > - TUFI menus don't show up well in Chrome. Chrome is our default browser on > Windows because it has incognito mode, which we use. The author of TUFI > should fix the stylesheet so that the drop-down menus are usable on Chrome, > please! (Can somebody please forward this request via the FMS board > please?) > - Chrome sometimes seems to lose the web interface CSS, showing either a > blank screen or a non-styled copy of the loading a page or dangerous > content page. There were no errors in the log concerning fproxy. Reload and > even shift+reload make no difference, but restarting Chrome fixes this. > Initially I had thought it might be related to it using lots of connections > as I was loading many sites with many images, but that didn't seem to make > any difference. Thoughts? > - We have a flag to tell Freenet that we are running Chrome in incognito > mode, which will show a much shorter and less worrying browsers warning at > the beginning of the wizard. However, bugs in Chrome mean that just because > we tell Chrome to open Freenet in incognito mode doesn't mean it actually > will. I had turned off this flag, Juiceman turned it back on, for now I > have turned it back off, because it is a security issue. Thoughts? > > The next build will be released with the new installer in any case.
[freenet-dev] test install on Windows 7
Wee! But. Was that with the current version (the one from the website) or with the beta? I'm very surprised if the current version works on Win7 :o. Can't complain though... - Zero3 On Fri, 23 Oct 2009 11:30:33 -0500, Ian Clarke wrote: > I just did a fresh install of Freenet on a newly-minted Windows 7 box, > and I'm pleased to say that it went very smoothly! > > The installer downloaded and installed Java, and while (of course) I'm > no newbie, I didn't really encounter any usability problems, except > perhaps all the reading a user is expected to do when you choose > security settings. > > I think with those options we should try reducing it to a single > sentence for each, with a "read more..." link which opens up a more > detailed explanation. > > Ian.
Re: [freenet-dev] New wininstaller
Awesomeness! Did the merge succeed without issues? Any problematic conflicts? The reason for the Browse Freenet to Launch Freenet rename in the first place, was that Freenet is starting to do much other stuff than browsing [websites]. Mail, forums, IM, file sharing. Browse sounds a bit misleading as a common verb for that. Maybe something completely different? I'm responsible for turning the incognito flag back on. I really think the block should be placed in Freenet (by simply checking the user-agent), as the block can then easily be removed on a new build when Google have fixed Chrome. If it's placed in the launcher, we can't push the update to enable it again later on, as we depend on people updating their helper executables themselves. Which they probably won't (it's possible via the new tray manager though). - Zero3 On Fri, 23 Oct 2009 20:56:23 +0100, Matthew Toseland t...@amphibian.dyndns.org wrote: I have merged the beta branch of the wininstaller, in accordance with instructions from Juiceman and Zero3. The main changes in this branch are that it doesn't create a custom user to run Freenet in (which caused many problems for many users installing it due to password policies, anti-virus software, and things we don't understand), and that it has a system tray icon, from where the user can conveniently (provided his system tray isn't hopelessly cluttered already) start or stop or browse Freenet. In testing, it works, and so does Freenet. However there are a number of issues we need to deal with: - Launch Freenet after installation - Freenet will run anyway, launching it means browsing it, maybe we should change Launch Freenet here and in the system tray menu to Browse Freenet? - TUFI menus don't show up well in Chrome. Chrome is our default browser on Windows because it has incognito mode, which we use. The author of TUFI should fix the stylesheet so that the drop-down menus are usable on Chrome, please! (Can somebody please forward this request via the FMS board please?) - Chrome sometimes seems to lose the web interface CSS, showing either a blank screen or a non-styled copy of the loading a page or dangerous content page. There were no errors in the log concerning fproxy. Reload and even shift+reload make no difference, but restarting Chrome fixes this. Initially I had thought it might be related to it using lots of connections as I was loading many sites with many images, but that didn't seem to make any difference. Thoughts? - We have a flag to tell Freenet that we are running Chrome in incognito mode, which will show a much shorter and less worrying browsers warning at the beginning of the wizard. However, bugs in Chrome mean that just because we tell Chrome to open Freenet in incognito mode doesn't mean it actually will. I had turned off this flag, Juiceman turned it back on, for now I have turned it back off, because it is a security issue. Thoughts? The next build will be released with the new installer in any case. ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] [wininstaller beta] update.cmd wininstaller beta compatibility
Juiceman wrote: > Commit > http://github.com/freenet/wininstaller-staging/commit/2fe991d7c58f3fe2c23b222ee678ea5312c87072 > should have fixed update.cmd compatibility, please deploy it to the > website. > [snip] > Once the freenettray.exe is on the website I can wire it in to at > least update installs going forward. No need to wait on that. Deploy > away. > > Upgrading old installs can come later. > Cool! toad you should look into deploying the beta then. I have no idea how to handle this in git though. Perhaps it is possible to rename the "master" branch to "deprecated_v1" and the "beta" branch to "master"? Or would it be better to simply merge the branches and tag the merge with "generation_2" or something? - Zero3
Re: [freenet-dev] [wininstaller beta] update.cmd wininstaller beta compatibility
Juiceman wrote: Commit http://github.com/freenet/wininstaller-staging/commit/2fe991d7c58f3fe2c23b222ee678ea5312c87072 should have fixed update.cmd compatibility, please deploy it to the website. [snip] Once the freenettray.exe is on the website I can wire it in to at least update installs going forward. No need to wait on that. Deploy away. Upgrading old installs can come later. Cool! toad you should look into deploying the beta then. I have no idea how to handle this in git though. Perhaps it is possible to rename the master branch to deprecated_v1 and the beta branch to master? Or would it be better to simply merge the branches and tag the merge with generation_2 or something? - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] [wininstaller beta] update.cmd wininstaller beta compatibility
Matthew Toseland wrote: > On Thursday 08 October 2009 17:30:45 Zero3 wrote: >> Juiceman wrote: >>> As far as I know, the tray manager is not hosted on the Freenet >>> website anywhere and therefore cannot be updated. >> toad, can you upload a dummy of this, until the beta has been deployed? > > Done. Sorry for the delay. It would be really great to get the new installer > deployed, it is IMHO vital for 0.8. As I understand it the big problem is > that there is no working update script for the new installer? The beta branch is basically ready to be merged into master and deployed. This will also finally resolve the last long-standing wininstaller bugs from back when we used the Java installer (the custom user related ones). Only remaining issue is indeed update.cmd, but Juiceman hasn't replied on whether development for the beta branch is finished. It seemed to work in my tests though. Of the reported wininstaller failures, the beta seems to solve most of them. A few have reported failure even with the beta. I only managed to get a hold of one of these reporters, and his problem was revealed to be a broken Windows registry database. This new install design (using a standard service user account instead of a custom one) raised a new issue regarding how to update old installs. It was more or less agreed that it would be a better idea to start from scratch on a real updater than hacking UAC-functionality into update.cmd. Juiceman has looked at this, but not made any real progress. I'm insanely overbooked at the moment, so I'm afraid I cannot do this myself right now. This means that we will be leaving the current users behind, most importantly leaving them without the upcoming tray manager (which IMHO is an important aspect both short- and long-term). - Zero3
Re: [freenet-dev] [wininstaller beta] update.cmd wininstaller beta compatibility
Matthew Toseland wrote: On Thursday 08 October 2009 17:30:45 Zero3 wrote: Juiceman wrote: As far as I know, the tray manager is not hosted on the Freenet website anywhere and therefore cannot be updated. toad, can you upload a dummy of this, until the beta has been deployed? Done. Sorry for the delay. It would be really great to get the new installer deployed, it is IMHO vital for 0.8. As I understand it the big problem is that there is no working update script for the new installer? The beta branch is basically ready to be merged into master and deployed. This will also finally resolve the last long-standing wininstaller bugs from back when we used the Java installer (the custom user related ones). Only remaining issue is indeed update.cmd, but Juiceman hasn't replied on whether development for the beta branch is finished. It seemed to work in my tests though. Of the reported wininstaller failures, the beta seems to solve most of them. A few have reported failure even with the beta. I only managed to get a hold of one of these reporters, and his problem was revealed to be a broken Windows registry database. This new install design (using a standard service user account instead of a custom one) raised a new issue regarding how to update old installs. It was more or less agreed that it would be a better idea to start from scratch on a real updater than hacking UAC-functionality into update.cmd. Juiceman has looked at this, but not made any real progress. I'm insanely overbooked at the moment, so I'm afraid I cannot do this myself right now. This means that we will be leaving the current users behind, most importantly leaving them without the upcoming tray manager (which IMHO is an important aspect both short- and long-term). - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] [wininstaller beta] update.cmd wininstaller beta compatibility
Juiceman wrote: > On Fri, Oct 2, 2009 at 7:31 PM, Zero3 wrote: >> Hey >> >> What is the status for wininstaller beta compatibility in update.cmd >> Juiceman? > > I'm sorry, I've not progressed very far on the AHK replacement, I got > distracted. I don't know when I will be able to work on it again. I > will commit the file I started in case someone else wants to get to > it. No worries. I didn't mean the new updater though, but rather if the current update.cmd completely supports the beta branch (tray manager etc.)? >> I've noticed the following bugs while testing today: >> >> 1) Seems like it tries to set file permissions on installs without the >> custom user: >> >> "- Checking file permissions >> - Changing file permissions >> freenet: Der blev ikke udf?rt nogen afbildning mellem kontonavne og >> sikkerheds-id." >> >> A work-around until we have a real updater would be to not do so if >> bin\freenettray.exe exists. > > I will commit this asap. Cheers :) >> 2) The tray manager is not being updated. (I agree that we shouldn't >> install it on old installs for now, but if it already exists, it should >> be updated as all the other executables) >> >> - Zero3 > > As far as I know, the tray manager is not hosted on the Freenet > website anywhere and therefore cannot be updated. toad, can you upload a dummy of this, until the beta has been deployed? - Zero
Re: [freenet-dev] [wininstaller beta] update.cmd wininstaller beta compatibility
Juiceman wrote: On Fri, Oct 2, 2009 at 7:31 PM, Zero3 ze...@zerosplayground.dk wrote: Hey What is the status for wininstaller beta compatibility in update.cmd Juiceman? I'm sorry, I've not progressed very far on the AHK replacement, I got distracted. I don't know when I will be able to work on it again. I will commit the file I started in case someone else wants to get to it. No worries. I didn't mean the new updater though, but rather if the current update.cmd completely supports the beta branch (tray manager etc.)? I've noticed the following bugs while testing today: 1) Seems like it tries to set file permissions on installs without the custom user: - Checking file permissions - Changing file permissions freenet: Der blev ikke udført nogen afbildning mellem kontonavne og sikkerheds-id. A work-around until we have a real updater would be to not do so if bin\freenettray.exe exists. I will commit this asap. Cheers :) 2) The tray manager is not being updated. (I agree that we shouldn't install it on old installs for now, but if it already exists, it should be updated as all the other executables) - Zero3 As far as I know, the tray manager is not hosted on the Freenet website anywhere and therefore cannot be updated. toad, can you upload a dummy of this, until the beta has been deployed? - Zero ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] Win64 support options?
xor wrote: > On Friday 21 August 2009 22:31:03 Matthew Toseland wrote: >> How common is 64-bit Vista? Currently we install a 32-bit JVM, which works, >> but doesn't get auto-updated, and is somewhat slower than if we'd installed >> a 64-bit one (assuming we fix the FEC libraries and manage to build them >> for Windows). We can't install a 64-bit JVM, because the free version of >> the Java Service Wrapper (which we use for self-restarting the node when >> deploying updates, and for detecting hangs) only supports 32-bit. >> >> Options? > > Vista64 is very common already and Win7 x64 will be even more widespread. 64 > bit CPUs have been there for ages and we should support them. > > Regarding the 64bit JVM I have to state that we should keep shipping the > 32bit > one - it still seems to be intended by Sun that 32bit java is used on 64bit > windows: > > - The 64bit JVM does not install a Firefox plugin, or at least it does not > work (maybe because Firefox is still 32bit?) > > - The auto updater of the 64 bit JVM installs a 32 bit JVM so then you have > 2. > This is obviously a bug but it shows that Sun does not properly maintain the > 64bit windows JVM yet. I'm a bit out of the loop on this issue. Did we figure out if we should keep installing 32-bit java on 64-bit Windows? If so, any idea of when it will change? - Zero3
[freenet-dev] [freenet-support] WinXP installer fails, service won't start
Hi I'm the maintainer of the Windows Installer. Sorry for the long delay of this reply - I've been extremely busy lately. If you can, please send us the wrapper.log logfile. You can find it via the tray icon in the beta release. It might contain useful information. Where do you get the "2" error code? From the Windows service manager? Is there anything special about your system? Group policies? Special version of Windows? Non-standard antivirus software? You should be able to run the service in a command promt by simply copying the command line from the Windows service manager, eventually removing the "-s" switch. - Zero3 Magnus Ekhall wrote: > Matthew Toseland skrev: >> On Tuesday 25 August 2009 18:34:34 Magnus Ekhall wrote: >>> I tried to install using the 1232 version of the XP installer. >>> >>> At the end of the installation it says that it failed becaus the service >>> could not be started. >>> >>> If I try to start the service manually it will eventually fail as well >>> with the error code "2". >>> >>> Any ideas? >> Try the beta installer: >> http://privat.zero3.dk/FreenetInstaller_Beta.exe >> >> This will install an old version of Freenet, with no update.cmd. But it >> should auto-update to the latest version in an hour or so. >> >> Uninstall your current Freenet first, but don't uninstall the Java version >> it installed. >> >> PS Zero3: Shall I compile up a more recent beta/ version? > > > I tried the beta installer, but it too could not start the freenet service. > > "Service did not respond to signal" it says. > > I'm runnung the installer as admin and I have a recent java. > > Can I run the service in a shell or something to get a bit better error > messages? > >
[freenet-dev] [wininstaller beta] Testing on Windows + Uninstall survey
Matthew Toseland wrote:
> On Monday 24 August 2009 17:03:21 Zero3 wrote:
>> Matthew Toseland skrev:
>>> On Friday 21 August 2009 20:12:39 Zero3 wrote:
>>>> Matthew Toseland skrev:
>>>>> Here's another one:
>>>>>
>>>>> I accidentally built the installer with the beta branch. The tray icon
>>>>> worked, but when I uninstalled, and told it to do the survey, the survey
>>>>> failed (as usual), but control panel hung. Ideas? I think it might be
>>>>> waiting for firefox to close, but this is very bad behaviour, as there
>>>>> may be other stuff in firefox?
>>>>>
>>>>> I don't think this is specific to the beta branch - we wait for firefox
>>>>> (or whatever browser) to close before closing control panel.
>>>> Nop, it will not wait for the browser to close. It will exit right after
>>>> launching:
>>>>
>>>> [CODE]
>>>> If (_DoSurvey)
>>>> {
>>>>Run, http://freenetproject.org/uninstall.html, , UseErrorLevel
>>>> }
>>>>
>>>> Exit()
>>>> [/CODE]
>>>>
>>>> (The execute-and-wait-for-it-to-finish command is called "RunWait" as
>>>> opposed to the "Run" used here which will continue right away)
>>>>
>>>> Are you sure that freenetuninstaller.exe is running while the control
>>>> panel hangs?
>>> I don't know. I do know that control panel hangs until the browser exists.
>> Odd. Maybe it also considers processes spawned by the uninstaller as
>> part of the uninstaller itself, and does not return control to the
>> control panel until all of these have terminated. Would make sense, as
>> uninstallers often continue in other processes than the originally
>> executed one (the wininstaller uninstaller included).
>>
>> Nevertheless, this is a design choice by Microsoft. If they want to
>> freeze out the user while any part of an uninstaller is running, I
>> shouldn't try to (and probably can't) get around it.
>
> There must be a way to detach it.
There might be. No idea how much hacking it would take though. IMHO I
don't think the minor usability issue is worth the hack.
On Vista I am able to close the control panel, although not start a new
uninstall before the browser is closed.
>> A possible workaround could be to add a message to the survey completion
>> page simply asking the user to close the window.
>
> Unfortunately it's broken atm.
Any update on this? Please at least remove the survey from
http://freenetproject.org/uninstall.html and replace it with a
"Temporary out of order" message or something. We are seriously wasting
people's time right now.
- Zero3
[freenet-dev] [wininstaller beta] Release candidate
Hi all Time for a proper release candidate of the wininstaller beta branch. As always, all kinds of constructive feedback is welcome. Source: http://github.com/freenet/wininstaller-staging/tree/beta Binary: http://privat.zero3.dk/FreenetInstaller_Beta.exe Most interesting changes in the release candidate are: * Made launcher silently fail if start.exe failed (instead of trying to launch anyway when service clearly isn't running). * Updated Java online installer to version 1.6u16. * Bumped required Java version to 1.6. 1.5 is going end-of-life very soon. * Added Spanish translation. * Updated Danish translation. * Added update.cmd (still not perfect, see separate mail) * Added a wrapper.restart.delay to wrapper.conf as the wrapper default might be 0 seconds according to some reports. The delay might be needed in rare cases. * Delay execution of the tray manager until the user has clicked through the "Install done" infobox. (Usability reasons) * Rework of disk space calculation and display. Unless anything serious shows up, this should be ready to replace the master branch :). - Zero3
[freenet-dev] [wininstaller beta] Work on implementing the Russian translation
Hi again Sorry for the long delay. I've looked at your translation today, but it seems like the installer might not support Cyrillic characters as it is right now. They show as "" on my system at least. Did you test the translation yourself by compiling the installer with your translation? Did it work? I've filed a bug for it at https://bugs.freenetproject.org/view.php?id=3563 if you want to follow the progress on this. I've got some things to try out when I have the time. - Zero3 StandAlone-Alien wrote: > Russian translation > > > > > ___ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] [wininstaller beta] update.cmd wininstaller beta compatibility
Hey What is the status for wininstaller beta compatibility in update.cmd Juiceman? I've noticed the following bugs while testing today: 1) Seems like it tries to set file permissions on installs without the custom user: "- Checking file permissions - Changing file permissions freenet: Der blev ikke udf?rt nogen afbildning mellem kontonavne og sikkerheds-id." A work-around until we have a real updater would be to not do so if bin\freenettray.exe exists. 2) The tray manager is not being updated. (I agree that we shouldn't install it on old installs for now, but if it already exists, it should be updated as all the other executables) - Zero3
[freenet-dev] [wininstaller beta] Work on implementing the Russian translation
Hi again Sorry for the long delay. I've looked at your translation today, but it seems like the installer might not support Cyrillic characters as it is right now. They show as on my system at least. Did you test the translation yourself by compiling the installer with your translation? Did it work? I've filed a bug for it at https://bugs.freenetproject.org/view.php?id=3563 if you want to follow the progress on this. I've got some things to try out when I have the time. - Zero3 Валентин StandAlone-Alien wrote: Russian translation ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
[freenet-dev] [wininstaller beta] Release candidate
Hi all Time for a proper release candidate of the wininstaller beta branch. As always, all kinds of constructive feedback is welcome. Source: http://github.com/freenet/wininstaller-staging/tree/beta Binary: http://privat.zero3.dk/FreenetInstaller_Beta.exe Most interesting changes in the release candidate are: * Made launcher silently fail if start.exe failed (instead of trying to launch anyway when service clearly isn't running). * Updated Java online installer to version 1.6u16. * Bumped required Java version to 1.6. 1.5 is going end-of-life very soon. * Added Spanish translation. * Updated Danish translation. * Added update.cmd (still not perfect, see separate mail) * Added a wrapper.restart.delay to wrapper.conf as the wrapper default might be 0 seconds according to some reports. The delay might be needed in rare cases. * Delay execution of the tray manager until the user has clicked through the Install done infobox. (Usability reasons) * Rework of disk space calculation and display. Unless anything serious shows up, this should be ready to replace the master branch :). - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] [freenet-support] WinXP installer fails, service won't start
Hi I'm the maintainer of the Windows Installer. Sorry for the long delay of this reply - I've been extremely busy lately. If you can, please send us the wrapper.log logfile. You can find it via the tray icon in the beta release. It might contain useful information. Where do you get the 2 error code? From the Windows service manager? Is there anything special about your system? Group policies? Special version of Windows? Non-standard antivirus software? You should be able to run the service in a command promt by simply copying the command line from the Windows service manager, eventually removing the -s switch. - Zero3 Magnus Ekhall wrote: Matthew Toseland skrev: On Tuesday 25 August 2009 18:34:34 Magnus Ekhall wrote: I tried to install using the 1232 version of the XP installer. At the end of the installation it says that it failed becaus the service could not be started. If I try to start the service manually it will eventually fail as well with the error code 2. Any ideas? Try the beta installer: http://privat.zero3.dk/FreenetInstaller_Beta.exe This will install an old version of Freenet, with no update.cmd. But it should auto-update to the latest version in an hour or so. Uninstall your current Freenet first, but don't uninstall the Java version it installed. PS Zero3: Shall I compile up a more recent beta/ version? I tried the beta installer, but it too could not start the freenet service. Service did not respond to signal it says. I'm runnung the installer as admin and I have a recent java. Can I run the service in a shell or something to get a bit better error messages? ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
