130

Experimental Piefed support is now available for Voyager (vger.social)

submitted 3 weeks ago* (last edited 2 weeks ago) by aeharding@vger.social to c/voyagerapp@lemmy.world

74 comments fedilink hide all child comments

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.

(page 2) 24 comments

sorted by: hot top controversial new old

[-] viking@infosec.pub 1 points 3 weeks ago

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.

[-] aeharding@vger.social 0 points 3 weeks ago

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?

[-] mintiefresh@lemmy.ca 1 points 3 weeks ago

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.

[-] Shadow@lemmy.ca 0 points 3 weeks ago

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

[-] mintiefresh@lemmy.ca 0 points 3 weeks ago

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

[-] Shadow@lemmy.ca 1 points 3 weeks ago

@rimu@piefed.social help? =)

[-] Blaze@lemmy.dbzer0.com 0 points 2 weeks ago

Seems like it works now!

[-] Shadow@lemmy.ca 1 points 2 weeks ago

Weird, I haven't done anything....

load more comments (1 replies)

[-] viking@infosec.pub 0 points 3 weeks ago

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.

[-] aeharding@vger.social 0 points 3 weeks ago

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

[-] sprite0@sh.itjust.works 0 points 3 weeks ago* (last edited 3 weeks ago)

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.

[-] aeharding@vger.social 0 points 3 weeks ago

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.

[-] rimu@piefed.social 0 points 2 weeks ago

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

[-] viking@infosec.pub 0 points 2 weeks ago

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

load more comments (2 replies)

[-] viking@infosec.pub 0 points 2 weeks ago* (last edited 2 weeks 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?

[-] viking@infosec.pub 0 points 2 weeks ago

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?

[-] aeharding@vger.social 0 points 2 weeks ago

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

load more comments (11 replies)

[-] fievel@lemmy.zip 1 points 3 weeks ago

Is there a way to access it with Obtainium (e. g. github project releases) or F-droid?

Thanks this is a great project.

[-] RedstoneValley@sh.itjust.works 1 points 3 weeks ago

This might be the wrong place to ask. But anyway, can someone please explain the difference between Lemmy and PieFed to me? I've searched a bit and it seems that both are doing roughly the same thing, but with a different fediverse protocol or something?

load more comments (2 replies)

[-] Luci@lemmy.ca 1 points 3 weeks ago

Great! I can make the switch off lemmy now!!

load more comments