Spending short lifetime for development and boring things.
$argon2id$v=19$m=512,t=256,p=1$J7IZNfNG3RC2FiSRzZfQzw$0seu3KTpAnSufFxXDbHccXnX81enF+A++beI9VvHVVA
Just one question - where it is native? Are you pretty sure?
Disabled, not needed. iOS.
Not Electron but yes unfortunately. It uses Ionic that isn’t native, but as declared “native-quality”, that means “mostly looks like native” but that’s not so 🤷🏻♂️. But anyway Voyager is cool. It could be really better with real native UI onboard of course.
Already now. Approximately 4h.
That new problem isn’t about links in post body, but about link in the “link-post”. To reproduce tap to “example” link and then tap to link there - will open in the browser instead of this app.
Okay, seems to I was wrong about special url-handling. I needed for lemmy hosts as minimum. As example, will be great to open links to posts in the same app instead of in-app/os’s browser. So now I’m sure we need it for various urls and I was wrong 😑
Excepted result, kinda:
Is it really needed to create special handlers for special hosts? Where YouTube is there and Twitter and other services. So, how much special handlers there will be?))
Okay, I can reproduce it on iOS and it is expected behavior.
In the settings turn on open links in in-app browser. Results is expected as promised - in-app web-view.
Otherwise if you set “open links in default browser”, it opens with YouTube app after all because of app-url-scheme, you know.
So, IMHO, all right on iOS.
Just link to test and reproduce. https://youtu.be/1riOhUGTY2U?si=dU820qhERnmCzTS0
1.15.6, all ok, can’t reproduce.
Okay, just take a look at code. https://github.com/aeharding/voyager