81
[Release][v1.67.4] Add support for PieFed
(lemmy.world)
You're a fucking legend, thank you so much :D
Congratulations, I'll take it for a spin.
Edit: once Google play has the latest
Should be fully released now!
This could be huge, especially for getting people off Reddit and onto the Threadiverse. It's unfortunate that Lemmy has the political baggage it does, but here we are. So if people are recommending Piefed instead and they now also have a super polished app to suggest, I can see that being a very positive factor.
That was awfully quick. Do you even sleep at all?
8 hours every day :D. But Imy sleep schedule is really messed up. ๐
Awesome, thank you!!!
Yay! I'm so glad to be back. Moved to piefed when lemm.ee went down. Feels like I'm home again ๐
Thank you !
I updated earlier today and haven't been able to use lemmy.zip at all - just gives network error.
Just tested Lemmy.Zip on my device and it worked fine. Can you confirm that you are able to access https://lemmy.zip/ without issues?
Also what is the exact network error? Eg. Is it a no internet connection error?
Works fine from web browser and Voyager on the same device and connection.
Trying to load my feed it just spins for as long as I leave it open, but if I minimize the app and come back it says: Network Error. Please check your internet connection and try again. It occurs on both WiFi and mobile data.
If I try to view my inbox, instance info, or web settings I additionally get an error detail link with the message: Response was not 200. Response code: 504. Url: https://lemmy.zip/api/v4/site
Pulling up that specific url in my browser fails, but with a 404 instead of a 504.
[Edit] tried logging out and logging back in, and logging in gives the same 504 from the API url
Oh what the. For some reason, the app thinks lemmy.zip is using Lemmy API v4 when it's not. I'll dig more into this.
Oh I just realized that you are getting a 504, not a 404. This means that the lemmy.zip server isn't returning anything back.
Can you try changing the user-agent, then restart the app and see if that fixes the issue?
To change the user-agent, go to Settings > Misc > Client user-agent. I would try Test user-agent and Test user-agent 2 first but you should try them all until it works.
For whatever reason 1.67.4 seems to have resolved things? Maybe just the app actually restarting was the fix. I'll definitely give the user agent switch a try if I see the same issue again.
Following up on this one, I am still seeing this issue intermittently, but doing a force stop and restarting the app does fix it.
Very odd
As best as I can tell, it looks like the app being dormant for an extended period is the most likely trigger for me.
Trying to login to piefed.social, gives me Client Error. Code: 400: Message: incorrect_login. Im sure its correct because I logged in on the web app to write this comment with the same info
I just tested signing into both piefed.world and piefed.social with two different accounts, different usernames and passwords and both worked. Can you triple check to verify?
update I signed up for another account on piefed.social just to triple check and I was able to sign into that one too.
Update 2 tried signing in with user name and also with email separately and confirmed both work.
I made a new account and it worked. So I can only assume it was an issue with this account, maybe because of its 128 character password? I only used 60 characters for the new one. Im not sure.
Ah yeah, the password length was the issue. Summit truncates to 60 characters because it was a limit for Lemmy apparently. I'll can do a dot release in a bit.
I ran into the same problem with my lemmy account months ago, not being able to log in there too without a reset. Should stop using 128 as a default lol. Thanks for being on top of it.
I can test with a 128 char password in a bit.
Editing comments after posting doesn't seem to work. Comment box flashes but still shows the original comment.
Urg. I blame PieFed for this one. The API documentation clearly says that Posts and Comment objects have a field named updated but the server actually returns it as edited_at. This value is used by the client to determine if a post/comment needs to be re-rendered.
Update Will fix in a patch update.
I wanted to suggest a small UI/UX tweak that might help streamline the posting experience.
Currently, when creating a post, Summit displays a horizontal formatting bar above the keyboard with options like:
Italic
Bold
Numbered List
Spoiler Text
Text Emojis
Add Link
Add Image
(etc.)
While this is functional, having to swipe through the bar to find the desired option can feel a bit clunky, especially on smaller screens or when you're quickly trying to format something.
My Suggestion:
Instead of a swipeable bar, what if there was a single expandable button above the keyboard? When tapped, it could expand into a radial menu (or option wheel). The most commonly used options (like Bold, Italic, Image, etc.) could be placed in the center circle, with the rest arranged around it in an outer ring. Think of it as a compact, gesture-friendly hub for quick formatting.
This could:
Reduce screen clutter
Speed up post composition
Be more visually intuitive for users already familiar with similar UIs in mobile games or design apps
The app currently offers a way to reorder the list of formatting options as a solution for this problem. I think most screens, even the smallest ones, can easily fit 7 different formatting options. If you want easier access to formatting tools you use often you can reorder the tools so tools you often use are at the front of the list. If there is any particular reason you cannot do this or if there is a different use case let me know.
My "All subscribed" feed contain posts from several non-subscribed communities when logged into piefed.zip.
There seems to be an issue with the mobile API at the moment: https://piefed.zip/post/223804
Yep, that sounds exactly like what I'm seeing.
On another note, reading your reply in the Summit inbox and tapping on "go to post" in the context section results in the following error:
Client error. Code: 400. Message: missing parameters for post.
Seems like at least the first issue has been fixed 20 minutes ago: https://piefed.zip/post/223804#comment_512392
Will fix in a patch update.
The cause for this one is PieFed doesn't behave like Lemmy. For the Lemmy API, you can navigate to a post using comment ID alone. PieFed requires a post id and a comment id.
Moved over from the PieFed PWA and pretty happy with the speed and stability.
It looks like the PieFed deduplication doesn't happen in Summit yet? Not sure if the means the detection happens outside of the API, and would thus be hard to implement in an app?
Yeah it's not supported at the moment. I'll add this request to the roadmap.
Great work!
Only bug I experience at the moment is that I can't edit my comments on any Lemmy community.
It always fails with
[...] code 400, key:"
But nothing is written in after that quote sign.
I can't reproduce this bug on my end. I'm creating a test account on your instant just in case. Can you confirm which version of the app you are using?
Interesting. I can confirm I can reproduce the bug but only on your instance. Looking into the issue now...
Found a fix. Will find some time to release the fix.
Wow thanks, that was much faster than I anticipated!
Unable to post images to communities/instances.
Whenever I try, I always get this message:
Server error. Code: 500. Message: {"files":null,"msg":"ffprobe Failed with exit status: 1"}.
No matter the post / community / instance.
There was a bug in the v1.67.1 release that was fixed in v1.67.2. Can you confirm of you are using v1.67.2 of the app?
Nevermind, i just checked, and the app wasn't updated.
I was still on v1.67.1.
Which is weird, because when I opened the app, it said that it had updated.
Anyways, I just updated, and now it's working fine.
Cheers ๐ฅ
Attempting to add new account and log into piefed.world:
Parameter specified as non-null is null: method com.idunnololz.summit.api.PieFedApiAlphaAdapter.H, parameter
I can't reproduce this crash. I also don't see it logged on my end. Not much I can do without more information unforuntately.
Can you reproduce the crash 100% of the time?
Yeah, I've been trying to figure out what I can do to maybe get something to change. Only thing I can think of now is to export my settings then reset the app.
Cleared all app data and even reinstalled the app. Issue persists.
Unfortunately, I don't have the time to get a proper debug log. Maybe next week or so.
this post was submitted on 16 Jul 2025
81 points (100.0% liked)
Summit
1095 readers
34 users here now
Community to discuss Summit, an open-source Lemmy reader for Android.
App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit
APK: https://github.com/idunnololz/summit-for-lemmy/releases
Source: https://github.com/idunnololz/summit
Support the app
Website: https://summit.idunnololz.com/
founded 2 years ago
MODERATORS