

Yes, that’s something I’ve thought about doing
Punch nazis, trebuchet TERFs.
I am building Voyager, a client for lemmy!
Yes, that’s something I’ve thought about doing
The main reason is SSR so sharing in messages provider the preview image and whatnot. Also more control over the onboarding, and avoiding confusing the PWA with the native app. That’s a nice alternative though!
Universal Links that are verified, like go.getvoyager.app, will automatically open in the app. The Lemmy links are there, but are “unverified” and won’t open in the app unless the user configures them to. Also, adding unverified domains isn’t possible in iOS. So this is a much more universal, zero-config option.
Mastodon redirect is great and works with voyager, but is more of a power user thing. Go.getvoyager.app works out of the box :)
This service requires knowing that the other party also has and exclusively uses Voyager.
Well, kinda. It is one click to open the Lemmy link directly. I’ve also thought about adding config options to the service to auto redirect to the Lemmy instance, to make it unobtrusive for other app users. The code is open source so I’m happy to hear suggestions to make it work better!
Last year 5 people in my town burned alive in a Tesla while talking with 911 operator after a crash. No media reports other than local news.
I will probably investigate after Lemmy v1 is released, no promises though. Support for two platforms would add a significant amount of development overhead.
For losing your position, I recommend enabling and using the hide posts button. You can always temporarily unhide and/or reset by long pressing the hide button. 🙂
I’d say about 50% of reloads is an iOS bug where indexeddb crashes. Apple is aware of that one but they haven’t fixed it yet… so should get a bit better eventually.
Looks like it loads flakey. Issue with the image host maybe? Here is screenshot of Lemmy-ui via Lemmy.zip also not working.
That would be super cool! I think it could be accommodated in Lemmy API. Have you tried making a feature request there?
The strikethrough you posted works fine in Voyager. If something specific doesn’t work, please post in [email protected] (or better yet, a GitHub issue) so I can fix. :)
Not sure what’s going on with hexbear, but I doubt they block those users in app. Maybe you’re using an instance that is defederated from them or something.
I’m the voyager dev and you’re using the voyager app :)
Voyager blocking behaves exactly the same as in jerboa, since both let the backend do it.
As for markdown, what do you mean? Like a WYSIWYG editor? If so, Voyager prefers to write markdown directly. Fun fact: it was actually one of the main design goals of markdown!
I’m happy to add a “contrast”/“colorblind” theme too if none of these work for you. Just lmk a list of hex codes that work in light mode (dark mode darkens them).
Lemmy doesn’t support push notifications yet. It can be tracked here: https://github.com/LemmyNet/lemmy/issues/2631
You can track progress by the Lemmy devs here!
New Lemmy users aren’t mods usually, so they won’t see this UI element. In any case though, I like this UI 😉
Oh I see, that’s why then. It’s necessary for version info
It’s not going to change, sorry. This is the way Apollo has done it and I really enjoy its UX. For new Voyager mods, I recommend giving it time to get used to it.
It’s essentially a shortcut button, that’s all. And show you what actions you can take at a glance on an arbitrary piece of user generated content.
What I mean is your username will be green if you distinguish your comment so that others know you’re a moderator.
Voyager doesn’t show users that you’re a moderator unless you explicitly distinguish your comment, to allow you to interact without asserting yourself.
Edit: as an example, I just distinguished this comment
Have you tried resetting hidden posts?