Yep - the latest release supports both 0.18.x and 0.17.x. I’ve been running it for the past few releases over the last couple of days and I really like it.
It gets weird fast, because before privacy controls in the Lemmy source code mean anything, we need trusted third party verification of a server’s patch level, and security controls.
That can be done, and I think Lemmy has a shot at getting to that point, but it’ll be awhile.
In the meantime, I suspect the Lemmy developers are hesitant to add and advertise features that you can’t be sure are actually correctly enabled on your instance.
But yeah, let’s not let perfect be the enemy of moving toward better.
Edit: Assuming you completely trust your instance admin, we could start adding some basic privacy to actions taken on your home instance.
But as soon as the user starts interacting via federation, all bets are off - because the federated instance may he malicious.
I think we might see one or more “trusted fediverse” groups emerge in the next few years, with instance admins making commitments to security controls, moderation, code of conduct, etc.
So, in theory, the lemmy software could start implementing privacy controls that allow users to limit their visibility to whichever part of the fediverse their instance admin has marked as highly trusted.
But even then, there’s risks from bad actors on highly trusted instances that still allow open signups.
Anyway, I totally agree with you. It’s just a genuinely complex problem.
If all the people complaining would just contribute to the codebase this wouldn’t even be an issue.
Often, you even see the devs coming into threads like this and making suggestions, like “make a pull request.” They want more people contributing.
It’s tons of people whining, very few people contributing. Guess what? While at a certain point, adding developers stops increasing productivity, there’s a small window where adding developers does increase productivity.
If I am correct, Lemmy only has four main developers. That’s well within the range to add more developers and increase the productivity, making new features and security come faster.
So I get it, but things take time, and are complicated, which you thankfully can see.
People whinging about it in threads does nothing to change it. Donating to Lemmy’s development costs or contributing code does.
So much of it sounds like it sounds like its from less-technically-inclined people (some of its valid critique from experts, but they generally… write bug reports and do pull requests…) who just want it to be better but the only way they know how is to “bring awareness.” Well, all that “awareness-bringing” just amounts to spreading FUD.
I think we might see one or more “trusted fediverse” groups emerge in the next few years, with instance admins making commitments to security controls, moderation, code of conduct, etc.
There is now at least one system in place for admins to vouch for other instances being non-malicious, and to report suspected instances. It is called the fediseer: gui.fediseer.com
I couldn’t possibly care less about Docker Desktop. Portainer is a much better solution when graphical administration becomes necessary. (Which should be never)
This is interesting to me for my use case scenario, specifically SteamOS.
What I’m trying to do is run an emulated Everquest server (lookup EQEmu). The community there has several methods of installation of the server, Windows, Linux, and Docker. The hurdle to overcome is the immutable file system, specifically when it comes to the database (MariaDB). I think I may have found a work around via Linux brew and installing MariaDB through that (which I’ve done, I just have to make the final connection). However the Docker setup, when running it on a separate distro is stupid easy. If they make this a Flatpak, it can potentially be the solution I’m looking for.
Really the end goal is creating a Single player Everquest. I have a dual boot with it operating via Windows, but would much prefer to have it on the SteamOS side of the house.
Docker Desktop ≠ Docker Engine, and I think what you (and several in this thread) are thinking is actually Docker Engine. Docker Desktop ultimately includes a Docker Engine inside, but it does not appear you need that virtual machine (e.g. running non-Linux code). See: docs.docker.com/desktop/faqs/linuxfaqs/#what-is-t…
Docker Desktop is based on KVM, which already works with Flatpak. So this is not something new. For example, GNOME Boxes is available as Flatpak and provides a way to run KVM guests in SteamOS.
Starting with version 3.5 (the current stable) SteamOS already includes Podman with the default installation. And running the daemon-y Docker Engine “bare metal” is not going to be any easier with the immutable filesystem. While Docker Desktop solves this by using KVM, it adds another layer with performance loss, vs. just running Podman containers.
So what you want is already available, and no Docker Desktop is actually needed.
But so if Docker Desktop does include Docker Engine, does that mean I wiill now be able to run Docker (with a some performance loss) simply by installing a Flatpak, i.e. I won’t even need to touch the CLI?
Yes. If you mean “CLI” as for e.g. pacman install, it is a GUI (Electron) application, so I expect will install straight from e.g. KDE Discover and then run without you touching the shell.
Installing podman-compose with the immutable filesystem is fairly straight forward, since it is just a single Python file (github.com/containers/…/podman_compose.py), which you can basically install anywhere in your path. You can also first bootstrap pip (python3 get-pip.py --user with get-pip.py from github.com/pypa/get-pip) and then do pip3 install --user podman-compose.
I don’t use SwiftKey, just tested it because you shared a tool for doing it and claimed it was able to subvert Android permissions.
You probably didn’t actually disable the permission – like I said, the idea that an app could get around system-level permissions like that, in a way you could plainly observe would be headline news. It would be astounding that you somehow uncovered something that massive.
Damn FOSS Android Auto development is starting the new year off strong! First grapheneOS successfully implementing it on a non-stock OS and now this too. Too bad I got rid of my vehicles last year and no longer have a use for it on my ebike.
I saw the other day Tuta complaining that Outlook has been sending emails from tutanota.com straight to junk/spam. What’s surprising is tuta.com emails were fine. So not sure if their domain change had anything to do with it, or if MS is doing the same thing as in the OP.
github.com
Top