It’s not fixed in release yet, just beta.
Do you have remember community sort turned on or off?
I see what you’re saying, but I disagree it should be consistent: the user agent should accurately identify the software that’s requesting a resource.
When Voyager just sends VoyagerApp without the browser stuff, it’s because the code that is making the http request actually bypasses the browser entirely, and is done natively with CapacitorHttp (helps to bypass CORS for perf and server misconfiguration).
I could see an argument for changing it to CapacitorHttp/8.0 VoyagerApp/1.0 for API requests. But if voyager changed the header to include browser ua, that would actually be spoofing since the browser played no part of making or handling the request.
i'm not sure why this was causing issues here though, especially with the login, as that should just be 100% api stuff and therefore use
VoyagerApp/1.0from the native app?
Yes, that’s right, that is odd! 🤔
o you know if Voyager can send browser-like user agents when installed from App Store?
Voyager actually used to haha. But added a static voyagerapp user agent because lemmy.ml started blocking without last year 🫠 can’t win unfortunately. Thanks for fixing.
Btw, voyager PWA will always use browser ua, native app will use VoyagerApp/1.0 for api requests, AND <browser ua> VoyagerApp/1.0 for browser managed requests (like loading images).
TLDR native app will always have VoyagerApp/1.0 somewhere in the string, PWA doesn’t touch the ua
Thanks, can you check the test build and lmk if that fixes it?
Can confirm! I’ll try to fix next release
Edit: potential fix deploying to test build, I will release in a couple days assuming no regressions
Ah, that sounds like an old Lemmy glitch. I’m not sure what causes it. If you could do a screen recording I could confirm. Also you can check Lemmy-ui or other apps (with same account) to confirm.
Either is fine, GitHub is better for my tracking but /c/voyagerapp@lemmy.world gets more community support
Should be fixed in next release!
I think this is a Piefed bug, I've seen it before. I'm sure it'll get tracked down at some point.
:(
Sorry I can't be more help, but I'll keep my eye out. Another thing you can try is backing up the app, then fresh reinstall and see if you can reproduce with stock settings. There may be a specific setting that causes it.
You can export/import app settings which should include tags. Does that not work?
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.
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 @mikrotik@mikrotik.social) 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 ›
🤔 Please let me know if it comes back! And you can double check the version you're running in the about app page.
I'll kick off a release for this fix rn.