Re: constipated email on occasion

[Daniel]

Ed Mullen wrote on 20/12/2018 5:21 AM:

Daniel wrote:
Just occured to me ... most of my time on-line, I am connected to news 
servers (either this moz one or UseNet). Does SM still check my ISP 
provided POP3 mail account even though I'm connected to a News Server 
somewhere??


Yes


I thought this would be the case but thanks for confirming, Ed. ;-)

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Frank-Rainer Grahl]

webp and av1 wouldn't be a problem. Can be backported even to 2.53 which is 
already beyond ESR60 in some places (TLS 1.3 and a few smaller things). WebVR 
is something we might talk again about in 10 years. Webrender is still work in 
progress and will probably crash more than work with older drivers. ymmv.


What is a problem are css and new real web standards.

FRG

WaltS48 wrote:

On 12/19/18 12:22 PM, Ray_Net wrote:

Ant wrote on 19-12-18 02:13:

https://blog.seamonkey-project.org/2018/12/19/updating-everyone/


IMHO It looks like that it is the end of life of SeaMonkey.

I think that I have understood that SeaMonkey will never use web extensions  
...


I hope that I am wrong...


Forget web extensions.

Will SeaMonkey work with new web technologies like WebP images.



The AV1 video codec.

 



WebVR, WebRender and who knows what else.

They are already behind on getting a release based on Fx 60ESR out which 
doesn't support WebP, and 52ESR was EOL in September of this year.


Thanks for the update ewong.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Navigator address bar: copying URLs with spaces

[mozilla-lists . mbourne]

Paul B. Gallagher wrote:

mozilla-lists.mbou...@spamgourmet.com wrote:


Paul B. Gallagher wrote:


So my question is, why do you need the display to be garbled instead 
of easily readable? Do you really want to try to parse 
 manually 
instead of letting the program do it?


Depends what you want to do with it. If you need to insert that text 
somewhere which expects a proper URL, you need the percent encoding. 


Depends on your definition of "proper URL." Most modern programs 
(including SeaMonkey) can handle non-ASCII URLs just fine, but most 
older ones require percent encoding. I still make a habit of enclosing 
URLs in angle brackets because there's a large installed base of older 
programs that will misinterpret spaces (and a few other things) as "end 
of URL." Percent encoding prevents that, of course.


By "proper URL" I mean one which conforms to the specification of a URL 
(or rather a URI to be strict) - RFC 3986. Many modern applications 
display percent-encoded sequences in the URL as the corresponding 
characters, and perform the reverse conversion on text entered by the 
user - but those representations are not really URLs.


 is a URL.

 is not a URL - it's what you get by 
replacing the percent-encoded sequences from the above URL with the 
characters represented by the corresponding UTF-8 sequences. It may look 
similar to a URL, and SeaMonkey (and may other applications) may display 
it, allow you to enter it, and handle converting it into 
 where an 
actual URL is needed, but it's not a URL.


One day, none of this will matter because all software everywhere will 
use the full Unicode character set and human-readable IRIs will be the 
norm. For now, workarounds abound. ;-\


As far as I can tell, IRIs (RFC 3987) still require spaces to be 
percent-encoded as %20, but they do at least allow things like 
 without percent-encoding the 
non-ASCII characters.


Also as far as I can tell, IRIs are not used by current versions of HTTP 
(not even HTTP 2), which are still defined in terms of URIs. That 
doesn't prohibit web browsers from displaying things like 
 as an address and handling the 
conversions - but for presenting that address to other applications of 
unknown capabilities (whether that's copy/paste or inserting X's primary 
selection) I'd expect it to give the actual URI (or part of the URI if 
only part of the address is copied/selected).


--
Mark.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Steve Dunn]

On 2018-12-18 20:13, Ant wrote:

https://blog.seamonkey-project.org/2018/12/19/updating-everyone/


	Thank you to everyone who has been working on this project.  I 
understand that it's a huge task and the pay sucks :-) and I really do 
appreciate it.


	For what it's worth, here's my opinion on what I want to see in future 
Seamonkey, which may or may not be similar to anyone else's.  Executive 
summary:  my priorities for what I'd like to see in future Seamonkey 
versions are #1 support for non-obsolete extensions and #2 performance.


	Background:  Seamonkey is my default browser largely because I used 
