We’ve been working on adding (alpha) PieFed support to the Interstellar app for the past few weeks, and it has finally been released.
Keep in mind that the API is currently limited in its capabilities, and we were not able to implement all the features Interstellar provides; this is the case wherever you see a screen or pop-up message that says “Unimplemented” error. Additionally, the alpha API could easily change at any moment, so don’t expect it to work without issues.
If you’d like to try it out despite it being an “alpha” feature, then when you go to sign-in, enter preferred.social
as the Instance Host. See this post (https://piefed.social/post/484755) if you’d like more information about that instance and general PieFed API info.
Hi, just testing. I’m writing this from Interstellar on Piefed.
Awesome!
Oh, now I can’t comment from Piefed anymore.
I got “ClientException: Request failed with status 400: REQUEST: ('error”: " 429 Too Many Requests" when I tried to submit my comment.
Now I’m getting “type ‘Null’ is not a subtype of type 'String” in the comment area when opening the post.
My original comment was:
Notifications don’t seem to work. I’m getting “UnimplementedError” when viewing them.
And the post body text is missing when I open a post. When I tap upvote, the post body text appears.
Not complaining, only pointing out some things I’ve noticed. I’m happy there’s a second app for Piefed in development.
I have no idea why you’d trigger the rate limiter by posting a comment, but it seems like you did.
Thank you, I’ll look into it. I’m seeing the same thing as well from my PieFed account.
Yeah, that’s just one of those screens that doesn’t work yet. There’s just no API routes for notifications yet. I’ll certainly add support once PieFed has it though.
It’s possible this is an issue with the PieFed API, but I’ll certainly check this as well, just to make sure.
No problem at all! The whole reason I’ve released it is so people can thoroughly test both the app and the API for bugs.
@[email protected] I looked into it, and it seems both the issues you found (null error visiting this post, and empty body) are issues with the API, so it should just be something the PieFed devs need to fix on their end. (So I won’t need to make a whole new release to fix it, luckily)
Ah nice. Thanks for looking into it!
@[email protected] has swiftly fixed both issues with the API, so they should both be good now!
Awesome. I can confirm, post body text is visible now.
Amazing ⚡
Congratulations, test failed successfully