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™, 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.
piefed.social should be fine, that’s what I’ve been testing with! I’ll keep my eyes out though.
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?
i’m having the same issue with piefed.social, i reset my password and double checked logging in with the web worked.
having the same issue at piefed.blahaj.zone so might be my device. This is so cool thank you so much just knowing it’s gonna happen is delightful.
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.
That seems low. I’ve increased it to 20 per hour.
Are those login attempts per user, or overall API logins?
Per IP address.
In that case this shouldn’t have been an issue, I tried from my home wifi and mobile without VPN, and nobody else in my household is using PieFed or Lemmy.
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?
.ca has known issues. .social should work though. What build number do you see on the About page?
What surprises me most is that using interstellar, I can log in to piefed.ca just fine:
Same as you, I was not able to log into my instance on Voyager but can when using Interstellar
Try build 698, just released :)
Should fix piefed.social. ca still has known issues with admin array not returned for some reason
Will do as soon as it’s available for me, can’t see it on the play store yet. Thanks!
Updated to 698, no changes on my end - both .social and .ca throw the error message just like before :-/
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!
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
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!
Yay!!
Beta Track [697] d0aef95