00:00:18 <a-865> no audio today in SM or Chromium :(
00:00:57 <a-865> forgot I pulled the pin jack :p
00:01:17 <nsITobin> closed captions
00:01:19 <nsITobin> ?
00:01:27 <nsITobin> well badly done subtitles
00:01:37 <nsITobin> closed captions have a standard they have to adhear to
00:01:46 <nsITobin> like being somewhere close to correct and .. sensical
00:02:07 <nsITobin> deff not something for the likes of the internet
10:01:53 <blockhead> is it just me or is gmail now refusing when one uses seamonkey?
10:04:02 <frg_Away> my tst mail account still works. If webmail it is probably a different case. Never tried.
10:24:12 <a-865> blockhead: last month I had to change to using 0Auth2 to use pop.gmail.com any more to both fetch and send.
11:19:37 <blockhead> so ... that's "yes"?
11:38:34 <a-865> it was until I changed
11:40:00 <a-865> https://www.os2world.com/forum/index.php?topic=3079.0
11:45:15 <blockhead> a-865: thank you.  i'm reading it now
11:47:27 <frg_Away> 2.42 is too old for proper oauth2 support. Basically you are on your own with this version.  The workaroiunds should not be needed with latest 2.53 but with google you never know. As with ms best to use a provider who not uses oath2. This s*cks and is basically a vendor lockin. Yes I know. All about security....
12:02:36 <a-865> blockhead: I don't think I actually needed that page's instruction. IIRC, I simply looked in settings until I found 0Auth2 and selected it for both pop and smtp.
12:03:36 <a-865> I only use gmail for a minimally used secondary account.
12:18:29 <blockhead> i'd never heard of 0auth2 until today so this is enlightening
12:19:06 * blockhead only uses google for real life things, things that need an email
12:19:30 <blockhead> s/google/gmail/