Re: [freenet-support] Usability improvement ideas
There _has_ to be a question when installing asking the user if he/she pays for bandwidth (esp outgoing) and set the configuration in Freenet accordingly - bad press resulting from Joe Doe installing Freenet and getting $1000 bills (think NZ, OZ) isn't good. Hmm. Good idea. However, I'm not sure that you CAN run a freenet ndoe with any reasonable performance if it's limited to 3GB/mo as is common in oz. Technically, the solution is the average bandwidth limiter. However this is not known to work well (it is pretty much untested since NIO), mostly because no developers have that sort of connection. Perhaps we should put some effort in, but I'm not sure that it's proportionate as users with such connections won't get much out of or contribute much to Freenet. Yes, it might be useful for the occasional content author, so it IS worth thinking about; it's just that they'll be put off by the dire performance implied. But I'm not a developer and I do need to keep a leash on the bandwidth my node produces. I've set it to 24576 in/24576 out so hopefully overall I won't be leaching more than 48KiB/sec. I share a network with a friend who pays the bill (has a 50G/month limit) and I'd like to have a present, but, limited network bandwidth profile. He was really leary of letting me run a freenet node and he's all but banned kazaa and other related progs from being used by his roommates. Better portals. People _don't_ want links to child pornography (no, I don't want a discussion, flamefest etc, I'm talking the general public who want to USE Freenet) to be the first thing they see. Instead the top portal should contain links like the Diebold one, the Scientology Bible etc. Advertise the fact that Freedom of Speach is the central issue. This doesn't sound like such a bad idea. I'm sure persons delivering the really disgusting content have other channels for disseminator their keys. But I think freenet itself handles this problem. The very fact I'm getting DNF's is testment to the fact the freenet is very efficient (maybe a little too so) at weeding out stuff not accessed much like child pornagraphy with more active datastore things like stuff being censored by the DMCA and stuff (becuase that's a very hot topic right now). Freenet pretty much handles the child pornography on its own due to the way infrequently used data is preempted for newer data; and likely to require a lot of work of its maintainer (frequent inserts becuase it will degrade in the network rapidly becuase IMHO not a lot of people wish too see that material so they never request it - even more so because these are images and possibly even likely to be splitfiles - makes the maintenance to make the material accessible without the infamous DNF a lot of work for the maintainer of such sites). On the other hand the file degradation feature tends to be bad for trendy things. Where the first month a resource is placed into the network (oh an example I like, such as an anime fansub) and then it idles and erodes away. It frustrates the heck out of me becuase the freesite that links to one video I'd like to see is *still* there but the 700M video DNFs all over the place (it's a splitfile) while trying to fetch it. Somebody want to maintain a freesite that links to controversial material but doesn't link to illegal material? A lot of it is a matter of judgement and personal ethics - Thought Crime links to Mein Kampf and an article on bestiality as well as a lot of overtly political stuff. Anyway, YoYo's Controversy section is a good start. My thought on the home freesite links is that a good starter freesite should appeal to the majority of people and have the darker side of the freenet not bluntly proclaimed on the first page the freenet user sees. Splitting adult content away from general content/freenet/freedom links (ie having a single link to a separate freesite index for adult material may be a start in the right direction). This will at least make the first contact palatable for *anyone* entering the home freesite. Something that might also be good is have some duplication of material that isn't controversial, illegal, or typically censored (ie: kid-safe freesites, educational sites and the lot). So that the freenet looks more like the internet. This will encourage more people to use freenodes to access content. Hitting heavy on the no popups or banner ads slogan needs to be flogged way more than it's mere mention in the documentation now. I think a good one is run a banner on normal internet sites: run your own website! no size limit, no space limit! think this is a lie [click here] (links to freenet.sf.net). Another idea might be to encourage people to mirror their sites onto freenet if they are on gee-oh-sh*tties or yoohoo/homestead with their grossly commercialized page extras forced onto their clients' websites and add a link [to view this site without ads click here]. Which should link to a
Re: [freenet-support] Usability improvement ideas
On Thu, Mar 11, 2004 at 12:11:25PM -0800, Christopher Brian Jack wrote: There _has_ to be a question when installing asking the user if he/she pays for bandwidth (esp outgoing) and set the configuration in Freenet accordingly - bad press resulting from Joe Doe installing Freenet and getting $1000 bills (think NZ, OZ) isn't good. Hmm. Good idea. However, I'm not sure that you CAN run a freenet ndoe with any reasonable performance if it's limited to 3GB/mo as is common in oz. Technically, the solution is the average bandwidth limiter. However this is not known to work well (it is pretty much untested since NIO), mostly because no developers have that sort of connection. Perhaps we should put some effort in, but I'm not sure that it's proportionate as users with such connections won't get much out of or contribute much to Freenet. Yes, it might be useful for the occasional content author, so it IS worth thinking about; it's just that they'll be put off by the dire performance implied. But I'm not a developer and I do need to keep a leash on the bandwidth my node produces. I've set it to 24576 in/24576 out so hopefully overall I won't be leaching more than 48KiB/sec. I share a network with a friend who pays the bill (has a 50G/month limit) and I'd like to have a present, but, limited network bandwidth profile. He was really leary of letting me run a freenet node and he's all but banned kazaa and other related progs from being used by his roommates. Does it stick to the input limit? Also, the output limit is a little advisory - the node should very rarely use more than 40-50% over the limit, but it may use over 100% for longish periods. However it should average out because of rate limiting. Anyway, we know that the bandwidth limiters, especially the output bandwidth limiters, are vital for freenet to be widely adopted, that is why we have put so much effort into them. The point I was making was that many users have far more restrictive limits than the above - 3GB/mo works out to 1.2kB/sec! 50GB/mo works out to 20kB/sec... I suspect you may have problems with the above... Better portals. People _don't_ want links to child pornography (no, I don't want a discussion, flamefest etc, I'm talking the general public who want to USE Freenet) to be the first thing they see. Instead the top portal should contain links like the Diebold one, the Scientology Bible etc. Advertise the fact that Freedom of Speach is the central issue. This doesn't sound like such a bad idea. I'm sure persons delivering the really disgusting content have other channels for disseminator their keys. But I think freenet itself handles this problem. The very fact I'm getting DNF's is testment to the fact the freenet is very efficient (maybe a little too so) at weeding out stuff not accessed much like child pornagraphy with more active datastore things like stuff being censored by the DMCA and stuff (becuase that's a very hot topic right now). Freenet pretty much handles the child pornography on its own due to the way infrequently used data is preempted for newer data; and likely to require a lot of work of its maintainer (frequent inserts becuase it will degrade in the network rapidly becuase IMHO not a lot of people wish too see that material so they never request it - even more so because these are images and possibly even likely to be splitfiles - makes the maintenance to make the material accessible without the infamous DNF a lot of work for the maintainer of such sites). Interesting perspective. I hope you are right. On the other hand the file degradation feature tends to be bad for trendy things. Where the first month a resource is placed into the network (oh an example I like, such as an anime fansub) and then it idles and erodes away. It frustrates the heck out of me becuase the freesite that links to one video I'd like to see is *still* there but the 700M video DNFs all over the place (it's a splitfile) while trying to fetch it. Somebody want to maintain a freesite that links to controversial material but doesn't link to illegal material? A lot of it is a matter of judgement and personal ethics - Thought Crime links to Mein Kampf and an article on bestiality as well as a lot of overtly political stuff. Anyway, YoYo's Controversy section is a good start. My thought on the home freesite links is that a good starter freesite should appeal to the majority of people and have the darker side of the freenet not bluntly proclaimed on the first page the freenet user sees. Splitting adult content away from general content/freenet/freedom links (ie having a single link to a separate freesite index for adult material may be a start in the right direction). This will at least make the first contact palatable for *anyone* entering the home freesite. Yes, this is why I like YoYo. However all the major index sites have what's new
Re: [freenet-support] Usability improvement ideas
On Fri, Oct 31, 2003 at 10:31:58PM -0800, Paul wrote: I see the installation of Freenet and the configuration of Freenet to be an area that needs serious attention. First, I use Freenet on a Mac, but Mac OS X is not shown anymore as a compatible OS on the Freenet web site download page. It used to be there, but not anymore. I know to use the Linux download and instructions, but the only reason I know that is because the web site used to state this. A new user will likely not realize this. Second, the install process needs to be easier. Yes, installing Freenet is as simple as copying over a handful of files, but a single-click install program is very nice. The Mac .pkg format is simple and effective, and it allows scripts to be included and run during the installation process. Care to volunteer? I don't have a Mac to develop a package on. Third, configuring Freenet is a major pain. Right now, in order to copy over my few custom .conf file settings, I have to first fake out Freenet into thinking that it is running for the first time so it creates a new .conf file with default settings. Then I bring up both the new .conf file and the old one in a text editor, and go through each setting, line by line, an copy over my custom settings into then new .conf file. Why can't you just copy over the old .conf file? Any settings that haven't been overridden will be commented out and therefore the node will use the default settings. If each new update of Freenet would be able to read in the last version's .conf file, add new options to it, that would be a good start. There is an option to do this. An even better improvement would be a nice GUI tool to edit and maintain all of Freenet's configuration options. We have thought about doing it via the web interface. We don't want actual GUI code in the main Fred tree. Fourth, starting and stopping Freenet is a pain. I have to bring up the Terminal, and type in a command line to start and stop Freenet. This is extremely un-Mac-like and you will loose 99% of your potential users when they see that they HAVE to use the command line to get Freenet to run. A simple double-clickable icon is what people want. Well, Mac users are probably 5% of our target market (linux about 30% and the rest windows), probably. It would be nice to have a proper package. All of these could easily be done on the Mac with an Applescript Studio type application. I've seen people write a really good GUI front-end to command line programs in a matter of days with Applescript Studio. Linux would also benefit from all of the above improvements. The first impression of Freenet is the install and configuration process. Right now this process gives a new user a distinctly negative impression of Freenet. This impression just gets worse when they run it for the first time and can't load any sites. But that's a whole other discussion... Paul -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Usability improvement ideas
On Friday 31 October 2003 12:54 pm, Doug Bostrom wrote: The splitfile interface provides a useful measure of progress or at least continued activity. How about something to give users a little feedback while other key types are being retrieved? Browsers generally provide some kind of indication of progress, but some just lie (IE) and if there's no progress in bytes retrieved, many users new to Freenet will likely assume nothing is happening and either try another key or give up even though productive activity is happening behind the scenes. Why not feed the site through the filter dynamically and once some is filtered, send it out to the browser? Before there's anything even to filter, it could say, like, mapfile retrieved, DBR root retrieved, although this would tend to confuse newbies. Maybe we need to ship some good documentation available directly from FProxy. -- I love deadlines. I love the whooshing sound they make as they go by. - Douglas Adams Nick Tarleton - [EMAIL PROTECTED] - PGP key available ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Usability improvement ideas
On Sat, Nov 01, 2003 at 11:35:53AM -0500, Nick Tarleton wrote: On Friday 31 October 2003 12:54 pm, Doug Bostrom wrote: The splitfile interface provides a useful measure of progress or at least continued activity. How about something to give users a little feedback while other key types are being retrieved? Browsers generally provide some kind of indication of progress, but some just lie (IE) and if there's no progress in bytes retrieved, many users new to Freenet will likely assume nothing is happening and either try another key or give up even though productive activity is happening behind the scenes. Why not feed the site through the filter dynamically and once some is filtered, send it out to the browser? Before there's anything even to filter, it could say, like, mapfile retrieved, DBR root retrieved, although this would tend to confuse newbies. Maybe we need to ship some good documentation available directly from FProxy. Last I heard Ian was opposed to putting documentation on fproxy. -- I love deadlines. I love the whooshing sound they make as they go by. - Douglas Adams Nick Tarleton - [EMAIL PROTECTED] - PGP key available -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Usability improvement ideas
On Sat, Nov 1, 2003 at 14:10:43 +0800, Toad wrote: On Fri, Oct 31, 2003 at 10:31:58PM -0800, Paul wrote: I see the installation of Freenet and the configuration of Freenet to be an area that needs serious attention. First, I use Freenet on a Mac, but Mac OS X is not shown anymore as a compatible OS on the Freenet web site download page. It used to be there, but not anymore. I know to use the Linux download and instructions, but the only reason I know that is because the web site used to state this. A new user will likely not realize this. Second, the install process needs to be easier. Yes, installing Freenet is as simple as copying over a handful of files, but a single-click install program is very nice. The Mac .pkg format is simple and effective, and it allows scripts to be included and run during the installation process. Care to volunteer? I don't have a Mac to develop a package on. I had a feeling you might ask that. While I can program, I just do not have the time right now to learn the specifics of how to do this, and then do it. The time investment goes beyond doing this once. I'd have to do it for every single release. And at the rate they are coming these days, that's a huge amount of time. Third, configuring Freenet is a major pain. Right now, in order to copy over my few custom .conf file settings, I have to first fake out Freenet into thinking that it is running for the first time so it creates a new .conf file with default settings. Then I bring up both the new .conf file and the old one in a text editor, and go through each setting, line by line, an copy over my custom settings into then new .conf file. Why can't you just copy over the old .conf file? Any settings that haven't been overridden will be commented out and therefore the node will use the default settings. Problem with this is that I then have no idea what the new options are. I might want to, or need to, tweak the new options. If each new update of Freenet would be able to read in the last version's .conf file, add new options to it, that would be a good start. There is an option to do this. Yeah, but it uses the command line which is what I'd like to get away from completely. Command-line = very difficult usability An even better improvement would be a nice GUI tool to edit and maintain all of Freenet's configuration options. We have thought about doing it via the web interface. We don't want actual GUI code in the main Fred tree. A web interface would be great and be very universal. Is this comming soon? Fourth, starting and stopping Freenet is a pain. I have to bring up the Terminal, and type in a command line to start and stop Freenet. This is extremely un-Mac-like and you will loose 99% of your potential users when they see that they HAVE to use the command line to get Freenet to run. A simple double-clickable icon is what people want. Well, Mac users are probably 5% of our target market (linux about 30% and the rest windows), probably. It would be nice to have a proper package. Linux and Mac OS X are, at the low-level, the same: UNIX It's just that Apple has put a great set of API extensions on top of it to create the easiest to use OS available. So if usability improvements are made in a universal way that also works under Linux, then both the Mac users and Linux users would benefit. That's 35% of Freenet users. Is there anything like Fink (http://sourceforge.net/projects/fink/) in the Linux world? With the addition of the GUI tool, Fink Commander, Fink is just usable on the Mac. If there was a compatible tool under Linux, you might be able to unify the Mac OS X and Linux Freenet packge. Another usability suggestion to help Mac users: Mac OS X does not come with wget. So the update-freenet.sh script will not run. Mac OS X does include curl which I think is similar to wget. Any chance of having the update script use curl incase wget is not installed? All of these could easily be done on the Mac with an Applescript Studio type application. I've seen people write a really good GUI front-end to command line programs in a matter of days with Applescript Studio. Linux would also benefit from all of the above improvements. The first impression of Freenet is the install and configuration process. Right now this process gives a new user a distinctly negative impression of Freenet. This impression just gets worse when they run it for the first time and can't load any sites. But that's a whole other discussion... Paul -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -Paul ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Usability improvement ideas
On Saturday 01 November 2003 05:13 pm, Paul wrote: On Sat, Nov 1, 2003 at 14:10:43 +0800, Toad wrote: On Fri, Oct 31, 2003 at 10:31:58PM -0800, Paul wrote: I see the installation of Freenet and the configuration of Freenet to be an area that needs serious attention. First, I use Freenet on a Mac, but Mac OS X is not shown anymore as a compatible OS on the Freenet web site download page. It used to be there, but not anymore. I know to use the Linux download and instructions, but the only reason I know that is because the web site used to state this. A new user will likely not realize this. Second, the install process needs to be easier. Yes, installing Freenet is as simple as copying over a handful of files, but a single-click install program is very nice. The Mac .pkg format is simple and effective, and it allows scripts to be included and run during the installation process. Care to volunteer? I don't have a Mac to develop a package on. I had a feeling you might ask that. While I can program, I just do not have the time right now to learn the specifics of how to do this, and then do it. The time investment goes beyond doing this once. I'd have to do it for every single release. And at the rate they are coming these days, that's a huge amount of time. You wouldn't have to redo it every release; except for new configuration options, you would just have to change the version number and stick in the new JAR. Right? (I'm a Mac imbecile.) -- I love deadlines. I love the whooshing sound they make as they go by. - Douglas Adams Nick Tarleton - [EMAIL PROTECTED] - PGP key available ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Usability improvement ideas
On Friday 31 October 2003 07:37, Ian Clarke wrote: So, this email is an invitation to anyone that has constructive criticism or suggestion's for how Freenet's first impression can be enhanced. Topics include installation, FProxy, even the website's layout. Ian. The splitfile interface provides a useful measure of progress or at least continued activity. How about something to give users a little feedback while other key types are being retrieved? Browsers generally provide some kind of indication of progress, but some just lie (IE) and if there's no progress in bytes retrieved, many users new to Freenet will likely assume nothing is happening and either try another key or give up even though productive activity is happening behind the scenes. My host here has about 80MB of data constantly queued for transmission over 100 or more connections sharing a 15kB uplink. I find myself wondering who will wait for any of this to arrive and how much of this queue will actually arrive at a client instead of being aborted. I suspect such failed attempts probably degrade the overall network performance a bit, so a progress indicator might help the network as a whole by reducing accesses truncated due to impatience. Good on you for asking for suggestions! ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Usability improvement ideas
One thing people haven't suggested yet: Log file rotation with deletion of old logfiles and a maximum space usage setting. On Fri, Oct 31, 2003 at 12:37:27PM +, Ian Clarke wrote: As the developers work hard to improve the core operation of Freenet, it can be easy to forget about the more superficial, but equally important aspects of Freenet, namely installation procedures, and usability for newbies. For those intimately familiar with Freenet's operation it can be difficult to look at Freenet's operation from the perspective of someone new to the software, and often something that seems minor and trivial to a core developer, might have a significant impact on a new user's view of the software. So, this email is an invitation to anyone that has constructive criticism or suggestion's for how Freenet's first impression can be enhanced. Topics include installation, FProxy, even the website's layout. Ian. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Usability improvement ideas
[EMAIL PROTECTED] wrote: freenet:// handled by Opera, Firebird etc. If Freenet isn't installed, a redirection to http://freenet.sf.net where the download links are more prominently displayed. We have debated the whole freenet:xxx thing before and there are serious problems with it - not least of which that it will force us to start maintaining a different Freenet plugin for each version of each different web browser, this could rapidly turn into a support nightmare. Combine this with the fact that there is little other than an asthetic benefit to this. Ian. ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Usability improvement ideas
On Fri, 31 Oct 2003 15:57:49 +, Ian Clarke [EMAIL PROTECTED] wrote: freenet:// handled by Opera, Firebird etc. If Freenet isn't installed, a redirection to http://freenet.sf.net where the download links are more prominently displayed. We have debated the whole freenet:xxx thing before and there are serious problems with it - not least of which that it will force us to start maintaining a different Freenet plugin for each version of each different web browser, this could rapidly turn into a support nightmare. Combine this with the fact that there is little other than an asthetic benefit to this. You asked what is needed for general acceptance of Freenet, I replied. I've advocated Freenet for a long time along my peers (I'm a professional Software Engineer, specialising in crypto/security issues) - and trying to get people to visit links to http://localhost: isn't working. Other programs (e2dk:// I believe) do this - Freenet needs it as well. My experience is that this is a central issue for regular people - your mileage may of course differ. This is a project where I would expect people who feel strongly about the issue to be the ones who'll maintain it. I'll gladly do what needs to be done towards Opera since that's my browser of choice. ___/ _/ -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-dev] Re: [freenet-support] Usability improvement ideas
Troed Sångberg wrote: You asked what is needed for general acceptance of Freenet, I replied. And I disagreed. I've advocated Freenet for a long time along my peers (I'm a professional Software Engineer, specialising in crypto/security issues) - and trying to get people to visit links to http://localhost: isn't working. Just how are you trying to get people to visit such links? Verbally? If so, I suspect that it might not be the http://localhost:/; part of the URL that puts them off, but rather the [EMAIL PROTECTED],UUleYfXnBfLThNmkB8dACg part might be the bit with which they are having trouble. freenet:xxx URLs won't change that, but they will introduce a world of pain. Freenet URLs are much more likely to be given to people in hyperlink form, in which case the actual form of the URL isn't particularly relevant. The whole freenet:xxx thing is purely cosmetic. Ian. ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-dev] Re: [freenet-support] Usability improvement ideas
On Fri, 31 Oct 2003 18:03:33 +, Ian Clarke [EMAIL PROTECTED] wrote: Just how are you trying to get people to visit such links? Verbally? If Thanks for calling Freenet advocates idiots - but the reaction is more pity from my side than anything else. http://localhost:; is what people find weird. They're used to http://; ftp://; etc and for them Freenet isn't serious until treated likewise. I'll look into what needs to be done, and simply do it. It doesn't matter if you think it's purely cosmetic or not :) ___/ _/ -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-dev] Re: [freenet-support] Usability improvement ideas
[EMAIL PROTECTED],UUleYfXnBfLThNmkB8dACg part might be the bit with which they are having trouble. freenet:xxx URLs won't change that, but they will introduce a world of pain. Freenet URLs are much more likely to be given to people in hyperlink form, in which case the actual form of the URL isn't particularly relevant. The whole freenet:xxx thing is purely cosmetic. Except that you also have to mandate that everyone uses localhost: and not everyone can. Some people will want to use proxies, others will want to use a different port. Standardising on a freenet: hyperlink is just an obvious thing to do. It would also make freesite pages saved to disk work more reliably if passed around. I say go for it, but the way to do it is for the plugins to be done as separate projects and their releases included as a part of a freenet distribution if a stable one ever happens. Does anyone have any decent docs on netscape plugin architecture? ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] Usability improvement ideas
Quoting Ian Clarke [EMAIL PROTECTED]: So, this email is an invitation to anyone that has constructive criticism or suggestion's for how Freenet's first impression can be enhanced. Topics include installation, FProxy, even the website's layout. freenet:// handled by Opera, Firebird etc. If Freenet isn't installed, a redirection to http://freenet.sf.net where the download links are more prominently displayed. There _has_ to be a question when installing asking the user if he/she pays for bandwidth (esp outgoing) and set the configuration in Freenet accordingly - bad press resulting from Joe Doe installing Freenet and getting $1000 bills (think NZ, OZ) isn't good. More advertising. Atm Diebold are shutting down sites hosting their memos using the DMCA. Educate the world to the fact that Freenet can be used for the public good - the memos are already available in Freenet. Better portals. People _don't_ want links to child pornography (no, I don't want a discussion, flamefest etc, I'm talking the general public who want to USE Freenet) to be the first thing they see. Instead the top portal should contain links like the Diebold one, the Scientology Bible etc. Advertise the fact that Freedom of Speach is the central issue. I just wrote a comment to an article in Sweden's largest IT-newssite where I brought this up (regarding the Swedish military wanting to tap regular users' Internet-connections). This is where we need to push Freenet. (http://www.idg.se/ArticlePages/200310/31/20031031135522_SOS/20031031135522_SOS. dbp.asp for the ones who can read Swedish) ___/ _/ - This mail sent through IMP: http://horde.org/imp/ ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
