SatyrSack @ SatyrSack @feddit.org

Please correct my English.

---

Read more

Posts

2

Comments

299

Joined

10 mo. ago

I think that is just one of the differences between the iOS and Android versions. I have all the gestures disabled in Voyager's settings, but swiping does nothing.

Are you referring to the Android system navigation mode (Settings app > System > Gestures > Navigation mode)? I use 3-button navigation, because setting that to gesture navigation just causes too many problems in various apps.

But aside from that, my current Lemmy app, Thunder, allows me to swipe from anywhere onscreen to navigate back. Not just from the edge. Which is much better for accessibility purposes.

I see gestures as one of the promoted features on that site. Is there a way to use gestures for navigation instead of actions? That is the one feature keeping me from Voyager. I want to be able to swipe to go back, etc., not swipe to upvote, etc.

HTML predates XML by several years.

Yes, 6 - 1 = 5

One of the six edges is angled, making the edge opposite of it unusable for scraping ice.

I think they mean having an AI read code and then write documentation for it. Not having an AI read documentation.

You can still seed without port forwarding. This machine is running behind Mullvad

Could be worse. At least it's documented

Kongratulations

*KOOL

The Internet is a series of sewer pipes

Huh, I did not know that any didn't. I just tried a bunch, and here is a quick breakdown of what was preinstalled on each:

KWrite is the standard text editor. Kate is the advanced one. The name actually literally stands for "KDE Advanced Text Editor"

THERE'S A GOD DAMN GATE

Add support for the Proteus Byowave controller

That sure looks like an interesting device, but I cannot imagine that being worth the €300 for anyone. I would expect that even someone who really needs a far-from-standard controller for accessibility reasons could find a better (albeit less reconfigurable) option to suit their needs.

https://byowave.com/

The past two generations have supported that

I think it depends on what app the formatting is displayed on.

That is probably where the confusion lies here. Because in the default Lemmy web UI, omitting the space literally displays the number signs as-is without making the line a larger font at all.

A question about this: does it change the way it actually looks? I’ll fix it, but I’d love to know if there’s a practical difference in using space vs no space?

Without the space, they don't render as a header at all.

No space:

##THE LIST

With space:

THE LIST