Or here, or the PG forums, or wherever - it's all good. If you run into any let us know! You can add entries to our Issue Tracker, discuss them on our Forums, or even just report them to me via email.
The "Gov" list was merged into the "P2P"/"Bluetack Level1" list a year or two (?) ago, which is why we removed it.ĭave88/Fajo/et al: Glad to hear PeerBlock is working well for you! As I said there are likely additional bugs in there, both known and unknown. The Installer/Uninstaller was nearly completely rewritten in recent Interim Releases, and I believe cleans up pretty much everything now - again, a heck of a lot better than the old PG2 installer. (And is currently, in my admittedly biased opinion.) There are still likely to be some bugs even in that release, but it should be pretty darn good I think.
#PEERGUARDIAN OFFICIAL SITE DRIVER#
We're trying to concentrate on fixing all the "Show Stopper" bugs right now, as we gear up for an official PeerBlock 1.0 release once we have a signed driver available. That said we're still much more stable than PG2 RC1 is - there are so many bugs in that release I really wouldn't recommend anybody using it. There are still a number of bugs in there, as per our Issue Tracker. Once a number of Interim Releases have been put out, and they've been sufficiently tested that we don't believe there are any excessively nasty bugs in there, we'll roll them up into a new Public Release.Īs far as these releases go, I'd really define them all as at a "Beta" level. Interim Releases are available from our Dev Blog, and generally contain fixes and new features that haven't yet had enough airtime to be considered stable enough for inclusion in a Public Release yet. Difficult to define "stable" at this point in our development cycle, but they at least have had a lot more test-time than our other builds. Public Releases, available from the main site, we try to ensure are as stable as can be. Tipstir: We actually have two "release trains" - Public and Interim. Otherwise, sorry it didn't work out for you for whatever reason, and hopefully a future version will. Unless it's a different problem entirely, in which case I'd love to get a copy of your peerblock.log file if you still have it lying around by some chance so I can see what went wrong and fix it.
#PEERGUARDIAN OFFICIAL SITE UPDATE#
But if you'd update your list-servers as per the instructions linked-to on our main download page ( ) I'd be willing to bet things would work much better for you. Starting with r93 PeerBlock will instead use lists hosted at on new installs these list-servers are much faster and more reliable, and are hosted by "fakhir", one of the site admins / founders over at the PeerGuardian website so can be trusted as much as you'd trust the PG2 list-servers.ĭon't know why PG2 would be able to update lists from those serverswhile PeerBlock would not, probably just luck of the draw. If you were running r86, that release still makes use of hosted list files by default - those servers are notoriously unreliable, and are the source of most peoples' list-updating problems. Out of curiosity, do you remember if you were running the "Public Release" (0.9.2, r86) available from our main website, or the latest "Interim Release" (r93) from our Development Blog at ?
Hmm, sorry you ran into some problems, tipstir.
0 kommentar(er)
