Excellent, thanks for the hard work!

Great! Thanks jacadcaps!

Wayfarer 10.0 is now available for download. The new version comes with WebKit rebased to WebKitGTK 2.48.3 (latest stable). As always, automatic updates are recommended.

A lot of work in this release went into improving youtube support, with better auto-quality switching, built-in predefined settings and user-agents. The MediaSource player was rewritten to fix the issues that plagued it in Wayfarer 9. Additionally, Wayfarer can now all automatically redirect all YT video links into youtube-nocookie.com that gives you just the video player, with no comments, recommended and most notably no video ads.

This version also adds HTTP/3 support, contingent on soon-to-be-released openssl3.library update.

Great! Thanks jacadcaps for this new release!

Thank you very much, haven't tested it yet but as always your support for MorphOS is greatly appreciated.

Just sent you a small donation to say thanks ...

Great, Jacek! Thank you very much.
I'm so excited to see how Wayfarer performs with YouTube videos. Until now, it hasn't been much fun on my X5000. I'm looking forward to it and will report back!

w00t

Oh! Wow! YT works now a lot better.....

The openssl3.library update can be downloaded from https://www.morphos-team.net/news

Why does Wayfarer now need ICU in Progdir: again? I thought that's part of MOS-Distribution?

@Amigaharry2

Because it now needs a more recent version of ICU. 3.20 will possibly ship with 2 separate ICU installs because of that.

Ah, new version is commeing...Thank you!

10.1 is now out!

- Fixed blob:// file downloads
- Fixed a crash in CSS blending (reported on vw.pl, swisspost.ch)
- Fixed not being able to restart Wayfarer after a crash
- Improved WebKit assert logging

prosternons nous devant lui
cet hommme est un dieu
(en fait quand meme pas non plus)
merci
pas possibilité de donner un don vu mes finances mais je verrais plus tard

Is there any chance regarding Cloudfare? Or is there any workaround? (e.g. logging in via Chrome and exporting some cookies or related).

@analogkid

I've been in contact with Cloudflare about this, but they've cut it off. Not surprising given the minuscule user base. It is something they'd have to support in their fingerprinting code. This has nothing to do with whether you're logged in to a website or not.