We have deployed Midori browser 0.4.3 in "2016-02-09-raspbian-jessie.img" on RPi 2B, running kiosk mode against a single URL that refreshes every 60 seconds. We've seen non-stop operation for 30-40 days duration, CPU utilisation less than 10% and RAM utilisation around 20% (no swapping is happening)...

The beep file was converted from WAV to MP3, now at least 4 of the 5 beeps play via ADSL line, which is acceptable. Bandwidth utilisation dropped from about 80kbps to 12kbps.

I changed the following in Midori preferences:

- enabled local cache storage for HTML5
- disabled the proxy
- increased Midori's local cache from 100M to 200M

So now at least 3 of the 5 beeps would play.

When I test with Chromium 48 behind an ADSL line, I hear 4 of the 5 beeps.

I have a very peculiar situation when I use Midori browser 0.4.3 (Jessie OS) to run a website that plays a WAV file every 60 seconds. The WAV file consists of 5 beeps interspersed with short silence, total duration 3 seconds, 536kbyte file size, 1411kbps bit rate. The website is deployed on the cust...

Thank you Dougie.

After some further Google research and testing on my RPi, it appears that the hosts file is indeed being used before a nameserver in the resolv.conf file is used. Example: resolv.conf contains router IP address 192.168.1.1 Enter 11.22.33.44 as IP address of cnn.com into hosts file and do a ping. Pin...

We have an RPi running a Midori browser against a web server located on the other side of a low-bandwidth WAN in a data centre. The RPi is on 'this side of the WAN' on a subnet of 10.14.9.0/24, and the webserver is in the datacentre on 'the other side of the WAN' on an IP of 10.10.17.15. The URL in ...