vger://__HOST_PATH__ should work.
Edit: or universal links are https://go.getvoyager.app/__HOST_PATH__
Ah, thanks for letting me know. I just checked and it's because you're running lemmy v0.19.3. That's pretty old; I would recommend upgrading.
That being said, Voyager should have more helpful error messages for unsupported versions, and also should still support 0.19.3 until the next major release, so I'll push a fix.
That’s actually incorrect, it is a solved problem in voyager. Clicking the link in the post from any Lemmy instance, or up to date piefed instance like piefed.blahaj.zone, opens in app.
The only reason it doesn’t work from piefed.ca is piefed.ca is running an outdated version of Piefed that doesn’t support the federated instances endpoint in api/alpha.
Proof:
Thanks for checking!
I was actually testing an invalid login, where it says "connection error" instead of "invalid login credentials" because the backend error isn't sent due to a CORS issue.
After attempting login with piefed.social vs feddit.online, here's the screenshots. See the "CORS missing origin" error under trasnferred column for feddit.online. Also the lack of access-control-allow-* headers compared to piefed.social.
Awesome thanks for confirming!
That’s what happens when you try to signup, not login. There is a login button below pick a server button.
Also, try the web at https://vger.app/, probably easier to debug!
Do you know the admins? It looks like CORS is broken on signin (POST req), which causes the PWA to break.
Works for all the other instances so maybe they are doing something custom
The image link is broken, doesn’t work in the browser either
Hey, thanks for the Voyager rec! Note, Piefed is still experimental with Voyager, there are known issues, so as others said it might be a bit early to recommend to brand new users.
Also, any reason you prefer https://vger.app/settings/install versus https://getvoyager.app/? The latter has a bit nicer onboarding!
Voyager now has experimental Piefed support in the App Store and Play Store. F-droid rolling out soon. 🥳
Make sure your app is up to date (v2.37.0 or greater) and enjoy!
P.S. Support is under active development and there are known and unknown issues. Please post any feedback or questions!
::: spoiler Background image credit
https://images.nasa.gov/details/hubble-observes-one-of-a-kind-star-nicknamed-nasty_17754652960_o
Astronomers using NASA’s Hubble Space Telescope have uncovered surprising new clues about a hefty, rapidly aging star whose behavior has never been seen before in our Milky Way galaxy. In fact, the star is so weird that astronomers have nicknamed it “Nasty 1,” a play on its catalog name of NaSt1. The star may represent a brief transitory stage in the evolution of extremely massive stars.
First discovered several decades ago, Nasty 1 was identified as a Wolf-Rayet star, a rapidly evolving star that is much more massive than our sun. The star loses its hydrogen-filled outer layers quickly, exposing its super-hot and extremely bright helium-burning core.
But Nasty 1 doesn’t look like a typical Wolf-Rayet star. The astronomers using Hubble had expected to see twin lobes of gas flowing from opposite sides of the star, perhaps similar to those emanating from the massive star Eta Carinae, which is a Wolf-Rayet candidate.
Instead, Hubble revealed a pancake-shaped disk of gas encircling the star. The vast disk is nearly 2 trillion miles wide, and may have formed from an unseen companion star that snacked on the outer envelope of the newly formed Wolf-Rayet. Based on current estimates, the nebula surrounding the stars is just a few thousand years old, and as close as 3,000 light-years from Earth.
Thanks, I can reproduce it! It happens when the remember feature is enabled and you're opening a post for the first time from a community where you haven't opened any other posts from (since app startup)
I'll fix in the next release
Not sure where to post this: the Piefed API doesn't support CORS, at least testing against piefed.social, so requests from webapps like photon, alexandrite, voyager via PWA would not work.
Also, is there a way to pass a fedilink to resolve, like Lemmy resolveObject?
And lastly, how is Piefed planning on handling updates to the API for lemmy v1? Things like varying object type arrays being combined, and new/updated sorts.
Thanks!
NOTE: This feature is currently being rolled out to the Apple and Google stores and should be available in the next day or two. However on desktop you can try it out right now (after enabling - see below) at https://vger.app/!
This is currently in BETA, and is turned off by default. On tablets and desktop, you can turn it on in Settings -> Appearance -> Layout. (The setting won't show up on phones.)
The right column is dedicated to viewing a specific post. The left column is for the regular navigation of the app.
Pro tip: On macOS, I recommend adding Voyager to your Dock (https://vger.app/) with Safari's new "Add to Dock" feature! Check out the above screenshot - it's quite slick.
Enjoy and let me know what you think!
I recently got fiber internet and wanted to bypass all ISP equipment with the was110. Since I needed a router with SFP (I've had an Edgerouter-X for years) I decided to go switch to Mikrotik.
The l009 is such a nice router! I ended up pairing it with a cheap no-name multi gigabit managed switch (4x 2.5gb rj45 and 2x sfp+ for high speed transfers to my NAS) and a Mikrotik wAP AX for wifi, which is powered through the passive PoE on the l009.
I've been playing with LACP bonding, VLANs, firewalling and IPv6 and there is so much to it. It is such a great way to learn.
Mikrotik is a pretty cool company too. Fair prices, based the EU, have a fediverse presence (shout out @[email protected]) and support old hardware pretty much forever.
Granted, their equipment has a quite high learning curve. But if you have the time and patience, it is really rewarding.
view more: next ›
The go.getvoyager.app links work well for those that doesn't have the app installed, so good for sharing with friends. Not really relevant for your use case though!