In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a year later. Another three years later, the SeaMonkey project is discontinuing support for the SeaMonkey 1.x series today in favor of SeaMonkey 2.0, which is not only more modern, but also maintained for stability and security problems.
As the SeaMonkey 1.x series no longer receives security updates, due to resource constraints, the SeaMonkey team strongly urges users of that series to upgrade. Additionally, the team continues to strongly urge people still using the old Mozilla Suite or Netscape 4, 6 or 7 to upgrade to the new SeaMonkey 2.0 version. All these older software packages suffer from a large, and steadily increasing, number of security vulnerabilities because they are no longer being maintained.
Everyone on reasonably modern operating systems is urged to switch to the newest release available for free download from the open source project’s website at www.seamonkey-project.org, providing the familiar suite functionality in a remodernized application with additional features and fully up to date security.
For the few who can’t afford that, a last 1.x release is available. SeaMonkey 1.1.19 does fix a few security issues, but not all known security vulnerabilites, some of which may even be grave. Those are only fixed in the new SeaMonkey 2.0, which will continue to be maintained for quite some time and updated for any security issues as they might arise, while the team is working on evolving the well-known suite even further in future versions.
-
Recent Posts
Recent Comments
- H. on SeaMonkey 2.53.18.2 is out!
- Thorben on SeaMonkey 2.53.18.2 is out!
- xrror on SeaMonkey 2.53.18.2 is out!
- Wolpi on SeaMonkey 2.53.18.1 updates
- Augusto on Teething problems with archives
Archives
- September 2024
- July 2024
- March 2024
- January 2024
- December 2023
- November 2023
- September 2023
- August 2023
- July 2023
- March 2023
- January 2023
- December 2022
- September 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- April 2021
- March 2021
- January 2021
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- February 2020
- January 2020
- December 2019
- September 2019
- August 2019
- July 2019
- February 2019
- January 2019
- December 2018
- September 2018
- July 2018
- May 2018
- April 2018
- February 2018
- November 2017
- October 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- December 2016
- October 2016
- September 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- April 2015
- August 2014
- November 2012
- October 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- October 2011
- September 2011
- August 2011
- June 2011
- April 2011
- March 2011
- February 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- July 2009
- June 2009
- March 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- April 2006
- February 2006
- January 2006
- December 2005
- November 2005
- September 2005
Categories
Meta
Well, that answers my question about SeaMonkey 1.1 support.
I use a lot of older OSes for various reasons, and SeaMonkey 1.1 has worked very well for me all these years. Sadly 2.0 won’t work on these, so I will just have to keep using this final version then.
Also, this version has the same problem with loading HTTPS sites on Windows 95/NT 3.51 that 1.1.18 had. (There was a piece of dead code among code imported from Firefox 3.x that pointed to a 98-only function) I’ve got a hack for that.
anyway, good job SeaMonkey folks!
I want to move as much as possible of my workflow onto my new iPad next week. I do lots of editing with Seamonkey, oh no! I’m guessing my workaround will be to load pages into google docs, type lots there (mostly text without formatting), then carefully cut and paste the new text back to seamonkey files later when at home on mac. Boy would seamonkey on iPad be nice! Any chances?
I’m a mouse rather than keyboard user. Is it possible to create a desktop shortcut directly to my SeaMonkey email box?