Bob wrote:
(1): Can I LOCK OUT automatic installation of updates? I MUST be able to choose when updating happens.
Right now, the internal capacity for updates is broken. The only way to update is a manual download/install, at least for Windows/Mac.
On my Ubuntu box, I do have the ubuntuzilla repository enabled, and it happens frequently enough that that installation gets updated through package updating processes before I get around to updating Windows or Mac.
(2): How up-to-date is Seamonkey kept? I already have strong security on my system, but need to avoid security holes.
I believe that security updates up through Firefox ESR 68.10 have been backported, and developer notes indicate that there's a little bit of stuff from 78.0 ESR that have been backported, as well.
(3) How easy is it now to migrate Bookmarks, passwords, and so on?
Not sure. For Bookmarks, you can probably start with export to HTML, and then import that into Seamonkey, but I've never tried that. That process is pretty much standard for moving stuff from one profile to another, whether Firefox or Seamonkey.
As an aside, one of the things that I do with Seamonkey is to make use of the tool that allows for automatic export of bookmarks at the end of the session. From there, with other browsers and profiles, I tend to set them to use that file as their home page, and as a result, all of my browsers have access to all of my bookmarks, at least as of the end of my last Seamonkey session. The visual layout isn't great, but it's an easy way to share bookmarks.
I haven't tried to migrate passwords, so I can't comment there. There might be something in an article at mozillazine.org
You probably can't copy files from one profile to another, even if they're all the same file name. In the same way that Firefox versions after about 57.0 are not backward-compatible, the same applies to Seamonkey since 2.53.0. If you want to test, you probably can copy files (e.g., bookmarks, passwords) from a Firefox profile to a Seamonkey profile where you understand that what Seamonkey is interacting with is test copies (and you still consider your Firefox data to be authoritative), it might work, but if it doesn't, then you'll see the effects of what "not backward portable" looks like.
Ultimately, for live data, you're going to want to export/import, rather than trying to copy.
(4): "Bonus" question - is the composer still part of Seamonkey?
It's still there, usable, but unsupported. I have a handful of HTML files that I used to maintain with the composer -- I really like the convenience of viewing something, and pressing CTRL-E to be able to edit. However, a couple of years ago, I moved to using the stand-alone Kompozer, which has a little more capacity. It's also unsupported, but it's newer than using the bundled composer. Much newer (and supported, I think) is Blue Griffon, but I find that has enough UI quirks to it that I prefer Kompozer.
I use Ubuntu 18:04 LTS - switched to it around the time I abandoned Office and IE (for security and other valid reasons).
Although I primarily work in Windows 10, I do use Seamonkey on an installation that I just upgraded to Ubuntu 18.04 from 16.04, and it pretty much behaves the same way in Ubuntu as it does in Windows. Because I have a strong preference for doing package maintenance by repository and APT, and since Ubuntu's maintainers no longer distribute Seamonkey, I'm getting my updates from ubuntuzilla.
The one thing to be aware of is that there's a growing number of sites that claim not to be able to handle Seamonkey, and demand Firefox. Seamonkey 2.53.3 is set to show compatibility with Firefox 60, but that's now old enough that more sites are objecting unless they see Firefox levels at at least 68.0. Most sites are satisfied if they see "Firefox 68.0" and you can do that with making one or more entries in about:config (either global or site-specific). It's not so much that sites *can't* handle Seamonkey, by making use of features that Firefox 78 has and Seamonkey 2.53.3 does not, so much as site operators that don't want users to run browsers that they deem to be "old" or "insecure" or just "not Firefox" (the latter for purposes of user support).
Smith _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