Netscape, which morphed into Mozilla, which morphed into Seamonkey.  On 
my home computer, I also use it for personal email.  I also use Firefox 
and am quite happy with it; I just don't particularly want to have to 
switch (nor do I particularly want to have to switch my mail to 
Thunderbird), especially since I expect there would be quite a bit of 
the years worth of configuration (of the browser and of extensions) that 
might have to be redone by hand.


	The biggest thing I want Seamonkey to do is to support modern add-ons. 
None of the Seamonkey extensions I use have had updates in over a year; 
meanwhile, their Firefox versions continue to be developed.  So at some 
point, for me, Seamonkey becomes unusable as my main browser if things 
like ad blocking and HTTPS Everywhere are years out of date.


	#2 is performance.  I use both Seamonkey and Firefox on two different 
computers, and on both, Firefox performs better - sometimes dramatically 
so.  And any time Seamonkey is sluggish, the CPU utilization tells me 
it's largely running on one core only (e.g. it's eating about 25% of CPU 
time on a four-core computer), which usually isn't the case in Firefox. 
So I guess we need Quantum, and yes, I understand that's an enormous 
thing to port, but the farther Seamonkey falls behind other browsers in 
performance, the less useful it is.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[WaltS48]

On 12/19/18 12:22 PM, Ray_Net wrote:

Ant wrote on 19-12-18 02:13:

https://blog.seamonkey-project.org/2018/12/19/updating-everyone/


IMHO It looks like that it is the end of life of SeaMonkey.

I think that I have understood that SeaMonkey will never use web 
extensions  ...


I hope that I am wrong...


Forget web extensions.

Will SeaMonkey work with new web technologies like WebP images.



The AV1 video codec.



WebVR, WebRender and who knows what else.

They are already behind on getting a release based on Fx 60ESR out which 
doesn't support WebP, and 52ESR was EOL in September of this year.


Thanks for the update ewong.

--
OS: Ubuntu Linux 18.04LTS - Gnome Desktop
https://www.thunderbird.net/en-US/get-involved/

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Frank-Rainer Grahl]

This is not true. 2.57 based on ESR60 will either support them or not appear 
at all. It will support classic extensions too but because of removals from 
Gecko a lot will need to be adapted. Same for TB 60 right now.


After 2.57 it is all in the air. We could follow Firefox and become a second 
rate Chrome clone like them or fork and probably die. Or do both if no new 
devs appear because even option 1 needs extensive changes.


FRG


Ray_Net wrote:

Ant wrote on 19-12-18 02:13:

https://blog.seamonkey-project.org/2018/12/19/updating-everyone/


IMHO It looks like that it is the end of life of SeaMonkey.

I think that I have understood that SeaMonkey will never use web extensions  ...

I hope that I am wrong...

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: constipated email on occasion

[Ed Mullen]

Daniel wrote:
Just occured to me ... most of my time on-line, I am connected to news 
servers (either this moz one or UseNet). Does SM still check my ISP 
provided POP3 mail account even though I'm connected to a News Server 
somewhere??




Yes

--
Ed Mullen
https://edmullen.net/
Deja Coo: Not that damned pigeon again!

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Ray_Net]

Ant wrote on 19-12-18 02:13:

https://blog.seamonkey-project.org/2018/12/19/updating-everyone/


IMHO It looks like that it is the end of life of SeaMonkey.

I think that I have understood that SeaMonkey will never use web 
extensions  ...


I hope that I am wrong...
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[David E. Ross]

On 12/19/2018 4:44 AM, Jonathan Wilson wrote:
> I for one intend to continue using Sea Monkey as long as it remains 
> possible to do so.
> 
> If I wasn't busy with a billion other things, I would even find a way to 
> contribute to the project somehow and make good use of my C++ skills.
> 

I will remain with SeaMonkey as long as all of the 25 .xpi extensions I
have still work.

-- 
David E. Ross


President Trump still insists that Mexico will eventually pay for
his border wall.  If he really believes that, why does he not pay
for it out of his personal billions of dollars and then personally
collect from Mexico?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Jonathan Wilson]

I for one intend to continue using Sea Monkey as long as it remains 
possible to do so.


If I wasn't busy with a billion other things, I would even find a way to 
contribute to the project somehow and make good use of my C++ skills.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Daniel]

