Yesterday after discovering &pp=sAQA breaking by History tracking (got a custom CSS injected to make sure its distinct) I added this

    document.querySelectorAll('a[href*=\\&pp\\=]').forEach(el => {el.href = decodeURIComponent("/watch?v="+el.href.match(/v=(.*?)(&|$)/)[1])})

to my userscript injected into YT. I still need to pinpoint reliable DOMSubtreeModified event to make it work without manually reloading the page.

Edit: and just now discovered its being added server side. Fetched https://www.youtube.com/youtubei/v1/browse?key=xxx already has &pp=sAQA, makes patching even easier, just donna hijack fetch and strip them in the handler... aaand done:

    const origFetch = unsafeWindow.fetch
    unsafeWindow.fetch = async (url, init) => {
      if (url.url.startsWith('https://www.youtube.com/youtubei/v1/browse?key=')) {
        let response = await (await origFetch(url)).text()
        response = response.replace(/(\&pp\=.*?)",/g,"\",")
        return new Response(response)
      }
      else {
        return origFetch(url)
      }
    }

    window.addEventListener('DOMContentLoaded', ()=> {
      if (document.location.pathname == "/feed/subscriptions") {
        document.querySelectorAll('a[href*=\\&pp\\=]').forEach(el => {el.href = decodeURIComponent("/watch?v="+el.href.match(/v=(.*?)(&|$)/)[1])})
      }
    })

Regular expression replaces on content are very fragile. Unfortunately, browsers do not yet provide general request regulation capabilities. Until then, Transcend Consent Manager's API can solve this much more easily with a more robust request-override based approach:

    self.airgap = {
      overrides: [{
        matcher: '//www.youtube.com/',
        override(request) {
          request.urls.forEach((input, i) => {
            const url = new URL(input, location.href);
            if (url.searchParams.has('pp')) {
              url.searchParams.delete('pp');
              request.urls[i] = url.href;
            }
          });
        }
      }]
    };

Its true URLSearchParams is a proper blessed way of working with url parameters, but its just my tiny userscript working on a serialized JSON, so either I grep and be done with it, or be forced to actually parse it, traverse huge Object looking for 100 individual URL fields to modify "properly", and stringlify once again. Im good with regex thank you :)

>Transcend Consent Manager's API

what is that?

>request-override based approach

the idea is to modify those URLs before they get rendered on the page, this way they get applied :visited style in the first place.

> what is that?

A new consent management tool for website owners. We're currently in closed beta. Learn more here: https://transcend.io/blog/defeating-cookie-banners

> the idea is to modify those URLs before they get rendered on the page

These overrides are applied before the URLs are rendered on the page or trigger any requests.

>DOM nodes by directly patching the prototypes, methods, and accessors of all global element constructors and DOM tree construction utilities. We can write a patcher which overrides the constructor prototype, which allows us to check if the URL is allowed before the DOM mutation is performed.

Now I understand. Your product is aimed at corporations seeking more mature? compliance with privacy laws. Sounds like tough market.

I actually find all kinds of browser history pollution a very serious problem rendering it almost useless (only useful the way "recycle bin" is - to recover an address of that useful page you have seen yesterday but forgotten).

I wish there were browser extensions capable to smartly sanitize the history by removing duplicate URLs pointing to the same actual page visited multiple times during the day and/or by via slightly different URLs, removing the specific parameters which can be removed without changing what does the link point to, rearranging the remaining parameters alphabetically, removing GMail and alike useless URLs, also normalizing the entry titles by removing everything but the actual article title (e.g. removing website name or moving it to an uniform place - always the beginning or always the end) etc.

I like the way Vivaldi Browser presents history. So much easier to use than other browsers.

I haven't used Vivaldi before. Can you explain what is eaiser to use?

It's just organized better. There are some screenshots on the help page that show it better.

https://help.vivaldi.com/desktop/navigation/history/

I'd prefer that the browser be taken out of the equation completely.

The web browser is becoming just a shitty operating system, largely controlled by unaccountable megacorps who are primarily interested not in empowering users but in tracking them and serving them ads.

You can use curl if you don't like browsers. It just needs a lot of imagination to get an idea on how the site is supposed to look like.

Whatever, pmoriarty is right. Today a browser indeed is an operating system with its own GUI toolkit and a decentralized repository of apps (we call the web, most of the sites actually are apps today).

Perhaps if the web servers served something like QML/XAML/whatever (while other web servers serving just APIs for them to get/post the content) and there was an operating system command to run such an app by its URL, both the developers and the users might have a better experience. Or perhaps worse.

This way we might even have more than one standard competing: QML, XAML and whatever else would emerge (introducing new would be more viable) vs just HTML.

It's not as good, but the history is pretty useful: https://www.youtube.com/feed/history

That link shows empty to me, since I've never logged into YouTube, and most of the time I'm not even logged into the Google account.

(I don't know if it's still the case, but I've heard that if you log into YouTube, and Google for some reason decides your real name is not your real name, you could lose access to your whole Google account; and at least to me, the Google Talk account was more important than being able to comment on YouTube videos.)

I don't think that's been a thing for a long time.

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

Last I checked, it was impossible to create a YT/Google account without providing a (working) phone number. Which is even worse than requiring "real names" (which can at least be spoofed).

That depends. I’ve found that, while creating an account on an iOS device, providing a phone number isn’t required, but while creating an account via a desktop browser, it is.

It will probably depend on other factors as well such as IP, country, …

It was still possible as of six months or so ago, who knows what factors Google takes into account to decide whether to require a phone number or a simple email.

The absolute future of a proprietary service-specific history.

That would require to be logged in to a Google account

Does it work when a video was deleted?

how do you use the history exactly?

I inject this into YT

    // make VISITED links distinct
    //subscriptions/lists
    css += 'a#video-title {color: #167ac6!important;}';
    css += 'a:visited#video-title {color: #141761!important;}';
    //commenter channel name
    css += 'a#author-text {color: #167ac6!important;}';
    css += 'a:visited#author-text {color: #141761!important;}';
    //sidebar
    css += 'a #video-title {color: #167ac6!important;}';
    css += 'a:visited #video-title {color: #141761!important;}';
    
    css += '#content-text a, #description a {color: #167ac6!important;}';
    css += '#content-text a:visited, #description a:visited{color: #141761!important;}';

makes pretty clear which links are visited