The package is experimental and is mainly for developers of cryptographic libraries, not for application developers.
Seems to me that any application that accepts password input should be doing this. I wish more languages offered a reliable way to do it.
On KDE Plasma, I would stick with Kate and hide/disable some the fancier interface features. It might seem like overkill, but since it’s built from common components that other KDE apps use anyway, the effective resource consumption will probably be light. And Kate is quick.
On a Gtk desktop, you might try Mousepad. This is what I used before moving away from Xfce.
Scintilla my beloved
(This is the text editor component in Geany and Notepad++)
You may be underestimating the competency and speed of KDE devs. These people are the effing top.
I promise, my view of KDE developers is well informed. But it doesn’t matter, because KDE development alone isn’t going to fix deficiencies in the Wayland protocol.
so this is all a non-issue.
I think that view is overly optimistic. We shall see.
Yes, but I don’t want to dox myself here by pointing out specific issues that affect me, and I already have a plan to address my particular needs (although it will require significant work and still leave me with a worse Plasma experience).
I’m more concerned with the impact on the community as a whole. This will push some people into migrating to the ghetto of a very-long-term-support distribution, costing them time and making them second-class citizens, and is likely to push others into giving up Plasma entirely. I don’t think we will hear from many of them, since most people either do not participate in software discourse on social media, or will realize that there’s not much point in shouting when you’ve been deliberately left behind.
Too soon, IMHO. This is going to be disruptive to people who rely on X11 functionality that’s unsupported or broken on Wayland and XWayland.
I can only hope that the fallout leads the wayland-protocols maintainers to finally address more of their project’s deficiencies.
It is impressive to see Quake run at full speed knowing that Windows 95 runs DOS executable in a virtual machine.
I don’t think it was a virtual machine in the hypervisor sense (as the term often implies today), nor in the bytecode interpreter sense (à la Java).
But if the ENDS are both compromised…
If either end is compromised, then there is someone reading over the proverbial shoulder, and the conversation should be considered compromised.
Hopefully Linux Phone gets some love.
That would be a welcome step in the right direction, as would open hardware.
So just to confirm the answer to my question question: Its pointless to use encrypted messaging on an Android device?
Of course not. End-to-end encrypted messaging protects against eavesdroppers in transit. It’s an opaque envelope.
(Edit: Keep in mind that Google is not the only potential eavesdropper out there.)
What it cannot do is protect a message from someone reading over your shoulder when you write a message or open an envelope. On mainstream Android, that could be Google, if they choose to abuse their system-level access. On iOS, it could be Apple. And so on.
Those companies might be eavesdropping on sent/received messages already, either at a large scale or in a minority of cases, or regionally, or they might not be doing it at all… yet. But they have the capability. You’ll have to decide for yourself whether that risk is acceptable.
Google has the capability to read everything that you can read on an Android phone, unless you have taken steps to remove all Google-controlled components that have system-level privileges. Last time I checked, this included Google Play Services, which are installed by default on most Android phones.
Note that messengers with end-to-end encryption, like Signal, cannot protect against an adversary with full access to your device.
This is part of why people de-Google their phones, which usually means replacing the entire OS with something like LineageOS or GrapheneOS.
If you’re implying that I didn’t recognize someone taking a jab at a unix command, then no, not whoosh. I got that. It doesn’t make a clever or funny joke, though, because the command they chose to ridicule is easy, and is the same in other archive tools like 7z and rar.
If you think something else went over my head, then perhaps you could enlighten me by saying what you mean.
tar x is pretty easy, isn’t it? Or tar xf if they need to specify the input file/device.
deleted by creator
To be clear, this is not about EXIF data (which is its own problem).
Digital cameras can be fingerprinted from the images they produce, due to variations between pixels in any given sensor. If you’re concerned about an image being traced back to your camera, you might consider some post-processing before distributing it.
Yes. I posted the link because some of us won’t visit that site, but are curious about the video.
This appears to be the video:
I wonder if they’re counting the SIMs in smartphones.
the operating system does not interpret it in anyway.
*in any_way. ;)
What about Googling stuff offline?
The word master does not originate from slavery. If you study the etymology, you’ll also find that it significantly predates slave, and has more than a few meanings that are not even remotely related to slavery.