Edmund Wong wrote on 19/12/2018 7:37 PM:

Daniel wrote:

Ant wrote on 19/12/2018 12:13 PM:

https://blog.seamonkey-project.org/2018/12/19/updating-everyone/


Thanks for the link, Ant.

And EWong and Co, Thank you, Thank you, Thank you for all your past
efforts.

As Alex said on the blog ...
Quote
I keep hope for this project, and trust the SeaMonkey team to find a
good way to continue it despite the many problems.
It’s hard nowadays for you all, and I’m sad that I don’t have the skills
to help you.

If it’s necessary to keep SeaMonkey alive, take your time.
Hang in there…
End Quote

My *only* complaint about SM is with the ever increasing sub-version
numbers, .48, .49, .53, .57, etc!! Can I suggest, if you do go with the


To be honest, I"m also tired of the increasing version numbers.  It's
silly and it's a relic from the rapid train release days.

I've always preferred the ol'  small # increments.  i.e. 2.1a1, 2.1b1
2.1rc1, and finally 2.1 :)

Unfortunately, we can't change it to, say 3.x as it represents something
new and improved.  Of course, we can always change how we represent
versions.  But that's for another discussion.

Best Regards,

Edmund

So the change to quantum, or whatever, would not "represent something 
new and improved"??


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Luis Carlos González Moráles]

   

Edmund Wong wrote:
> Daniel wrote:
>> Ant wrote on 19/12/2018 12:13 PM:
>>> https://blog.seamonkey-project.org/2018/12/19/updating-everyone/
>> Thanks for the link, Ant.
>>
>> And EWong and Co, Thank you, Thank you, Thank you for all your past
>> efforts.
>>
>> As Alex said on the blog ...
>> Quote
>> I keep hope for this project, and trust the SeaMonkey team to find a
>> good way to continue it despite the many problems.
>> It’s hard nowadays for you all, and I’m sad that I don’t have the skills
>> to help you.
>>
>> If it’s necessary to keep SeaMonkey alive, take your time.
>> Hang in there…
>> End Quote
>>
>> My *only* complaint about SM is with the ever increasing sub-version
>> numbers, .48, .49, .53, .57, etc!! Can I suggest, if you do go with the
> To be honest, I"m also tired of the increasing version numbers.  It's
> silly and it's a relic from the rapid train release days.
>
> I've always preferred the ol'  small # increments.  i.e. 2.1a1, 2.1b1
> 2.1rc1, and finally 2.1 :)
>
> Unfortunately, we can't change it to, say 3.x as it represents something
> new and improved.  Of course, we can always change how we represent
> versions.  But that's for another discussion.
> Was going to say the same!
I, as an SM end user, don't like the version numbering scheme. Perhaps
the new version with the new engine (if it's possible to create) shall
be version 3.0, then comes bug fixing versions (3.0.1, 3.0.2, etc), as
was 9 or so years ago.
I really miss you Sea Monkey, you're really my savior.

> ___
> support-seamonkey mailing list
> support-seamonkey@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-seamonkey

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Edmund Wong]

Daniel wrote:
> Ant wrote on 19/12/2018 12:13 PM:
>> https://blog.seamonkey-project.org/2018/12/19/updating-everyone/
> 
> Thanks for the link, Ant.
> 
> And EWong and Co, Thank you, Thank you, Thank you for all your past
> efforts.
> 
> As Alex said on the blog ...
> Quote
> I keep hope for this project, and trust the SeaMonkey team to find a
> good way to continue it despite the many problems.
> It’s hard nowadays for you all, and I’m sad that I don’t have the skills
> to help you.
> 
> If it’s necessary to keep SeaMonkey alive, take your time.
> Hang in there…
> End Quote
> 
> My *only* complaint about SM is with the ever increasing sub-version
> numbers, .48, .49, .53, .57, etc!! Can I suggest, if you do go with the

To be honest, I"m also tired of the increasing version numbers.  It's
silly and it's a relic from the rapid train release days.

I've always preferred the ol'  small # increments.  i.e. 2.1a1, 2.1b1
2.1rc1, and finally 2.1 :)

Unfortunately, we can't change it to, say 3.x as it represents something
new and improved.  Of course, we can always change how we represent
versions.  But that's for another discussion.

Best Regards,

Edmund
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey