Quote:

Great :) thanks.

Quote:

Wow!
I'm glad you're still developing your software.

:) :) :)

Work on Wayfarer 11 progressing...

@ jacadcaps - It would be even better if there was a way to "interrupt" break-into a loading webpage and just close it, if required, like any page that we come across with "Cloudflare" control, as we won't be able to access such a content controlled webpage anyway.
Having to wait until a lengthy JavaScript heavy webpage has loaded, can also seem to be toooo long quite often anyway to just be able to close it!

Normally it'll eventually let you close the tab - that's what happens with osnews for example.

Irrespective of the specific example, my main question was what I can do if Wayfarer hangs because the content is too complex, etc.?

Can I just wait and see or can I interrupt it somehow?

@Primax

It's the donation box (ha ha). Once you block ko-fi.com the site is super-fast. Feel free to complain to os-news' admins. The iframe spikes the CPU on Safari/macOS as well.

@Primax Being incompatible with newer web standards (ECMAScript 6, for example) has a few benefits. The biggest one is that most common tracking solutions will not work, thus do not permnanently run in the background and monitor your mouse movements, etc.

While OSNews advertise at the top that they are no longer running ads, there are still currently 9 tracking scripts active on this website.

Aside from this, you might be blocking ads and trackers in OWB but not Wayfarer. Put differently, different browser configurations could play an additional role as well.

A question:

Do you also have websites where Wayfarer runs at full capacity? I have the traffic indicator at the top of the menu, and it is completely maxed out: no more bars, just blue.

This happens more often lately. This is an example:

https://www.osnews.com/story/143070/amibrowser-the-chromium-engine-running-on-a-linux-host-talking-to-a-68k-amiga-application/

By the way, no problems if I ran that with OWB.

My question: Is this due to my X5000? Or is it the same for you? If so, can someone explain why?
And above all: what can I do in such a case? Wayfarer then no longer responds.

Thanks!

@jacad: Could now test Amazon again here in Vienna: Works now! I've done absolutely nothing on installation - just booted and it runs...! Seems really to be a temporare Provider-Problem (again...!).

Quote:

Thanks

If one wants to view Adobe Flash content, then download the .swf file and play it locally on your system. AmigaOS4 has Gnash, but I don't have AmigaOS4.

I would recommend Flash Player 1.4/1.6 by Maxim Ilyn from 2008, but I've tried the program and it is less than ideal. You don't get play/pause/rewind or any controls like that, the .swf just autoplays. I tested two or three .swf files when I tried Maxim's program, however long ago that was, and, if I recall correctly, autoloop is not even an option. Audio continues playing, but the video stops and doesn't loop, so that's a bummer.

There's one other option that I have yet to try, and that's swfplayer 1.4b6, hosted on Aminet. It's from 2005 and compiled for 68k AmigaOS3, so it should work fine on MorphOS, but the developer prefaces that the software is in beta, so it has kinks. I do not know if using it is a worse experience than using the newer Flash Player 1.4/1.6 by Maxim Ilyn.

@ jacadcaps - I thought you'd say something like that in response to my comment.

However, thanks for taking the time to reply - a lot easier, and less time consuming than converting Ruffle !!

Quote:

No.

Even if I somehow managed to write all the necessary bits to make Web Assembly work (all JIT stages, etc), Ruffle would still assume it's running on little endian. You'd have to fix Ruffle itself and compile it to WebAsm. This is all doable, of course, with a team of people that have infinite spare time.

@Amigaharry2

Could also be some local (on-disk) cache issue... But it's normal that a different network connection may serve you a different website, essentially, since it'd be coming from a different CDN.

Quote:

Very interessting! Tested it at home with A1-Provider: Does not work!
Tested ist now in second location with SPUSU-Provider: works as you discribed. (same Powerbook)
crazy! Maybe a temporal issue of A1 (had such things in the past). Will test it on monday, when I'm back!

> I always thought that any code that is little endian,
> can be converted to big-endian

Sure, but someone would have to undertake that task. As a side note, the better approach than creating another, big-endian variant of original little-endian code is to rewrite it into endian-agnostic code to ease maintenance.

@roschmyr: Here, too. Amazon.de works as expected.

[ Edited by analogkid 13.08.2025 - 09:00 ]

Quote:

hm, https://www.amazon.de works as usual here

Unfortunately some URLs does'nt work any more as expected. Amazon shows only unformatted page and is useless.
(https://www.amazon.de)
CPU-load is most time at 100%
With V10.4 it's working....

Quote:I always thought that any code that is little endian, can be converted to big-endian - even if it was never intended to be used on big-endian systems in the first place? And ... vice-versa!

Or is there some hardware "trick" that it accomplishes on little-endian systems that it just can't on big-endian CPUs, even if the code was converted to big-endian code?

10.5 is now out. WebKit was rebased to latest stable WebKitGTK 2.48.5.

@Primax

I haven't done anything :P

@NewSense

Ruffle relies on little-endian-only tech.

@Jacek

With the latest update, Mastodon menus are working fine again. Thanks!