Yeah, that is a valid opinion to hold. I am saying that trust is garbage.
You could consider compiling the KeePass app yourself, if you’re worried about that one in particular.
A guy I used to study with, decided that he just wouldn’t have a password manager on his phone.
I’ve certainly considered switching to a Linux phone for that, among many other reasons…
This F-Droid-like model (also popularly implemented by Linux distributions) is usually considered an improvement in security.
The thing with FOSS is that ideally you don’t have to trust the developer at all.
In theory, you could read the entire source code and compile it yourself. Then you’d know for sure that no malware is included.
Obviously, in practice, you can only hope that some nerds dig into the source code and notify journalists of malware-like behaviour.
It is no perfect protection. But it is the only tangible protection that FOSS actually delivers.
What does not protect you, is to trust each individual developer. They could publish innocous source code and then build the release binaries from a version with the malware-like behaviour patched in.
But because you likely don’t want to compile each app yourself, you might still feel compelled to entrust that work to a third party. This is where the F-Droid team comes in. Rather than trusting each developer, you just have to trust a single team.
Well, and if an app is built in a reproducible build, then even the work from the F-Droid team can be verified.
I’m excited for these, especially with them likely coming for stable Firefox soon, too. My $DAYJOB hands out Ubuntu laptops and every time, we have to scrape off the Firefox Snap, because e.g. saving images doesn’t work and the Downloads directory is in some mystical place somewhere underneath ~/snap/. These APTs will almost restore the usability of other distros…
Ültrafast
Wenn beim Angelsächsischen mal wieder das Sächsische durchkommt…
If it helps, the Windows/Linux logic is basically:
Well, and Ctrl, Alt, Shift also serve for alternative characters when you’re typing. And some application or OS shortcuts wildly combine modifiers for more complex keybindings. And of course, some applications just didn’t get the note of how this generally works. I won’t claim, it really follows rules, but yeah, it’s not generally complete chaos either.
I think, what you’re describing used to be a thing, but there’s now a somewhat different, more granular way of rebinding keybindings:
However, it should be said that these will only apply within KDE applications. If you’re using third-party stuff, like Firefox, GIMP, VLC etc., they won’t apply.
If you really want to go hard on rebinding all kinds of keys for any application, you can also do things like these:
As cool as both of these are, and as much as I would still generally recommend picking KDE for these kind of customization possibilities, I wouldn’t recommend overdoing either. You won’t be able to use other PCs anymore…
Pictures are probably better than a thousand words here:
I’m a massive fan of GUIDs, too, but you’d have no protection from rogue instances reusing GUIDs of existing posts…
Less self-explanatory than “source-available”, because of that official definition.
I am talking about the official definition: https://opensource.org/osd/
The publication of that definition is what caused us to use the word “open-source” in our vocabulary. And the first sentence in that definition is “Open source doesn’t just mean access to the source code.”.
When I talk to our legal team at work and tell them that a library is open-source, I’m effectively saying to them that there’s no legal restrictions on us using that.
Mere access to the source code does not offer that. You could be granted access to the source code and not even be allowed to modify it, as you suggested to OP.
As far as I can tell, this is the case for Grayjay. So, yes, OP can modify it, assuming they don’t get caught doing so.
So, why can’t you say "source-available” or “basically open-source”? For a few weeks, I genuinely thought Grayjay was open-source, because of misinformation that you and others are spreading. It was mere chance that I looked into their LICENSE file, because I was curious to see what open-source license they’re using, only to see that they’re not.
I’m a software developer, so my interpretation of “open-source” needs to be extremely precise. Open-source has tons of legal implications. Their FUTO TEMPORARY LICENSE breaks some of those implications, which is fine by itself, but if you use the one word in the English language with a clear definition for it, then you’re effectively lying to anyone who uses that precise definition.
Here’s a solid recommendation post for PeerTube channels, which you can look through: https://social.growyourown.services/@FediFollows/111291322079656821
If you just want videos from PeerTube and Piped to appear in the same feed, you can do that via an RSS news aggregator. For example, Mozilla Thunderbird has that built in, but there’s also tons of small, dedicated applications, depending on what OS you’re using, or even as a browser extension.
In PeerTube, you can get an RSS feed, either of your subscription feed directly, or for the individual PeerTube channels, you’d like to subscribe to.
I don’t know, if you can also get an RSS feed for your subscription feed in Piped, but you can get it per channel. Just click on the little WiFi-looking button.
Grayjay is not open-source. It’s source-available. That still means your comment is true in principle, but don’t expect to be able to share your changes with anyone.
“Open-source” is not up for interpretation. The word was coined by this definition being made public: https://opensource.org/osd/
Interesting, I didn’t know that, but it doesn’t really change anything about my comment. Mozilla can offer APIs in addition to what Manifest v3 offers, allowing extensions that want to do these things to do them. It’s already the case today, for example, that uBlock Origin makes use of additional APIs for more effective ad blocking on Firefox.
Mozilla will want to be API-compatible, but there’s nothing inherent to the API that requires the arbitrary content-blocking limitation that Google put in. So, Mozilla will be API-compatible without adopting this shitty limitation.
Yeah, everything you said there is correct.
If you want a somewhat more comprehensive definition:
Funkwhale, Lemmy, Kbin (as well as Mastodon, PeerTube, PixelFed etc.) are pieces of software, which can be hosted on a server and which implement a communication protocol for the federation of social media content.
If someone then takes such a piece of software and actually does host it on their server, then that’s called an instance. Generally, they need to buy a domain name to do so, like “open.audio”, “lemmy.world”, “feddit.de” and so on.
You might be interested in Funkwhale instead.
It’s a more mature piece of software, it does federate and they’ve even put quite a bit of effort into podcasts.
They have a flagship instance at open.audio, which only allows Creative Commons content (to avoid copyright issues when federating).
So, as I understand, if your podcast is CC-licensed, they’d be happy to host yours.
I use Fira Sans and Fira Mono for everything.
Normally, I would reply to the guy, because, you know, he’s a human being, but there’s so many replies, I doubt, he can actually read all of them and potentially someone else has already made that point.
Anyways, I feel like something he kind of misses here is that many of us do it from a heartfelt place. Like, we’re all techies. We’ve all used commercial software to a point where we’ve grown so frustrated with it that we decided it is a waste of time.
So, it’s not us saying “Why don’t you go and just have more time/money?”.
Rather, it’s us saying “This thing is wasting your time? Here is a solution that I felt wasted less time in the long run.”.
Yes, sometimes that does miss the mark, because not every complaint is looking for a solution. Or because we may be frustrated with restrictions of commercial software, which are not a problem for less techy people. Or even because we’re embedded in this tech world and are hoping to make it a better place, which someone just quickly visiting may not care about.
But other times, I do just happen to know a lot about technology and a non-techy genuinely did not know about the solution I suggested and is actually really appreciative of me bringing it up. It does happen. And it’s not easy to discern who would appreciate a suggestion and who won’t.