I can't wait for the Etch-A-Sketch movie!
It always used to be IANAL on reddit. Why did they drop the I?
It's not sync-hronize. It's synch-ronize. So "synch" actually makes more sense. Just like "psych".
I don't take it seriously. I just don't see why people would want to share an unfunny comic based on a complete misunderstanding of what the singularity is.
It's not a meme. It's a comic, and a bad one.
Who's "we"? I love recaps at the start of an episode when the last one I watched was a week ago. If you don't like them, it's streaming video. Just skip forward!
I'm not OP.
If people had just chilled the fuck out... we might be in a better place now.
Gamers aren't a bloc, and each person has their own individual game tastes, opinions, and willingness to spend money on trivial junk.
Most gamers are tween Fortnight players or ones who play exclusively mobile games full of ads. They are not people like us. This was inevitable, and nothing would have or will ever change it. Most people just want a pleasant distraction from the horrors of life and don't have any particular principles when it comes to how they spend their money on games.
Those are wax beans.
Those are wax beans.
In the Android app, open your profile, tap Data and Privacy, then Personalized Shopping, then toggle it off.
The image link in question:
Screenshot of web UI of this post:
This was a comment I made on a "sink" post the mods deleted, and I think it's an issue that needs addressing, so I'm pasting it here. The comment I replied to said something like "Superscript and spoilers have always worked fine in Sync".
Ironically, that isn't valid Lemmy markdown. Sync should be supporting Lemmy markdown, not Reddit markdown. Here's what your comment looks like on the website:
This is^superscript^ and you can also do~subscript~.
Source:
This is^superscript^ and you can also do~subscript~.
Here's what it should look like:
Instead, you get this:
Personally I don't like Lemmy's syntax for spoilers, but Sync should still support it!
hidden or nsfw stuff
a bunch of spoilers here
Source:
hidden or nsfw stuff
a bunch of spoilers here
I'm surprised that actually even works in Sync. It didn't used to. However, Sync doesn't show my code block accurately, which is funny as fuck! No app should be editing my code block. Sync is replacing my text with reddit markdown in order for it to display properly. And even when I put that markdown in a code block, it still converts it to reddit style! It also strips out the warning text!
Here is what I actually typed:
And here's what Sync shows:
What a lazy ass way of doing it. It removes an important feature: the warning text, and won't even let me show Sync users how to do a proper spoiler!
Oh, WTF. Sync butchered my comment when editing it! I had to fix it back on desktop.
Sync is not fine. It's full of bugs that the dev is ignoring.
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.
The result 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.
Update it from the github. They released some bug in the version in the repos, and the fix hadn't yet made it there yet. At least that was the case a couple weeks ago. Updating from github fixed that problem for me immediately.