I can only help you with a couple of points:
There is no way to disable update messages. I never liked this every session message concept but my request to have an option to delay to once a week or month or so was ignored several years back.

Forcing Windows shutdown will always risk losing data and settings. It's something that should only be done as a last resort.

There will always be a version that does not work well on some people's systems. There are often workarounds but should be done with care.

The major difference in version 5.6.6 over version 5.6.5 was the addition of the integrated, auto-updating security feature requested by (and maintained by) Lord of the Rings. This feature was a major improvement to WireShare in terms of security. Just like antivirus software, the security files need updating periodically to protect users from malicious hosts and spammers. Unfortunately, the connection issue that you and others may have had with version 5.6.6 was not due to WireShare itself but was caused by a faulty online security file it had auto-updated to. This issue occurred if you had the "Strong Security" selected and was cause by an empty line in the security file. So, once the problem was identified, the online file was corrected and the issue was resolved.

Sorry, there is currently no way to disable the update notification at startup. I never considered that some people might prefer to use outdated versions. I will add a "Do not remind me again for this version." option to the next release. You would have to update to it though.

The major improvement in version 6.0.0 (Windows and Linux) is the code base was updated from 1.6 to Java 1.8 and added openJDK compatibility. The minor improvements made were; removed the Japanese blocking options (requested by LOTR), updated client preferencing, fixed some small bugs, and bundled the Java 1.6 runtime into MacOS app.

BigJx

FEEDBACK:



In WireShare 6.0.1 Options, the Transfers tab, Configure Torrent Settigns button, there should be "Seed forever" by default, current 1 day seeding only is too strict.


Also on Transfers tab in Options i think should be ~/Downloads, not ~/WireShare/Saved/ (or ~/Downloads/WireShare/ to prevent people accidentally sharing downloads not related to WireShare)


"View / Hide transfer Tray" should not be active by default, why not display Downloads tray right away by default, so user does not need to spend time searching where it is.

Originally it was for longer, but due to (legal) pressure the LimeWire developers changed this. At least that is what I was told when I had the same concern over a decade ago. Unless I am confusing this with FrostWire version 4.

Personally I agree with your concern.

One problem there is I see a lot of users on the network of various gnutella programs that share from their default downloads folder. They also accidentally share other files they may have downloaded via their web browser. This sometimes includes private information.

Just now looking at a particular host presently running on the network, their share statistic is:
196612/8,192 bytes

That's a total of 8 KB. Divide that by 196612 to get the average file size. Bytes becomes bits.

I am unable to browse the host to verify what kind of rubbish they are sharing. I doubt the host user is aware of this. But it is just this kind of accidental file sharing that is best avoided where possible. With WireShare having its own distinct downloads (& share) folder, this problem is minimized.

Your final point is also a good point. Though based off LimeWire 5, the LW 5 version was rebuilt from the ground up and intended to imply simplicity in its visual design compared to LW 4.

Replying regarding the issue of accidentally sharing sensitive files from Downloads folder, for example sensitive .pdf, .docx downloaded via web browser may be reduced like this:
1) changing description in Options / My Files / Configure (unsafe file sharing) by mentioning something like: Make sure that your Downloads folder is not common for other apps to store sensitive files like documents.
2) disabling documents sharing for downloads folder permanently internally in app

3) set default downloads folder to ~/Downloads/WireShare/ because i think for Linux user it is more convenient location he may not want to change as much as current ~/WireShare/Saved/

Not a bad idea.
Some persons purposely share certain types of documents. This may also include pdfs or MS Word docs. This might include non-copyright ebooks or 'how to' docs. h4x5h17 points this out in their post of https://www.gnutellaforums.com/gener...tml#post377157

There is a safe sharing option listed under 'programs':
(Edit) (An option we agreed should be incorporated. It's just not as obvious as it should be when listed under programs.)

I did not necessarily agree with the original download location design which went through some kind of name changes within the LW 4 sub-versions. But on the other hand, you need to differentiate between downloads/saved and incomplete folders & the present system does that but within the WireShare parent folder.

I personally used customized locations and folder titles. (1) A different hard disk drive with different downloads folder title. (2) Video and audio file downloads are each sent to different folders. This makes it much easier to find particular download types. Many years ago I even had them sent to different hard disk drives.
But that is a customized approach and nothing to do with the defaults.

The WireShare GnutellaWebCache (GWC) that is used for bootstrapping is now being redirected to https. As a result, all WireShare versions prior to 6.0.2 will no longer be able to connect to the GWC as https was not supported in those versions. Therefore, it is now recommended that all users update their WireShare to version 6.0.2 to; avoid connection issues, get security updates, and get update notifications in the future.

BigJx

This is an unexpected issue and earlier WireShare version users will no longer be able to get update notifications due to the https change. The https change was forced upon the WireShare project, not by choice. For example, version 5.6.6 no longer receives any form of notifications including version updates. Also versions 6.0.1 and earlier can no longer access the primary GWebCache (GWC.)
But the https change will have benefits. That includes potentially improved communications through a firewall and other benefits.

That's a shame. What Java is required and will it work with older PC's? I had a lot of trouble updating Java last time and making it actually work.

No java update is required to upgrade from either v6.0.0 or v6.0.1 to v6.0.2. The code is still Java 8 based (Windows version requires 32bit Java).

BigJx