33
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Mar 2025
33 points (100.0% liked)
PieFed Meta
587 readers
1 users here now
Discuss PieFed project direction, provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics.
Wiki
founded 1 year ago
MODERATORS
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.
@squirrel@discuss.tchncs.de 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!
@freamon@preferred.social 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