Your First Landing Isn't Always The Best
Your First Landing Isn't Always The Best


Any piefed instances that block out the tankie triad?
Your First Landing Isn't Always The Best
Any piefed instances that block out the tankie triad?
You're viewing a single thread.
I really like piefed but my choice of instance feels really incomplete. The ability to post images in comments is broken, for example, it just displays this:
[]https://)
I also can't preview a comment before posting and the notifications looks like trash where most of the message is hidden and once cleared there is no "view all" they're just gone forever. Also, the "context" button from a specific comment's url isn't there.
But I still really like piefed, can't wait for it to improve.
Social doesn't seem to have any of those issues, if you're curious.
I believe Rimu has noted that unreleased beta code is running on .social . Might be the reason, and a good sign of things coming to the other instances soon.
Images in comments is planned for a future release (probably 1.3). It's on version 1.1 right now.
Considering how young the project is I think it's really good already. Room for improvement of course, but very good.
Image upload for comments etc is coming soon. Already tagged for version 1.3:
https://codeberg.org/rimu/pyfedi/issues/284
Previews work on my recently deployed 1.1.2, perhaps .world is behind a minor.
Yay ! Now clients need to implement language switching
My piefed (.ca) UN gets far fewer and less diverse feeds, browsing under all>scaled, hot, not sure what's up but the votes are different, it federates differently, sees some, doesn't see others...
It’s probably as a result of less community subs to federate the content from having a smaller userbase.
It’d also be great if the Voyager app could support Piefed. I’m using the Blorp app as a compromise but it’s missing a lot of quality of life things that Voyager has.
Voyager supports Piefed now!
Source: Posted this on Voyager
The app tells me “Voyager doesn't support signups via Piefed right now, apologies!”
Click the "Log In" button instead of the "Join" button.
Voyager makes it a bit confusing, highlighting the join button instead of login which is used more often.
Works now, thanks!
I think this question was about login, but just FYI, PieFed doesn’t support registrations via the API yet. So I wouldn’t expect any 3rd party PieFed client to support signup. But login works.
Blorp dev here. I know you probably switched to voyager, but I’d love to know what you’re missing most from my app. Preferably organized by priority.
Voyager is also a solid app.
These are things that I couldn’t find any way to do in Blorp. It could be that they already are features but I just missed them or I ran into a bug. I’ve also not fully tested all of these with the newest app update.
• embed images in comments (this seems to be working with the newest app update)
• compact posts in feed
• remembering default sort for each community (as in, the app should remember that I want Community X to sort by New by default and I want Community Y to sort by Hot by default, and I want these to be independent of how the overall feed is sorted by default)
• block communities/users/instances (I think this was a bug; it seems to be working with the newest app update)
• attaching links in comments doesn’t always affix the link to the correct letters. It’s also annoying how the pop up box to add the text and link jumps upward when I tap on either text box to type (also, “Description” is misspelled).
• I’d like to be able to see the modlog for each community/instance/user (including myself) while within the app. I don’t think Voyager even has this feature.
• The search-within-a-community function seems to be broken on both Blorp and Voyager for Piefed and instead searches all of the Fediverse
• Voyager isolates each link within somebody’s comment at the bottom of the comment. This makes it easier to select the links and to see which text has which link.
Right now, Voyager doesn’t seem to properly block all NSFW posts for Piefed browsing (it works for Lemmy browsing), whereas Blorp does seem to work for that.
I appreciate your effort to make a better app experience!
Affixing the link to the comment can definitely be improved. Though I’m not sure I exactly understand it not affixing to the correct letters. It should affix to the selection?
Previously, if the text with the link attached was too long, the last few letters of the text would not have the link attached. I’m not able to replicate this issue anymore so it might have gotten fixed.
However, if I add text with a link attached and press OK in the pop up box, and then afterwards type text that I do not want the link to be attached to, all text that follows has the link attached.
Ooo that is really annoying. It looks like I can either have it not add to/extend a link at all when your cursor is at the end of a link, or I can have punctuation/a space terminate the link. Which makes more sense? Hopefully I explained that well.
Edit: I think I know what to do. I’m also going to look into adding community/user auto completing as you type their name in a comment. That’s something that’s missing that annoys me.