It's a problem with lemmy.world, likely due to running outdated lemmy 0.19.3 (looks great on lemm.ee, feddit.org, vger.social)
Not a client issue.
It's a problem with lemmy.world, likely due to running outdated lemmy 0.19.3 (looks great on lemm.ee, feddit.org, vger.social)
Not a client issue.
It's a problem with lemmy.world, likely due to running outdated lemmy 0.19.3 (looks great on lemm.ee, feddit.org, vger.social)
It's not a client issue. It's a lemmy/instance-specific issue. Look at the following link in your browser, then tap the image to expand. You will see bad image quality. https://lemmy.world/comment/11323036
Edit: Works fine with my vger.social account. Looks like shit on lemmy.world.
Edit 2: Looks like shit on sh.itjust.works and lemmy.world. Which are both running very outdated 0.19.3. Looks great on feddit.org, vger.social, lemm.ee which are running up to date version of Lemmy (0.19.5).
You're welcome! 💜
It depends on your instance.
This will be resolved once https://github.com/LemmyNet/lemmy/issues/4698 is resolved so please give it a "thumbs up" if you want it!
Can you do a screen recording? THanks!
Wisconsin does this to preserve native ecosystems! I believe this particular land is maintained by the County.
Prescribed fire is the intentional application of fire to a specific pre-planned area, under specific environmental conditions, to accomplish planned land management objectives. Without the use of prescribed burning as a management tool, Wisconsin could lose many of its native grassland, wetland and savanna plant communities.
https://dnr.wisconsin.gov/topic/forestfire/prescribedfire
https://www.danecountyparks.com/Volunteer/Prescribed-Burns
https://www.cityofmadison.com/parks/projects/2024-prescribed-burns
It works fine for me. Press the picture in picture button on the video overlay from post detail page
Go to profile -> hidden posts -> reset
What do you mean, “voyager wasn’t going to be supported”?
Hi there! I've received a few requests, so I've created a Patreon page for Voyager.
This adds an additional option, alongside Github Sponsors, Liberapay and in-app donations.
Thanks again to everyone that supports Voyager! 💙
While I have you here, let me show off a few of the new features from the release earlier today!
Random Community Button
Find new communities, randomly! Pull to refresh to find a new random one with ease.
Launch native app if available
Currently, if you tap a Youtube link, it will open Youtube in the in-app browser. (And same with news apps, etc.) Now, by default, it will open the app, if installed.
You can easily flip this off in Settings to get the old behavior ("Prefer Opening Native Apps").
Shortcut to copy text
If you want to copy all post/comment text, there is now a handy copy icon in the header of the sheet!
Android navbar style updates
I've tweaked Android navbar styles to make them a little nicer.
aeharding purple highlight
My username is now purple, so you can easily identify me as the Voyager dev
iOS Cache Clearing
You can now clear iOS cache for Voyager (native app only). Please note: It will not clear everything - iOS seems to keep 100mb around, without a way to clear. Other apps I checked seem to have the same issue.
Comments theme
You can now style the comments theme!
Record breaking temperatures today. 70F
Voyager has finally added support for spoilers! This was the 9th issue reported in Voyager's Github project, back in June last year. (Since then, Voyager users have created nearly 600 issues with around 500 being resolved!)
It was a huge undertaking, involving a few different packages and nearly one hundred unit tests in order to ensure proper parsing logic.
Also, I've published Voyager's spoiler plugin with AGPL-3.0, so any other FOSS lemmy app using Remark for markdown parsing can more easily add spoiler support :)
So, now Voyager should properly parse spoilers, check it out below! Shortly, I will add support in the Markdown toolbar so you can easily create your own.
(by the way - this release also adds support for horizontal rules. Voyager should now support all of the official Markdown syntax.)
Formatting
The Lemmy spoiler format is based on the CommonMark Container Block Directive proposal. In fact, the spoiler plugin was forked from remark's directive plugin (this plugin is not flexible enough to be compatible with markdown-it-directive, what lemmy-ui is using, without forking). Their behavior is very similar to Markdown code blocks. Here's the "happy path" syntax (but there's edge cases that behave similar to edge cases of markdown code blocks):
Hi there!
Some text
Some examples
Below are some examples stress testing the spoiler parsing.
The spoiler syntax happy path
Some text
::👋 Hi there with bonus colons and spaces!
This is a spoiler message. Boo! 👻
spoiler Nested spoiler!
This spoiler is nested within the "Hi there!" spoiler. I don't know why you'd want to nest spoilers... But you can 😆
:::::
Spoiler in a quote with implicit closing fence
You can quote spoilers. 🤔 idk why you'd want to but you can.
spoiler A spoiler at the end of the post
Bonus dog for tapping spoiler
view more: next ›
Probably because Sync on your phone is connecting/downloading directly from Imgur, which is bad for privacy. Voyager uses the image cached on your instance, if possible, to avoid connecting to arbitrary hosts to load images when browsing your feed.