Skip Navigation

Posts
14
Comments
230
Joined
2 yr. ago

Punch nazis, trebuchet TERFs.

I am building Voyager, a client for lemmy!

  • I haven't been able to repro, works fine for me, android+piefed.zip+viewing ich_iel. Have you tried asking the feddit.org admins? Maybe you could send them your IP and they could investigate the logs. Its possible they are blocking the user agent/ip. Voyager should send "VoyagerApp" somewhere in the user agent for the native apps.

  • Right? Jellyfin is awesome

  • Sorry, I fucked that up! Will fix ASAP

    edit: Fix is in 2.38.0, building right now

  • Deleted

    Permanently Deleted

    Jump
  • yes.

  • It is a piefed.ca issue. Piefed.ca is running an outdated version of Piefed that doesn’t support voyager’s in app linking.

  • 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

  • So fuck your tunnels, fuck your cars, fuck your rockets, fuck your cars againYou promised you'd be Tesla, but you're just another Edison'Cause Tesla broke a patent, all you ever broke were heartsI can't believe you tore humanity apartWith the very same machines that could have been our brand new start

    https://www.youtube.com/watch?v=LpxT9TLGoLI

  • Ah, that works, but this doesn't:

     html
        
    <!-- Save this as test-cors.html and open in a browser -->
    <!DOCTYPE html>
    <html>
      <body>
        <script>
          fetch("https://piefed.social/comment/6527914", {
            method: "GET", // or "POST", etc.
            headers: {
              "Content-Type": "application/json",
              Accept: "application/activity+json",
            },
          })
            .then((response) => response.text())
            .then((data) => console.log("Success:", data))
            .catch((error) => console.error("CORS Error:", error));
        </script>
      </body>
    </html>
    
      

    nor this:

     html
        
    <!-- Save this as test-cors.html and open in a browser -->
    <!DOCTYPE html>
    <html>
      <body>
        <script>
          fetch("https://piefed.social/.well-known/nodeinfo", {
            method: "GET", // or "POST", etc.
            headers: {
              "Content-Type": "application/json",
              Accept: "application/activity+json",
            },
          })
            .then((response) => response.text())
            .then((data) => console.log("Success:", data))
            .catch((error) => console.error("CORS Error:", error));
        </script>
      </body>
    </html>
    
      
  • I checked piefed.social and I'm still getting CORS errors. Does the change still have yet to be deployed there?

  • Nice, thanks! I’ll try it again soon

  • I could see that argument, but I also wanted to pick the best instance for most people, not necessarily an instance that works in every country with every shitty law. We're all volunteers here.

    And I might change in the future, or create a way for the app to chose a fallback default instance for a better user experience.

  • Are you on iOS or android? It should automatically strip the getvoyager part on paste into comment

  • Cool :)

  • Are you the bot author? If so have you considered using Lemmys alt text field directly? This would display the text with the image is some clients like voyager. It would also federate to Mastodon (post body doesn’t federate). You could also keep the text in the post body and do it both places :)

  • Where did you hear this? Voyager has excellent markdown support with an implementation that closely matches Lemmy-ui.

  • Oh, thanks. I was checking the login page but I just checked the signup page and there is indeed many missing instances!

    Voyager pulls instance data from Lemmy-explorer API, and so there must be an issue right now. I opened a bug: https://github.com/tgxn/lemmy-explorer/issues/225