Re: [freenet-support] links and images removed after update from 534
Nicholas Sturm ([EMAIL PROTECTED]) wrote: > I would consider running a more nearly permanent node if someone > (could and wanted to offer a little more explanation of setting up > a dynamic IP address). I looked over the site. Sort of presume when > that became really desirable someone would offer a little more guidance. Register with a dynamic DNS service. Most of these are free of charge, but they sometimes go away when the operator runs out of funds, time and/or patience. Some of them charge a small amount of money per month. Then, instead of putting your IP address in the node's config file, you just put your dyn-dns name. A quick glance at a seednodes.ref file will probably turn up several examples of this. From my current one: physical.tcp=ncsi.dyndns.ws:33655 physical.tcp=benedikt.dyndns.info:33628 physical.tcp=nf.dyndns.org:11559 physical.tcp=donadona.dyndns.org:36333 physical.tcp=xiexie.dyndns.org:12056 One of the features that Matthew's actively working on for the next major stable release of Freenet (as opposed to the little "bug-fix" [*cough*] releases we've been getting) is something called "ARK", which, as far as I've been able to deduce, is aimed at making this dynamic DNS business unnecessary. Nodes will be non-transient by default, and manual configuration of the IP address won't be required any more. Meanwhile, get a dyn-dns name and use it -- simple enough for most of us, but a bit outside the scope of the Freenet support mailing list, since it's so OS- and provider-specific. (Windows users who've done this are welcome to speak up here. I don't do anything but games with Windows, so I can't offer much guidance here.) -- Greg Wooledge | "Truth belongs to everybody." [EMAIL PROTECTED] |- The Red Hot Chili Peppers http://wooledge.org/~greg/ | msg02584/pgp0.pgp Description: PGP signature
Re: [freenet-support] links and images removed after update from 534
My impression sometime ago. When I saw to (new build item and the new GUI)/ I would consider running a more nearly permanent node if someone (could and wanted to offer a little more explanation of setting up a dynamic IP address). I looked over the site. Sort of presume when that became really desirable someone would offer a little more guidance. Nicholas Sturm [EMAIL PROTECTED] > [Original Message] > From: Greg Wooledge <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Date: 1/13/2003 9:44:34 PM > Subject: Re: [freenet-support] links and images removed after update from 534 > > Nicholas Sturm ([EMAIL PROTECTED]) wrote: > > > When I'm acquiring a new build, it simply replaces the previous one -- I > > don't have two at the same time > > unless an error occurs, powie. > > I've learned to be more conservative in my approaches to software > updates. This is especially true in cases of software where past > trends have led me to hold a relatively low level of optimism for > new releases. > > > Now that I'm not trying to run a permanent node, I > > don't even get the usual notice to undate. > > Nobody gets the explicit notices any more (unless they're on very > old builds); instead, there's a parenthetical note on the web > interface (gateway page) if your node has observed another which > claims to have a higher build number within the same "family" (5xx > [stable] or 6xx [unstable]). It's quite easy to overlook this, or > to ignore it. Some of us ignore it intentionally, at least for a > while. ;-) > > --=20 > Greg Wooledge | "Truth belongs to everybody." > [EMAIL PROTECTED] |- The Red Hot Chili Peppers > http://wooledge.org/~greg/ | ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] links and images removed after update from 534
Nicholas Sturm ([EMAIL PROTECTED]) wrote: > When I'm acquiring a new build, it simply replaces the previous one -- I > don't have two at the same time > unless an error occurs, powie. I've learned to be more conservative in my approaches to software updates. This is especially true in cases of software where past trends have led me to hold a relatively low level of optimism for new releases. > Now that I'm not trying to run a permanent node, I > don't even get the usual notice to undate. Nobody gets the explicit notices any more (unless they're on very old builds); instead, there's a parenthetical note on the web interface (gateway page) if your node has observed another which claims to have a higher build number within the same "family" (5xx [stable] or 6xx [unstable]). It's quite easy to overlook this, or to ignore it. Some of us ignore it intentionally, at least for a while. ;-) -- Greg Wooledge | "Truth belongs to everybody." [EMAIL PROTECTED] |- The Red Hot Chili Peppers http://wooledge.org/~greg/ | msg02581/pgp0.pgp Description: PGP signature
Re: [freenet-support] links and images removed after update from 534
The idea of using an older build is probably much more meaningful to some than to others (many others?). When I'm acquiring a new build, it simply replaces the previous one -- I don't have two at the same time unless an error occurs, powie. Of course I used to have a lot of old version of various files, but why I had no idea until they seemed rather redundant, but then they ceased to be a common situation. Now that I'm not trying to run a permanent node, I don't even get the usual notice to undate. Nicholas Sturm [EMAIL PROTECTED] > [Original Message] > From: Greg Wooledge <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Date: 1/13/2003 8:27:35 PM > Subject: Re: [freenet-support] links and images removed after update from 534 > > Phil L ([EMAIL PROTECTED]) wrote: > > > well, I had the same problem yesterday. unfortunately I had to delete my= > =20 > > 9 gig datastore and reinstall 534 :( this really sucks > > WHY did you delete the data store? The anonymity filter bugs in > some of the recent builds do not affect the contents of the data > store, nor the communications between nodes. They only affect what > is sent from the node to the browser via the fproxy (mainport) port. > > Everything in your data store should have been fine, unless you're > seeing a different bug than everyone else is. Restarting the node > with an older build of freenet.jar was all you had to do. > > --=20 > Greg Wooledge | "Truth belongs to everybody." > [EMAIL PROTECTED] |- The Red Hot Chili Peppers > http://wooledge.org/~greg/ | ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] links and images removed after update from 534
Phil L ([EMAIL PROTECTED]) wrote: > well, I had the same problem yesterday. unfortunately I had to delete my > 9 gig datastore and reinstall 534 :( this really sucks WHY did you delete the data store? The anonymity filter bugs in some of the recent builds do not affect the contents of the data store, nor the communications between nodes. They only affect what is sent from the node to the browser via the fproxy (mainport) port. Everything in your data store should have been fine, unless you're seeing a different bug than everyone else is. Restarting the node with an older build of freenet.jar was all you had to do. -- Greg Wooledge | "Truth belongs to everybody." [EMAIL PROTECTED] |- The Red Hot Chili Peppers http://wooledge.org/~greg/ | msg02577/pgp0.pgp Description: PGP signature
[freenet-support] links and images removed after update from 534
well, I had the same problem yesterday. unfortunately I had to delete my 9 gig datastore and reinstall 534 :( this really sucks what's wrong with sf?? [This E-mail scanned for viruses by Declude Antivirus] [http://www.swissworld.com] ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
