True. Even if the backend for any application is open sourced, end users can never make sure that the same code is actually running on the servers. The rule of thumb is: If the client sends some info to the servers, that info should be considered leaked by privacy standards no matter if the server's code is open source or not. Focus on the client and make sure it isn't sending anything that you don't want it to be sending.
There was a project where I was forced to use dropbox to share files. I set up a separate PC for the shared files because the closed source client had too many file access permissions.
And: FOSS clients do way less talking with the servers than a default application would. I need to hotspot my phone with my laptop a lot when I'm a work, and switching to FOSS clients more than halved the data I was using, meaning I can hotspot my laptop for cheaper :)
An open source front end app for a proprietary service is like an open source browser visiting a commercial site, you can know what the application/browse can do on your system. This is especially important when unlike phones, there's no standard sandbox for desktop applications.
1:50 What an open-source client brings is a confirmation or usefulness that there aren't any hidden shenanigans in the client collecting more information than it should (E.g. discord collecting what programs are running in the computer and sending that to their servers)
Obvious security flaw aside, the reason for that is to tell your friends what games you're playing. So it isn't unwarranted, at least, but I see where you're coming from.
In a similar vein, Caprine is a FOSS client for facebook messenger that I really like. Yeah, obviously everything you say is being reported to Facebook, but it cuts down the amount of thiings that are getting reported, and minimises the amount of damage they *can* cause with the permissions you give it.
Hey, DT, thanks for the shout out! What happened is, that the day I finished editing my tier list video, Nick from the Linux Experiment updated his tier list :D It didn't stop me making the video though, I agree with your take on the issue of having multiple creators tackle the same topic. It is fun!
I learned Linux by fixing things i broke. the arch wiki taught me most of what i know.i ran arch for five years and learned a lot so i thank the arch community. all you have to do is RTFM. i still use it even though i'm on LMDE 5. excellent video as usual...keep up gods work.
start by reading the friendly man pages, formulate 'intelligent' questions then turn to the community... reading the man page is ABSOLUTELY NOT all you have to do... although it is a good starting point.
Learning to use something that you enjoy is the best way to learn it. If you love the piano, you sit and tinker with it and you learn the notes and eventually you become pretty decent at playing it. Same with computer software. Before I switched to Linux full time, I was using Adobe Photoshop and Lightroom daily (used to shoot portraits and weddings for a living). I didn't take any classes on how to use those but I became pretty proficient at them. You just need to take your time and learn as you go. That's really the only way to learn how to do something you're interested in without shelling out thousands of dollars just to learn it.
@@marsdrums6298 Exactly. And a class can only teach you so much. You really get a sense of the command line and how Linux works when you use it full time and have to figure things out on your own.
I have to dissagre with the fact that open source client isn't usefull because the server stay closed source. It's still usefull because of the fact that you can audit the data sent to the closed source server
No, that's not true. Just because something is closed source doesn't mean you can't audit its data - that would depend on the data format, APIs, etc. etc. Likewise, just because something is open source doesn't mean you can audit its data - computing in the 21st century is all about encrypted connections and if you don't have the encryption keys for data on an encrypted link, then there's no way you can audit the content.
Linux Package install search with fzf in terminal: apt-cache search '' | sort | cut --delimiter ' ' --fields 1 | fzf --multi --cycle --reverse --preview 'apt-cache show {1}' | xargs -r sudo apt install -y This command allows you to search for packages and by just pressing enter the packages are installed with no major problems. The fzf preview window shows all available packages & also the amount. Thanks for the amazing content.
Yes multiple linux toobers covering the same topics from their own perspective is useful. It might even get me to watch a video on a channel I wouldn't otherwise watch. Oh and please do narrate a documentary, your southern twang is glorious.
the client pretty much handles what you send over a protocol/server, so an open client would absolutely make the difference for discord, because ideally you would control what kind of data the "discord service" is fetching from you.
I think we prefer open source frontend for proprietary services is we believe because it is open source, it will help us control the amount of data going to the service.
Related to the open source frontend, there is still value to that! With a proprietary frontend, the frontend is running on the machine and could do anything. With an open source frontend and a proprietary backend, while nobody knows what happens with the data in the backend, you can at least validate that only the data you choose to send is going to the proprietary backend. A proprietary frontend can send all kinds of shady things in the telemetry, which can be avoided when using an open source client.
Snap apps have saved me a lot of trouble getting functional versions to run on my computers and they tend to be updated more than flatpaks (in my experience).
Snapd and Flatpak are both technologies that allow users to install and manage software on Linux-based operating systems. Snapd is developed by Canonical, the company behind the popular Ubuntu Linux distribution, while Flatpak is developed by an independent group of Linux users and developers. One key difference between the two technologies is that Snapd uses a centralized approach, where all software is packaged and distributed by Canonical, while Flatpak uses a decentralized approach, where developers can create and distribute their own packages. This means that Snapd may be more suitable for users who prefer to have a single source for their software, while Flatpak may be more suitable for developers who want more control over the distribution of their software. Another difference is that Snapd uses a proprietary packaging format, while Flatpak uses an open-source format. This means that Snapd packages can only be installed on systems that have the Snapd runtime installed, while Flatpak packages can be installed on any system that supports the Flatpak runtime. This makes Flatpak potentially more portable and compatible with a wider range of systems. Overall, the choice between Snapd and Flatpak will depend on the specific needs and preferences of the user or developer. Both technologies have their own strengths and weaknesses, and it may be beneficial to use both in order to take advantage of the best features of each.
For keybinding, I think this user meant to cover sxhkd, which is keyboard shortcut manager, which is independent of WM you run, to have one common SW handling keyboard shortcuts ;)
One of the reasons banks and governments won't open source their software is that 1. Hackers will eventually find the bugs and attack people's property 2. Government won't pay for fixing bugs or any improvement as long as they are not forced 3. NO BODY will review these codes except some people who want to make money or are really kind hearted to waste their time for people who never appreciate them Let's make it clear, if you want to make foss, build it for making a resume or like a charity thing, most people wont find out the real reason behind foss. But anyway, you know you're doing sth good:)))
Hey DT, regarding open source payments service.. there are standards in India called UPI which is maintained by NCPI (govt org) that anyone can implement.. not sure the actual code is open source.. it probably is.. but it works very well.. every bank is forced to support it by regulator (RBI).. basically your statement that payments has no solution seems incorrect to me using UPI in India..
commenting on the Discord question: what is the problem in using a proprietary software which is free, nice, efficient and easy to use? I know the ideology stand point, but, in my opinion, there must be any practical reason. Ideology only by ideology can be pointless.
Because the official discord client kinda suck? (if discord sees a newer version available than what your package sources offer, you will be locked out of discord until you receive the next update. It just keeps breaking. Also the electron version they ship is ancient.)
Hey D.T. You were sure right about Arco Linux. Arco is the first arch base I really like. I do miss the mx snapshot feature. Can you show how to do a mx snapsot knockoff for Arch linux? I started my Arch journey and while I rtfm I would like a way to go back to my setup after a system failure. MX Snapshot was a cool utility that I miss.
most official proprietary clients does not exist for linux on arm (spotify, steam, discord, dropbox) or for linux at all (netflix, disney+). if there exists some opensource unofficial clients, you can at least access the service, if it's not accessible in the web browser (that will be problem on arm, as widevine is only available as 32bit binary in debian).
God snaps appimages and flatpak all those other things are getting ridiculous. People will do anything to get around manually compiling something including doing things much harder than just compiling it in the first place. I think serious Linux users should at least try installing LFS if not KISS Linux and compile your own kernel at least once to give a better understanding of how things fit together. Another cool distro is venom Linux that uses scratchpkg a source based package manager. There’s also some bin repos for the bigger things like browsers that take forever to compile but ya you can even use scratchpkg on top of your LFS install if you wanted but stop being scared and try building things yourself it’s much more rewarding
Same here, learned linux by installing and using it every day, since I started using linux around 2007 I have installed and tried around 60 linux distros out there, don't remember the exact number right now, but it's been one hell of a ride, learned a lot on how they worked, the ones I haven't tried yet are LFS, Arch & Gentoo, for me, I say it again, for me, they're too complicated and take too much time to work on them, I don't like things that are too complicated and/or require too much time to work on them, also I'm not very keen in RTFM, LOL!😅 P.S. Also the linux distros help forums are of great help, you learn a lot on them too, even when you find some trolls allong the way, LOL!😁
Hey dt, can you please make a video about vim plugins? From scratch to advanced. Specially how to install language servers, autocompletion etc. Please dt. I watched many youtube videos, they just provide a vim config, don't explain how config should be written.
I started learning back in the early windows 95 days. I was curious if I could make 95 look different and came across a link about Linux. Installed it, fucked up mom's computer, learned how to fix things and have been hooked ever since.
Discord is bad no matter if there is a open source client, but in the same case with Snap then it is fine. how can you say it is ok with snap and not discord ???
it is opensource, the source code is on github. but the packages provided by microsoft is "enhanced" by some proprietary bits and with telemetry enabled. but you can build your own packages from that source code or use vscodium which is "clean".
I still think an open source client and proprietary server is a million times better model than a proprietary client. At the very least you can know what kind of data gets sent to the server.
That's what i use because: if discord sees a newer version available than what your package sources offer, you will be locked out of discord until you receive the next update. It just keeps breaking. Also the electron version they ship is ancient.
personally,i think app containers (whatever they are called) like snap are just unnecessary it just seems like more bloat and overhead just to run a program if you don't like the package manager use a different distro like void or something
you should not hide the 'bald trolls' - nm yes you should... let me know when you are gonna grow it out cuz i am uber curious, til then i will use gimp to check you out with a big fro etc love the shaved look and of course love the videos
Hey DT, why is proprietary software automatically tagged as garbage ? I am not defending proprietary shadiness such as monthly subscriptions or telemetry. If software does something really well and is easy to use, is it garbage ? As a fan of technology, I try not to limit myself to what I use. To me, I relate it to music. If I say only genre x is good music, then I am missing out on a lot of music that may reside in some other genre.
The financial sector is proprietary because the companies that own the software also own our government, and they simply find a way to make any open source alternatives illegal.
The line between open and closed sources is very much ineligible. True open source does not exist yet. Hardware is generally closed source. So pretty much all of opengl or vulkan (gui app renderer) is closed source. So play nice with propriety software. Free and open source support is indeed good but also kinda a hypocrisy. Saying from the hypocrite myself.
Why hypocrisy ? If people tend to do the best they reasonably can, is that hypocrisy ? So since no human on earth could achieve perfection then everyone is hypocrite ?
@@heroe1486 probably, all we can do is better ourselves. Pretty much everyone is hypocrite since hypocrisy is about idealiogy that can't be achieved or practiced by the preacher themselves.