Something like that could work well. I dislike upgrading ubernode.org, because it leaves people stranded. I know we don't want to migrate problems from the old builds to the new ones, but if we accepted only a Few packets from them they could still get out the critical "The British are coming!" Message, if need be.
What about a UserAlert in fproxy- "A New 'mandatory' build has been released- It is HIGHLY recommended that you upgrade to this build immediately. Remaining with this version of Freenet will result in DRASTICALLY reduced performance. Click here to upgrade." All in all, it seems a Much more graceful solution. On Jun 29, 2006, at 7:58 PM, Evan Daniel wrote: > Now that we have an auto-updater, it seems there is more reason than > normal not have self-mandatory builds. > > What if, instead of refusing to talk to old builds, nodes simply only > allowed a very small number of requests from them, and routed a small > (or zero) number to them? It seems to me that would be sufficient for > most of the reasons that mandatory builds happen. > > This would allow people with old builds (if they've been on vacation, > or more importantly if they got the build from a distro package or > some such) to connect at least enough to run the auto-updater. > > It also seems a node could prioritize (local) auto-updater requests > over other requests without hurting security, and that it would want > to if it was being throttled as penalty for being old, so that it > would get the update finished ASAP. > > Thoughts? > > Evan Daniel > _______________________________________________ > Tech mailing list > Tech at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/tech
