On Wed, Nov 16, 2016 at 2:10 AM, Walter Dnes <waltd...@waltdnes.org> wrote: > On Mon, Nov 14, 2016 at 11:52:50PM +0000, Jorge Almeida wrote >
> The current Pale Moon requires glib-dbus. I do my own custom builds > of Pale Moon for my personal use without dbus. I also have an ancient > 32-bit-only Atom netbook. dbus is required for Necko-Wifi and Wakelock > in Pale Moon, and presumably also in Firefox... > > Necko-Wifi - allows improved geo-location if you have wifi, which most > PCs have, even newer desktops. It works by scanning SSIDs in your > vicinity and comparing against a master global database. The local data > has to be sent off to a master database (e.g. Google) for the comparison. > > Wakelock - is a generic API for grabbing a resource and not letting go > of it... https://www.w3.org/TR/wake-lock-use-cases/ It's mostly used > in mobile apps, but on the desktop it's used to disable the screensaver > while a long video is playing. > This is the kind of information that it would be useful to have in a central place (WiKi), at least for USE variables that are bound to have a global impact on the system. > If you can do without Necko-Wifi and Wakelock, you don't need dbus. > Let me know off-list if you need any help custom-building Pale Moon. > You can also join the Pale Moon web forum https://forum.palemoon.org/ > The linux section is https://forum.palemoon.org/viewforum.php?f=37 > Thanks. I tried Pale Moon once, but I think it had the same problem as Firefox regarding cpu use, namely with youtube. > -- > I don't run "desktop environments"; I run useful applications +1 Cheers Jorge >
