Polyfill: What's all this, then?

[NotHereToPlayGames]

I would also claim (with no data to back it up, I do admit) that hackers and cybercriminals have ZERO interest in creating trojans and malware targeting XP.

Why target x number of computers on XP when you can target y number of computers on 10 or 11?

y > x

 

Guess I also kinda see it this way.  Hackers and cybercriminals aren't interested in breaking into my XP anyway.

Yahoo data breach of 2017 - they hacked into Yahoo servers, not personal computers of the 3 billion accounts that were effected.

LinkedIn data breach of 2021 - 700 million users effected, 700 million personal computers were not hacked into.

Facebook data breach of 2019 - 533 million users effected (is it effected or affected?)

Yahoo data breach of 2014 - 500 million users effected  (and Yahoo clearly didn't learn anything because see above's 2017 data breach)

Twitter data breach of 2018 - 330 million users effected

LinkedIn data breach of 2012 - 165 million users  (and again they didn't learn anything because see above's 2021 data breach)

Equifax data breach of 2017 - 148 million users effected

eBay data breach of 2014 - 145 million users effected

Capital One

Target

Sears

JC Penney

Facebook data breach of 2018 - 87 million users effected  (then 533 million a year later in above's 2019 data breach)

Anthem

Dropbox

Tumblr

Uber

Home Depot

Marriot

 

Those seem to be the bigger ones.

I don't deny that home computers get hacked into, but I think "click-happy" consumers installed the trojans themselves because they're not really "computer people", they just want to play solitaire and download screen savers.

Edited April 11, 2022 by NotHereToPlayGames

[NotHereToPlayGames]

On 4/7/2022 at 4:52 PM, UCyborg said:

Tricks:

palefill with the following rule added to lib/main.js:

{
  selector: ["docs.microsoft.com"],
  fix: ["std-customElements", "std-PerformanceObserver", "std-queueMicrotask"]
}

@UCyborg - I am curious to know if your Microsoft.com example still works if your "fix" line is changed to fix: ["std-customElements"]

I am curious because the Babel-translated script for your example contains 7 hits for "customElements" but zero hits for "PerformanceObserver" and zero hits for "queueMicrotask".

[UCyborg]

It seemed to work, though it showed browser unsupported banner then.

[NotHereToPlayGames]

Anyone know of a way to polyfill attribution-reporting ?

This is the first encounter I have stumbled into where "new" browsers work but that Ungoogled Chromium v114 is "too old".

The web site is the USPS's login (do not need an account to test)  --  https://reg.usps.com/login?app=HOLDMAIL&appURL=https%3A%2F%2Fholdmail.usps.com%2Fholdmail%2F

Just type in a RANDOM username and a RANDOM password and you'll see the "unrecognized feature: attribution-reporting" in the error console.

[UCyborg]

Just why?

Edited June 25, 2024 by UCyborg

[NotHereToPlayGames]

If I understand the "why", agreed!  I'm not trying to reproduce the API, I'm trying to get v114 to "pass" the TEST for this useless function so that I can log in.  

This is one of those APIs that will keep me on v114 for "as long as possible"  --  "privacy rights" really are dwingling FAST with each and every update.

This may require a Proxomitron fix.  

[NotHereToPlayGames]

Haven't looket yet (liking Official Ungoogled v114 too much!), but this could be the nail in the coffin for my Ungoogled v114  

I can (?) easily pull this API out of 360Chrome v22 (Chrome v119) and "ungoogle" it, but I'm not really sure all of the time and effort to release another 360Chrome version is where I want to be  

[UCyborg]

So Firefox users are locked out completely? They shouldn't be using this in production.

[66cats]

58 minutes ago, NotHereToPlayGames said:

(do not need an account to test)  --  https://reg.usps.com/login?app=HOLDMAIL&appURL=https%3A%2F%2Fholdmail.usps.com%2Fholdmail%2F

Just tested with with some old 360Chrome 13.5, seems to work (gives me "We do not recognize your username and/or password. Please try again.").

Edited June 25, 2024 by 66cats

[NotHereToPlayGames]

Interesting!  Correct, I can log in using 360Chrome v13.5.  

Hmmm...

[NotHereToPlayGames]

I guess I should have started there, lol.  

All it took for a v114 successful login was to fake an older Chromium user agent or to fake a Firefox user agent.

Seems they only have certain versions of Chromium-based user agents being served that attribution-reporting JUNK.

I didn't spend time to track down exactly which ones, but I kind of have to suspect v100 and higher.

At any rate, I can stick with my beloved v114 for longer, lol.

[NotHereToPlayGames]

This whole dog-chasing-tail aspect of browsers updating five times per WEEK (slight exaggeration) is really getting OLD !!!

In the span of just a few days, I now have two web sites that no longer work in v114.

The USPS as cited above.

And now, like @Mathwiz at Chase, my Citi no longer works.  

Haven't tracked it down yet, only that v123 does work and v114 does not.

And not as simple as a user agent switch this time.  

But both USPS and Citi both continue to work in 360Chrome v13.5.

Which is fine and dandy, but my list of sites that do NOT work in 360Chrome v13.5 was too large and that was what prompted the move to v114 in the first place.

[UCyborg]

You can always go with standard Google Chrome with auto-update, then it will just work.

[NotHereToPlayGames]

I "could".  But I won't, lol.  Ungoogled is a MUST for me.  

So far, I've been testing all of the websites that no longer work in 360Chrome v13.5 (v86) and the websites that no longer work in Ungoogled v114 and so far they all work in Ungoogled v94.

I may be okay just running v94 as my default-catch-all.

Technically, the "only" reason I jumped from v86 all the way up to v114 was based on "Speedometer 2.1" scores (I know, not everbody is a fan of "quantifiable measurements").

At the time, Official Ungoogled was way up in the 120s or so, forget and impossible to "keep up" with their d#mn upgrade pace!

v114 simply scored the best and I've actually yet to see anything score higher on both my two computers running Win10 here at home and on my desk plus lab Win10s at work.

But that "speed" seems to come with some features that USPS and Citi are both now starting to implement.

I guess at least this time it wasn't the water bill.  LOL

[D.Draker]

On 6/25/2024 at 9:46 PM, NotHereToPlayGames said:

Anyone know of a way to polyfill attribution-reporting ?

This is the first encounter I have stumbled into where "new" browsers work but that Ungoogled Chromium v114 is "too old".

The web site is the USPS's login (do not need an account to test)  --  https://reg.usps.com/login?app=HOLDMAIL&appURL=https%3A%2F%2Fholdmail.usps.com%2Fholdmail%2F

Just type in a RANDOM username and a RANDOM password and you'll see the "unrecognized feature: attribution-reporting" in the error console.

Something's wrong with your Ungoogled. Probably got it from an un-official sources, like Russian repacks? The site works with a random version of Ungoogled 110, which is the bare minimum, the lowest requirement for most sites nowadays.