• SeaMonkey (was Re: MailCtraft is here!)

    From Ant@3:633/10 to All on Sunday, November 15, 2026 01:39:48
    In alt.comp.os.windows-10 Jim the Geordie <jim@geordieland.co.uk> wrote:
    ...
    For me, I'd rather use SeaMonkey, since both it and TB are web browsers anyway. So, TB looks like a crippled software to me.

    How many of us would like SeaMonkey to be updated ?
    Me for one.

    Add me too. I still use it, but many web sites just don't work like http://www.thedigitalbits.com/, https://www.gocomics.com, etc. SeaMonkey
    group needs help big time like developers, QA, etc. :( FYI, https://www.seamonkey-project.org/news#2026-11-08 for v2.53.25 Beta 1
    release.

    --
    "Christ died for sins once for all, the righteous for the unrighteous, to bring you to God. He was put to death in the body but made alive by the Spirit." --1 Peter 3:18. Out(r)ages, my body, USC Trojans, etc. suck. :(
    Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
    /\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
    / /\ /\ \ Please nuke ANT if replying by e-mail.
    | |o o| |
    \ _ /
    ( )

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Nobody@3:633/10 to All on Saturday, November 14, 2026 18:48:40
    On 2026-11-14 6:39 p.m., Ant wrote:
    In alt.comp.os.windows-10 Jim the Geordie <jim@geordieland.co.uk> wrote:
    ...
    For me, I'd rather use SeaMonkey, since both it and TB are web browsers
    anyway. So, TB looks like a crippled software to me.

    How many of us would like SeaMonkey to be updated ?
    Me for one.

    Add me too. I still use it, but many web sites just don't work...

    Time to ditch the past... and move on.

    (signed) Shirley



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Saturday, November 14, 2026 23:29:17
    On Sat, 11/14/2026 8:39 PM, Ant wrote:
    In alt.comp.os.windows-10 Jim the Geordie <jim@geordieland.co.uk> wrote:
    ...
    For me, I'd rather use SeaMonkey, since both it and TB are web browsers
    anyway. So, TB looks like a crippled software to me.

    How many of us would like SeaMonkey to be updated ?
    Me for one.

    Add me too. I still use it, but many web sites just don't work like http://www.thedigitalbits.com/, https://www.gocomics.com, etc. SeaMonkey group needs help big time like developers, QA, etc. :( FYI, https://www.seamonkey-project.org/news#2026-11-08 for v2.53.25 Beta 1 release.

    Part of working on projects like that, involves not compromising
    on your principles. For example, they're not going to add Manifest V3
    to the browser.

    As a result of not adding support for things that are obnoxious,
    of course the experience will be less than optimal.

    I'm just surprised that the various entities on the 'net, are
    so easily bought off. All the text sites with "your browser is
    too weird to display text" feedback. Which is of course, bullshit,
    as the things like Discord don't really need a three-ring-circus
    to work. That's the sad part about the payload from web sites like
    that, they're making claims about your browser, that are not even
    remotely reasonable claims.

    And when you see mention of the word "Cookies", it's got nothing
    to do with cookies. You can stop verifying that setting. What
    they mean is, they want to use your DOM storage, they want the
    Manifest V3, to store their tracking information for later. The
    reason they don't use a cookie, is the user can erase a cookie
    and so they're seeking a storage place you're less likely to be cleaning
    or filtering. This behavior is variously called "supercookies", due
    to its distributed nature.

    Paul



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From J. P. Gilliver@3:633/10 to All on Sunday, November 15, 2026 12:40:50
    On 2026/11/15 4:29:17, Paul wrote:
    []
    And when you see mention of the word "Cookies", it's got nothing
    to do with cookies. You can stop verifying that setting. What
    they mean is, they want to use your DOM storage, they want the
    Manifest V3, to store their tracking information for later. The
    reason they don't use a cookie, is the user can erase a cookie
    and so they're seeking a storage place you're less likely to be cleaning
    or filtering. This behavior is variously called "supercookies", due
    to its distributed nature.

    Paul


    When you say "less likely", do you mean it's still possible? If so, how
    does one go about it - or even just see what is there? [Please only
    answer if they're in terms a bear of little brain can understand :-) !]
    --
    J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

    As we journey through life, discarding baggage along the way, we should
    keep an iron grip, to the very end, on the capacity for silliness. It
    preserves the soul from desiccation. - Humphrey Lyttelton quoted by
    Barry Cryer in Radio Times 10-16 November 2012

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Sunday, November 15, 2026 08:53:51
    On Sun, 11/15/2026 7:40 AM, J. P. Gilliver wrote:
    On 2026/11/15 4:29:17, Paul wrote:
    []
    And when you see mention of the word "Cookies", it's got nothing
    to do with cookies. You can stop verifying that setting. What
    they mean is, they want to use your DOM storage, they want the
    Manifest V3, to store their tracking information for later. The
    reason they don't use a cookie, is the user can erase a cookie
    and so they're seeking a storage place you're less likely to be cleaning
    or filtering. This behavior is variously called "supercookies", due
    to its distributed nature.

    Paul


    When you say "less likely", do you mean it's still possible? If so, how
    does one go about it - or even just see what is there? [Please only
    answer if they're in terms a bear of little brain can understand :-) !]


    A browser can have a feature for handling storage. But this article is old.

    https://www.imore.com/firefox-rolls-out-new-tool-can-delete-all-your-cookies

    Products that work externally on a browser, you don't know how
    thorough they are. They have to be updated regularly,
    because browser design works for the weasels, not for us,
    and any cleaner product has to examine the latest browser
    versions for "moar databases inside".

    https://en.wikipedia.org/wiki/BleachBit

    https://www.bleachbit.org/download/windows

    https://download.bleachbit.org/get/BleachBit-6.0.6-portable.zip

    BleachBit-6.0.6-portable.zip\BleachBit-Portable\share\cleaners\

    firefox.xml 8,653 bytes

    <description>Delete LocalStorage, IndexedDB, and other data stored by websites</description>
    <action command="delete" search="walk.all" path="$$profile$$/storage/default/http*"/>
    <action command="delete" search="glob" path="$$profile$$/storage/default/http*"/>
    <action command="delete" search="file" path="$$profile$$/webappsstore.sqlite"/>
    <action command="delete" search="file" path="$$profile$$/storage.sqlite"/>

    The clauses I'm showing there, those are the ones I use. I would have to re-scan that file and see if there are any lines in there which could be
    abused for tracking and I should be including them.

    Not all the entries in firefox.xml are regarding tracking. Some
    of the things being cleaned, are "general hygiene". Accessing
    something like history, some sites were using in-line tracking, where
    a number in the URL corresponded to your identifier. And then a series
    of these stored in the history, might be accessed and "detected via
    a timing attack". Some of these techniques were like machine gun fire,
    and quite crude (the user would notice). The timing attack was
    being used to see if a thing was inside the history cache (quick response)
    or was not there (slow response). Mozilla used to counter these tricks,
    by adding a random delay to some activities to de-correlate the behavior
    of the tool.

    Sami had a website, which defined supercookies and he gave info on
    the ones he knew of and understood. There was a test program that would
    assert a supercookie, you were then supposed to go away and use your
    BleachBit Firefox-specific script, then come back and visit the Sami site again,
    and if the cookie value was still visible (say it was 123), if the screen displayed that value, your cleaner wasn't good enough. But that dev had
    no intention of keeping the site content current, he was up-front about it,
    and so today we don't really have a good way of checking how effective
    a tool like current BleachBit really is. To find the supercooking,
    the web page has a "sniffing recipe" and a list of items it will be
    checking. As devs discover more of these, they add them to the file
    on the web page that does the sniffing. That's why research done ten
    years ago, would not be good enough to cover absolutely everything today.

    Still, that's about the limit of my skills at this :-) I'm not sufficiently paranoid to spend any more time on it than that.

    Paul


    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)