@NewSense

He was strictly talking about installed RAM — it's that simple.

While recommending 2GB doesn't forbid running JIT on smaller systems, 1GB is a gamble based on modern web browsing demands. Average users on 1GB or less face a much higher chance of hitting memory limits with JIT enabled. If out-of-memory crashes happen, users should either turn off JIT or switch to a system with more RAM.

@ jacadcaps - now that you have released Wayfarer v11.5 with the added speed bonus of JIT, you have stated that 2GB of RAM/Memory is recommended, but just how does anyone get 2GB recognised in their system under MorphOS?

I have an iMac A1145 with 2.5GB installed (I could install more) but the most that is seen by the MorphOS system is 1.82GB, but only 1.69GB is accessible by the system under MorphOS v3.20, so why mention 2GB is recommended . . . if it is unattainable?

My G4 MacMini 1.5GHz has a 1GB memory stick installed, so would that be sufficient for the JIT to function as intended, as once it has booted there is less than 1GB of RAM available, and once it is running there is only about 850MB of RAM free, but once Wayfarer is running, then there is only about 600MB of free RAM?

@jaca:

Thanks for this! On your website the 11.3 is shown twice in the Download corner.

Wayfarer 11.4 out now and fixes a long-standing issue with videos freezing for multiple seconds.

I would love to see a summary of tips from all 76 pages of info on this thread! Post 1877 caught my eye just now as I scrolled to the latest here.... Keep up the amazing work!


Quote:


[ Edited by EVX 30.04.2026 - 17:45 ]

Quote:

Thank you Jaca! Look forward to it. Wayfarer has been running great for what I need it for...

Writing this from my very first run of Wayfarer 12 (WebKitGTK 2.52.0). Hopefully not long now before it can go public!

I analyzed the TLS handshake with Wireshark and it seems that for some reason the server doesn't seem to be happy with the TCP ACK we send to TLS 1.3 "Hello Retry Request, Change Cipher Spec" message. The message we send it fully compliant and correct.

The server acts as if it hasn't received the ACK, it thus will think we are missing some data and keeps resending the "Hello Retry Request, Change Cipher Spec" payload again with PSH|ACK. Since we from our point of view have already received the data, we consider this message a spurious retransmission and drop the data. No matter what, the server doesn't seem to receive any of our packets attempting the recovery, and the attempts eventually fail and the connection closes. This results in error 35.

There'a another site that has similar issues:
https://www.s-pankki.fi

Only TLS 1.3 connections are affected. Downgrading the connection to TLS 1.2 makes it work.

There is no obvious explanation as to why this would happen. My best guess is that there is some "anti-DDoS" filter device between the server and us. When triggered by "unusual or odd" packet patterns, it completely ceases forwarding any further data towards the server. The server gets super confused and keeps asking us to reply, but since all further communication from us is discarded by the device, the connection will eventually be torn down, and error 35 returned.

Another option would be a buggy device that has a broken TLS 1.3 implementation.

I haven't been able to confirm this or pinpoint it to specific device or equipment.

@jacadcaps,

I have tried Saturday and also yesterday to on https://www.agirc-arrco.fr/ . It is the site of a supplementary pension fund here in France. But I obtain this error ssl when loading the page.

Erreur SSL lors du chargement de agirc-arcco.fr
35:SSL connect error

I thought and expected to find in the preferences/settings to tick a case to ignore those ssl errors, like in Odyssey, but there is nothing. With some other sites I have the possibility to ignore ssl errors but not in this case.

So can you give me aqn explanation why do I obtain this ssl error ? Can you also investigate to solve this ssl error ?

Brumiga

Quote:

Thanks especially for that. Not crucial for surviving literally, but one of those little improvements that show how matured and well maintained the whole thing is. Thumbs up!

@ jacadcaps - You THE MAN !! . . . and Piru and of course the betatesters !!

Where would MorphOS be without a modern WebBrowser, that's regularly updated?

Not forgetting the Morph OS itself, supported by the Development Team, also being regularly updated.

Work on Wayfarer 12 ongoing.

Quote:

Splendid. Thanks Jaca

Wayfarer 11.2 is now out!

- Avoid opening an extra window when launched via OpenURL/commandline url
- Fixed text caret not reappearing upon reactivating the window
- Fixed enter key not scrolling contents in multiline text editing fields
- Reduced binary size by a few MB

If you've been stuck at 'You have been blocked' when trying to log in to PayPal, try changing the User Agent to Samsung Smart TV.

@primax

The player doesn't actually know what qualities are available, so that'd be hard to do.

@Jacek

As soon as a video has started playing - regardless, if it is a YouTube video or a video embedded in a website: is there any chance to get access to the quality playback option of the video (several SD, HD etc.) and put that in the Wayfarer menu just like fullscreen?

Because it is always a hussle to access any video option within the video. It does not work very well.

(@admins: if I go with Forum Index » User Forums » Applications, then 76 sites are listed for "New Modern Webkit-based Browser In Development" topic. Odd, because right now it only has 75...)

Thanks jaca!

Much yay, thanks jaca!

Wayfarer 11.1 is now out!

- Rebased to WebKitGTK 2.50.4
- Fixed fullscreen mode immediately switching back to windowed
- Disabled SVG radial gradients to improve performance

PS: and super cool: it is correctly written "Danke für ihren Beitrag"!!! :))

Quote:

It's really confusing....
Because if you log in here, it is confirmed in English (Thanks for logging in or something like that).
But if you log out, then it is confirmed in German...

And secondly: it is not possible to encode the "ü" correctly, but it does ciprectly for the "ä":
"Falls die Seite nicht automatisch neu lädt, klicken Sie bitte hier...".

??

Quote:

Yea, confirmed. This is pretty much the same on any other "mainstream" browser like Edge, Firefox or Chrome and not directly related to Wayfarer.

At least the german strings seem to be encoded in UTF8 but displayed in ISO-8859(-1), so any characters which are not part of the legacy US-ASCII character set are affected (like ä,ö,ü,ß and lots of others). If that is some limitation of the forum software and/or its encoding of HTML pages, I don't know ...

Jaca, your are a living coding machine.

Thanks!

W00t