CrayonRosary
The published order. Always.
I just realized it's the funky shaped border masking his foot. I first thought his foot was sticking out beyond the border.
It's true, though. This was you being an ass:
No, I'm reading what you write and gathering that you have zero idea how torrents work or even what they are...
What an asshole thing to say. And "running around"... Funny. It was one comment.
Which is what OP actually downloaded from Humble..
You said they downloaded the "tracker". Wrong!
I'm starting to gather that you have zero idea how torrents work or even what they are...
That certainly doesn't look like a foot belonging to a human.
You're being pedantic. The file extension is .torrent. Lay people call those torrents.
You, yourself just used "tracker" wrong. The tracker is the server hosting the torrent peer list, etc. Not the .torrent file.
And then your followup comment is just you calling the original commenter ignorant. You're not helping at all.
Torrent files contain hashes that verify the contents of the associated files. They are not easy to fake by injecting malware. That would require finding a hash collision so your malware files (plus some padding) hash to the same value found in the legitimate torrent file. That not some easy task to do.
Downloading a torrent file from a legitimate site—and its associated data—is as secure as downloading any file from that same site.
I recently leaned a lot of these "oldest people" are not who they say they are, are much younger, and are involved in pension fraud. Especially when birth records from 100+ years ago didn't necessarily exist.
Kinda ruined all these wholesome stories for me.
Replace beatbox with masturbate and all the sounds with "fap". And then creatively censor parts of the middle two frames.
Here's an example. I'll escape the markdown so you see the raw text:
:quality(80):no_upscale()/2018585659_8_1_230614_022120-w1920-h1280)
The URL contains unescaped parentheses which are illegal in a markdown link because the link itself must be wrapped in parentheses.
This results in my comments showing no pictures and users only seeing this nonsensical text:
:quality(80):no_upscale()/2018585659_8_1_230614_022120-w1920-h1280
If I try to escape the parentheses, I get this:
Oh, hey, it's the picture!
Whatever admin or bot is editing people's comments when moving pictures to some other host needs to escape special characters in the URLs.
Edited the image to stop putting the person on blast.
It would be good to display whatever the real error is instead of this erroneous message.
I don't even use filters except for a very short list of user filters from before the block API was implemented in Sync. I do, however have a very large list of blocked communities on the server, but I don't see why the Lemmy API would generate an empty page of posts due to my server-side blocks. Is it not smart enough to generate a page of posts after excluding my blocked communities? I've written a lot of paged database queries with filters, and implementing blocks after performing the query would be pretty dumb.
UPDATE: I just found this option:
Settings shortcut: Media > Shown options when peeking
That's where a "keep open" option could go, as well as a save button.
A lot of thumbanils have high resolution, and I want to see some detail on them without loading the article just to see it. Especially since mobile web pages most often don't allow zooming anyway.
Another option would be to have a save button you could release your finger over to save the thumbnail.
Even if it is an image post, these buttons could be available since I often don't pay attention to whether a post is an image post or not, and peek the image either way.
That gets squirted directly onto canvas and sold to fans.