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.
I love literally everything about this announcement.
I want to try other fedi platforms but have MAJOR inertia thanks to apps.
So Iβm fucking thrilled the one I prefer also wants to prefer all the things
Brb ima spin up an account. I fucking love you voyager, and everything your team does (I assume itβs a team? If not I love you very specifically. Yes you. I love you.)
This is awesome, thank you for your hard work! Lack of Voyager support for Piefed was the only thing holding me back - piefed.blahaj.zone, here I come!
If Iβm not mistaken when you install the TestFlight version it replaces the stable App Store version. For those with the App Store version installed you can use the PWA at the same time without disturbing your main setup.
Backing up settings and restoring them works too. Just mentioning an another way in case it helps someone.
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?
I've tested PieFed out for a bit, and I like what they have going on. It uses ActivityPub, just like Mastadon or Lemmy. It's mostly similar to Lemmy, but it has some additional features that are awesome:
Feeds - In PieFed you can combine multiple communities into a single feed (makes it so much easier to browse through all of the different c/technology posts from Lemmy.world, lemmy.zip, Beehaw, programming.dev, etc.).
Crosspost View - If a post has been crossposted, scrolling through the comments is organized into sections from each community that the post was crossposted into.
Delayed posting - Set a future time for when you want your post/comment to be posted.
Post tagging - Ability to tag a post as a spoiler, discussion, question/answered etc.
That's the goal. Especially since the compat lib is separate, I'm hoping to get it mature enough to the point that it could eventually be community maintained.
Iβve noticed link images are very pixelated when browsing piefed (piefed.social specifically) but then same links look fine when browsing lemmy. Iβm guessing this is a piefed side problem (or maybe an instance configuration choice?).
Yesterday I merged in a PR that lets the instance admin set the sizes for thumbnails.
But the real issue is that the thumbnails have a variety of uses - in the PieFed web UI thumbnails are shown quite small so 170px is fine. But some mobile apps might show the thumbnail in a manner that spans the whole screen which is going to need to be at least 350px wide.
I'll make PieFed generate a 500px version of the thumbnail and include that in the API response (as well as the smaller one).
Thank you I was picking the server 1st not login. Now it just keeps saying connection error (either way). Tried both username and email and pasted password cuz I am old with 2 cataracts ;-).
When I went to do the iOS TestFlight it asked me if I want to replace existing Voyager, you may loose all your data. I donβt want to lose my data. Can someone testing let me know if all your data does get deleted or not?
Before you install the TestFlight beta you can go to Voyager>Settings>Backup and Restore Settings. Save the .json in Files app and it can be used to put your App Store version back to how it is now. Iβm not sure how well the import setting works in the TestFlight version so I canβt speak to that.
Alternatively, you can keep the current app the way it is and install the beta PWA then use them simultaneously. Youβll have to adjust settings to your liking but this way if you decide not to continue using the beta you just delete the PWA.