UPDATE June 29: Piefed support is rolling out to the official store listings today in v2.37.0 ๐ŸŽ‰

I'm excited to announce that Voyager now has experimental support for logging in with Piefed! You can try it out today on:

This will roll out to the official app stores and vger.app soon(tm), once Iโ€™m confident there are no major regressions. If you prefer not to switch to beta builds, just hang tight.

Please note that Piefed support is EXPERIMENTAL! There are still many things that don't work quite right, which I'm hoping to improve over the coming weeks.

The basics including scrolling home/all/local, viewing posts, blocking, commenting and voting should work well. However there are some known issues:

  • Can't sign up for a Piefed account in-app, only log in with an existing one
  • Subscribed communities list is empty (should be fixed soon!)
  • Inbox tab doesn't load
  • Comment search doesn't work
  • Profile upvoted/downvoted doesn't load
  • No moderation tools
  • Mark as read doesn't persist
  • Creating/editing posts is currently untested
  • ...probably a bunch of other stuff too, please let me know below!

Behind the scenes, this interoperability is made possible thanks to aeharding/threadiverse, a new library I am working on to normalize various threadiverse-software APIs. It's open source so any project use it, but it's under heavy development right now. What's cool about this is in the future, adding support for mbin, or whatever else is possible!

Again, feel free to try it out and let me know if there are any more issues to be documented and fixed.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] 5 points 1 year ago (39 children)

I'm unable to log in with my existing piefed.ca account (which works with the interstellar app).

No real explanation given, just a generic error.

Haven't used voyager before, so it's not an older app or missing update, I went straight into the beta.

  • source
  • hideshow 39 child comments
  • [โ€“] [S] 4 points 1 year ago (38 children)

    Piefed.ca may be running a slightly outdated build of Piefed, but it's hard to tell because Piefed isn't versioned yet. Do you know an admin you could ask?

  • source
  • parent
  • hideshow 38 child comments
  • [โ€“] 6 points 1 year ago (9 children)

    Piefed.ca now upgraded to 1.0.0

    I believe they had just updated to 1.0.0 yesterday. And I believe this is the same version that piefed.social is running on as well.

    When I try using the web app version of the beta, I am able to see all the piefed servers (.social, .world, .blahaj.zone, etc) but I am still unable to connect to piefed.ca.

  • source
  • parent
  • hideshow 9 child comments
  • [โ€“] 5 points 1 year ago (5 children)

    I did an upgrade last night, but just did another one again. Try now?

  • source
  • parent
  • hideshow 5 child comments
  • [โ€“] 1 point 1 year ago (4 children)

    Just gave it a shot and I am having the same error.

  • source
  • parent
  • hideshow 4 child comments
  • [โ€“] 2 points 1 year ago (3 children)
  • [โ€“] 3 points 1 year ago (2 children)
  • [โ€“] 2 points 1 year ago (27 children)

    I think I'm on the same discord as one of the admins, let me check.

    I'm getting the same error with piefed.social though, just tested - I don't have an account there, but the error comes when I select the server, before even being promoted to enter my credentials.

  • source
  • parent
  • hideshow 27 child comments
  • [โ€“] [S] 3 points 1 year ago (26 children)

    piefed.social should be fine, that's what I've been testing with! I'll keep my eyes out though.

  • source
  • parent
  • hideshow 26 child comments
  • [โ€“] 2 points 1 year ago (18 children)

    I just got an update from google play this morning, though the version number is still 2.37.0, and I still get the error. On both piefed.social and .ca, no idea. I don't even get to the login screen, the error comes when I select the server and click "next".

    Tested logging in to Lemmy, which worked just fine - sending this very comment through Voyager.

    Would it help if I share my logs?

  • source
  • parent
  • hideshow 18 child comments
  • [โ€“] [S] 1 point 1 year ago (17 children)

    .ca has known issues. .social should work though. What build number do you see on the About page?

  • source
  • parent
  • hideshow 17 child comments
  • [โ€“] 3 points 1 year ago (15 children)

    piefed.social

    preferred.social

    What surprises me most is that using interstellar, I can log in to piefed.ca just fine:

    interstellar - piefed.ca

  • source
  • parent
  • hideshow 15 child comments
  • [โ€“] [S] 3 points 1 year ago (13 children)

    Try build 698, just released :)

    Should fix piefed.social. ca still has known issues with admin array not returned for some reason

  • source
  • parent
  • hideshow 13 child comments
  • [โ€“] 2 points 1 year ago (7 children)

    Hope I'm not spamming - in 703 (just updated) I now get to the login mask on piefed.ca, but then get a connection error when trying to actually log in. But hey, progress!

  • source
  • parent
  • hideshow 7 child comments
  • [โ€“] [S] 1 point 1 year ago (6 children)

    Not at all. thanks for letting me know (that was the hope of making the original post!) try the next build coming down in a sec

  • source
  • parent
  • hideshow 6 child comments
  • [โ€“] 2 points 1 year ago* (5 children)

    Woohoo, it works! With the limitations mentioned, but login and viewing at least is supported. And in a second I'll know if I can comment :-)

    Edit: Looks like I can. Awesome!

  • source
  • parent
  • hideshow 5 child comments
  • [โ€“] [S] 3 points 1 year ago (4 children)
  • [โ€“] 1 point 1 year ago (3 children)

    By the way, is it too soon to post issues for piefed on the github tracker (or here?), since it's still early stages anyway and stuff is knowingly borked?

  • source
  • parent
  • hideshow 3 child comments
  • [โ€“] [S] 1 point 1 year ago (2 children)
  • [โ€“] 1 point 1 year ago (2 children)

    I've updated to latest beta and all piefed instances besides blahaj are throwing the same error for me now.

  • source
  • parent
  • hideshow 2 child comments
  • [+] 2 points 1 year ago* (last edited 1 year ago) (5 children)
  • [โ€“] [S] 3 points 1 year ago (4 children)

    How strange. Only other thing I can think of is Piefed will rate limit API logins, to 6 per hour. After that it will fail.

  • source
  • parent
  • hideshow 4 child comments
  • [โ€“] 4 points 1 year ago (3 children)

    That seems low. I've increased it to 20 per hour.

  • source
  • parent
  • hideshow 3 child comments
  • [โ€“] 1 point 1 year ago (2 children)

    Are those login attempts per user, or overall API logins?

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] 1 point 1 year ago* (last edited 1 year ago)

    So I can get to the login page on preferred.social, which is the piefed testing instances with all the newest features, there I get the voyager popup that support is experimental etc., so maybe that can rule out device/general connectivity issues?

  • source
  • parent