Under Advanced tools, Connections, add a connection:
the "TLS" what does that stand for and what does it do?
Does that help or hinder adding known hosts?
I am still running 5.6.4.3

Transport Layer Security (TLS) to allow more secure communications across the network and used by the more modern gnutella programs. Using this will tend to invite the likes of Lime-code based apps, GTK-Gnutella and Phex but exclude the older apps. I don't know much more.

The earliest Lime code based implementations of TLS often had a side effect of causing problematic connecting to the network (possibly due to the TLS software implementation not being universally compatible with all hardware routers.) Both Cabos and Acqlite even had TLS disabled by default. But it was improved by the release of LimeWire 4.18 (of which the Cabos & Acqlite dev forgot to implement despite his last update around the same time.)

WireShare 5.6.6 is fine to update to. You will no doubt also better benefit from the hostiles updater it provides which was added for this version and by the gradual removal of out-of-date data (which also applies to WireShare) will help provide more hosts to connect to and share files with. Hostile updates are done silently, at start of a session when any updates exist. This version also utilizes GWebCache to help find fresh hosts to connect to.
I don't personally agree with some of the changes (removals) to the Adult filter (WireShare 5.6.4) that over-rided a small part of my work of a few years ago. But I guess ignoring years of real-time research is irrelevant and decisions based on whims is much more than fine.

Thanks for that very necessary information. I have not had great luck recently with 5.6.4. So I will be updating. Sorry to hear about the filter though. Years of research cannot be replaced by whims and assumptions.

A follow-up on this, 5.6.6 has increased my connections probably 5 times over the 5.6.4.3 version. Big difference!
Plus, I used the maximum filtering with total Japanese block setting. I'm hooking up with hosts super quickly and when
there's a drop, A new one will fill in immediately just like LW did in 2009.

Good to hear!

Personally I am not sure the full Japanese block is necessary these days. Due to the automatic blocking of a few types of BOTs added during my time working directly with the WireShare project, the only other hostiles are mostly or totally blocked via the hostiles file of which WireShare 5.6.6 updates periodically. That's after I eventually discovered the Japanese Browse-BOTs ID's and sources. I suggested to Big_jx last year it is probably time to remove the Japanese full-block hostiles version(s).

As far as connections go, if you really do have a bad day with WireShare finding connections, try removing (not necessarily deleting) the gnutella.net file from the WireShare settings folder before opening the program or closing the program down (make sure not still in Tray or Dock), removing the gnutella.net file then re-opening the program. A boot file will then be downloaded by the program as it's started for WireShare to connect with.

If not sure about the WireShare settings folder, for Windows: Search > type %appdata% into the text field.
Alternatively see http://www.gnutellaforums.com/genera...ows-7-8-a.html but replace the word limewire for wireshare.
MacOSX: OSX > Users > Account Name > Library > Preferences > WireShare.
Or via OSX Terminal: open ~/Library/Preferences/WireShare
Linux: CD ~/.WireShare
(if Ubuntu): nautilus ~/.WireShare

But do not delete the entire folder or the gnutella.net file at this point.