I get hundreds of millions of dollars every year by legitimising surveillance capitalists and enabling them to violate your privacy by default. (I wouldn’t exist without them.) Please trust me on privacy.
Why are you all looking at me like that?
OK, OK, you can stop glaring: I’m Mozilla, y’all love me. 💕
@aral to be fair, with the money they get from google they can keep up and keep Firefox competitive, if they wouldn't accept googles money, Firefox would disappear into nothingness and then we have a chromium only browser landscape. So I consider it currently a necessary evil.
@blacklight447 @aral Imagine Debian taking money from Microsoft to make Microsoft Office the default office suite on Debian while using the money to build a privacy respecting operating system alternative to Windows 10.
This seems unthinkable to most free software people, but Firefox setting Google as the default search engine and using the money to make a privacy respecting alternative to Google Chrome attracts a lot of debate about means and ends.
@aral So if you don't like Mozilla or Google, that leaves the one major browser engine you'd approve of being Apple's WebKit? I hope you can see why I say we need a Small Tech browser engine?
@alcinnz @aral I wish more time was going into konqueror. It was what I used to use until FF came along.
So nice having your web browser also be your file manager that could also handle ftp and ssh. Plus those lovely splittable windows.
I know dolphin can handle most of that except the browsing.
Actually, all the kde stuff like kate, kwrite, dolphin w/e uses kio slaves to handle file, fish, ftp and so on.
@fitheach @alcinnz @aral 'Moving and viewing files' over multiple protocols IS doing one thing well.
Confining that use to a single protocol means needing Multiple apps; as many as one for each protocol.
Dolphin does exactly this, so you win there (no web).
I enjoyed having the other protocols there as well though. Sometimes, i still do.
It's a while since I looked at Dolphin, but ti struck me as a mighty fine file manager.
The file manager/browser mash-up: didn't it start way-back when browsers were viewing the Desktop as if it was a webpage? I certainly remember the GNOME browser doing that (Galeon?). MS Windows did that for a while, too. Horrible idea.
Gosh, it isn't that long ago that file managers added features to allow use of WebDav, FTP and SSH/SCP etc. Libraries like KIO or filesystems like FUSE or GVFS were only added ten years ago, maybe slightly more.
Viewing file contents using FMs has probably been around a bit longer, usually by calling other applications. What seems weird to me is having a FM that is also a web browser (or is it a web browser that is also a FM?).
Finding the perfect file manager is like searching for the Holy Grail; the quest is eternal, and never fulfilled.
I have tried emelfm(2), and also Gnome Commander, Tux Commander, Nautilius, ROX, and many others. All of them have nice features, but I'm always looking for more. For years now my mainstay FMs have been Thunar and MC. Pretty happy with those two, although I would like a graphical two-pane FM (I know Dolphin, but KDE...).
@fitheach "The packaged versions of KDE apps"
What does this mean, sorry? I've never run into a situation when I can't mix and match any programs written with any old graphical tool kit.
When you install, e.g. konqueror or most any apps, under distros like Fedora, Debian, Ubuntu etc. you install a package where the developers have already made decisions for you regarding settings and dependencies. Alternatively, you could install the app from source(s) and perhaps avoid some un-needed dependencies.
@fitheach Can you give me an example please? I'm still not understanding. Everything is entirely changeable in prefs wrt what happens to each filetype, which is quite extensive.
I swear i'm not being deliberately obtuse Iain - just never ran into this problem you've experience with settings.
Depends, yes, of course. Any program using external libs has depends.
The dependencies are quite often flags which you set when you compile an app. When you install a package it has been compiled already, with decisions about those flags made by the package developer.
@fitheach I'm familiar with these things, yes.
Just looking for an example of where this limited people to only being able to use other kde applications with something.
It's very early here and perhaps I'm missing the obvious.
Have a look through the KDE documentation. This page (although talking about extragear) explains the high level organisation:
This page gives the flags when building from source:
Adding or omitting some of these modules could dramatically change the nature of individual KDE apps.
This is my personal Mastodon.