

Is that not literally the same link as the OP?
EDIT: Ah, the OP’s edit from 30 minutes before your comment has not federated out to your instance yet.
Please correct my English.
The lemming formerly known as:
Is that not literally the same link as the OP?
EDIT: Ah, the OP’s edit from 30 minutes before your comment has not federated out to your instance yet.
The comments below started me on a trail that led me to a relevant comment from a Lemmy dev:
I want to remind everyone that since users overwhelmingly don’t want their votes snooped on (for good reason), we will never add anything like this inside lemmy, lemmy-ui, or jerboa.
But it’s trivial to use an external tool to see who voted on what regardless of whose account it is
Is there a tool made for this out there? As far as I’m aware, the simplest way for the average user to do that is to run their own instance and then manually query its database directly, which is far from trivial.
Why not?
Wow, I misread “HM” as “HAHA” and had a different expectation of what the bottom text was going to be
May I go ahead and chisel your aromasphere?
I was thinking the League, but yes, that P&R scene was almost certainly inspired by the vaportini trend.
Although if you put it in vape form…
Vaportini was a short-lived trend that did not end up taking off.
There doesn’t need to be any evidence. This is something that is impossible to prove one way or the other, like Last Thursdayism.
Yes, this particular incident.
https://en.wikipedia.org/wiki/XZ_Utils_backdoor
In February 2024, a malicious backdoor was introduced to the Linux build of the xz utility within the liblzma library in versions 5.6.0 and 5.6.1 by an account using the name “Jia Tan”.[b][4] The backdoor gives an attacker who possesses a specific Ed448 private key remote code execution through OpenSSH on the affected Linux system. The issue has been given the Common Vulnerabilities and Exposures number CVE-2024-3094 and has been assigned a CVSS score of 10.0, the highest possible score.[5]
Microsoft employee and PostgreSQL developer Andres Freund reported the backdoor after investigating a performance regression in Debian Sid.[8] Freund noticed that SSH connections were generating an unexpectedly high amount of CPU usage as well as causing errors in Valgrind,[9] a memory debugging tool.[10]
Immediately get noticed
Realistically, though, we are only aware of that one because it was noticed in that unlikely scenario and then widely reported. For all we know, most open source backdoors are alive and well in our computers, having gone unnoticed for years.
You get me closer to God
Which came first, your username or your avatar?
Sure, it’s just that in the early days when we started getting more Lemmy apps than just Jerboa/Lemmur, Voyager tended to be on the forefront of adding new features not found in other apps. But nowadays, as the landscape of Lemmy apps has matured, Voyager has fallen behind as its philosophy seems to be stuck at “be a clone of Apollo”. It is by no means a bad Lemmy app; it is just no longer at the same relative level compared to other competing Lemmy apps.
Wow, I cannot even find a setting to enable it. I used to have a very high opinion of Voyager, but I am finding recently that it is missing a lot of features.
Speak for yourself
Also the internet icon shows there is Internet.
Looks to me like the icon that indicates the machine being connected to a network, but that network is not connected to the Internet.
**NO**
What is being implied here? That Website A encourages you to download an image from them in WEBP format, but you cannot then upload that image to Websites B through Z because those sites do not support WEBP?
Hmm, I think this is an Mbin vs Lemmy issue. There are two differences in the URL:
%2C
instead of,
. This part does not make a difference, because that resolves to a comma anyway=
at the very end for some reason. This is what breaks it. Remove that character, and the URL works fineThe weird thing here is that the broken URL only ever shows up on Mbin. Below are a few different links to the comment in which you shared the broken URL. If you view the comment on your Mbin instance, it is indeed broken. But if you view it on this community’s Lemmy instance or my home instance, your same comment actually has the working URL. Something about how the post/comment were federated must have messed things up.