Summit

I don't normally care about my cakeday, but I was confused.

I recently created this Piefed.World account (within this year), but it's telling me that my CakeDay is January 27, 2026, 348 days from now.

I posted it on the Piefed Support Community , and was told that it was a glitch in the app.

On Reddit, moderators can comment as regular users by default, and only display the green MOD badge when they intentionally “distinguish” a comment as an official moderation response.

It made me think about how this works across the Fediverse — particularly with PieFed.

PieFed supports opt-in mod distinction, allowing moderators to choose when they’re speaking officially versus when they’re just participating in a discussion as a regular community member.

That distinction can meaningfully affect tone, power dynamics, and how comfortable users feel engaging in open conversation.

By contrast, Lemmy (at least currently) does not support this feature at the protocol level, so this suggestion is not for Lemmy users.

Feature Suggestion (PieFed Users Only)

Would it be possible for Summit to support PieFed’s opt-in moderator distinction system?

Specifically:

Allow PieFed moderators to comment as regular users by default

Provide a clear, intentional toggle to mark a comment as “mod voice” when speaking officially

This would:

Help preserve conversational tone when Piefed mods are participating casually

Reduce unintentional authority signaling

Maintain transparency when acting in an official capacity

To be clear, this request applies only to PieFed users, since Lemmy does not (at least not currently) support this capability.

EDIT: Apparently Lemmy now supports the feature?

Or at least Lemmy.world does?

cross-posted from: https://lemmy.ca/post/60201661

cross-posted from: https://lemmy.ca/post/59348743

When using spoiler tags, if you add bold/italic formatting to the title, the title is hidden as part of the spoiler in Jerboa, instead of being rendered as a title with bold/italics.

Regular spoiler

Regular spoiler

Bold Title

Bold title

Italic Title

Italic title

The example that brought me here:

https://lemmy.ca/comment/21351153

Cross posted, because it seems Boost suffers from the same problem: not rendering bold/italic spoiler titles correctly.

Cross-posted as Summit also suffers from this issue.

Are there any updates on this issue? I run into it daily and it's definitely limiting the content I can access. I know it's been an ongoing bug so wanted to see if there was any update on resolving it. I didn't see anything in the release notes or recent posts.

Clicking here and changing instance to .world so I can answer to it, takes too long

Have you ever considered potentially adding support for Mbin, alongside the already existing Lemmy and Piefed login/support options?

I don’t personally use Mbin, but it struck me that supporting it could be interesting from an ecosystem standpoint — essentially completing the “trinity” of major ActivityPub-based forum platforms:

• Lemmy
• Piefed
• Mbin

Even if Mbin support isn’t a priority right now, I thought it might be worth floating as a future consideration, especially for users who like to move between different Fediverse ecosystems while keeping a single client.

I just downloaded summit. I can vote and do other things but I couldnt comment.

Here's the error:

LemmyAction failed. Cause: com.idunnololz.summit.lemmy.actions.LemmyActionFailureReason.UnknownError. Details: UnknownError(errorCode=401, errorMessage=Not signed in)

after some investigating, I tried posting this on the mobile client and saw an error that said im not allowed to post because I am on a VPN. turned my VPN off, tried posting my comment in the app, then it worked.

just thought you should know this error is incorrect and sent me down a rabbit hole. maybe there's something you can do to update this on your end? not sure though...

have a great day! love the app so far

I wanted to suggest a small but potentially impactful UI/UX feature for Summit related to how moderator comments are displayed.

On Lemmy, moderator comments are often visually distinguished by default, even when the moderator is just participating casually rather than speaking in an official moderation capacity.

While this transparency has value, it can sometimes unintentionally shift the tone of a discussion or discourage open conversation when a mod is simply engaging as a regular community member.

After discussing this in lemmy_support@lemmy.ml, it was pointed out that this isn’t really an API limitation, but rather a frontend/app decision — which is why I thought Summit might be a good place to experiment with it.

https://lemmy.world/post/41994121

Feature idea: An optional, opt-in distinction system for mod comments/posts, similar in spirit to Reddit’s “distinguish” feature:

• By default, moderators’ comments (and posts) appear as regular user comments/posts
• Mods can explicitly mark a comment as “mod voice” when speaking in an official capacity
• Summit could optionally provide a toggle or setting for users to:
  • Always show mod badges
  • Only show mod badges on distinguished comments
  • Or keep the current always-visible behavior

This would preserve transparency while giving communities more flexibility in how authority is visually communicated — potentially improving trust, discussion flow, and community health without changing Lemmy’s underlying model.

Summit has received a ton of feature requests over the years. Over time, a group of features began to accumulate that all relied on the app to track some sort of statistic. Whether it was the number of votes per user or the number of times a community was visited, these features can all be derived from tracking events.

User tracking has a bad rep since it's often associated with ads and it's a hot topic when discussing privacy, however the data is undeniably useful. This is why Summit will start to track certain events beginning with the next release. However, rest assured that this data will be stored on the client side only and it will be easy to opt out of.

Changes so far

• Add convenience setting to export settings to share for debugging purposes. This will be available via Settings > Import & Export settings > Copy settings for debugging. Tapping on this option will export your current settings (excluding the database) and copy it to your clipboard for easy sharing.
• Add a local tracking setting to enable/disable local tracking.
• Add local tracking setting page with some stats and an option to delete all local tracking data.
• Add a stats page to the "You" screen that displays some fun stats based on local tracking data.
• Add setting to change the communities listed in the community selector sheet from top communities to frequented communities of the current account.

I like the link preview option. Unfortunately, after opening or copying the link. I need to manually click the X mark to close the link preview. Auto dismiss would make it that much usable.

Development been quiet for a while - any idea is and when Piefed's new reactions will be supported in Summit?

I don't know if the developers designed it on purpose, but I think it's a bad experience.

I had a small UI/UX feature suggestion for Summit that I think could be helpful.

Currently, Summit already does a great job visually distinguishing roles:

• Community Mods are shown in green
• Instance Admin are shown in red

I was wondering if it would be possible to add a distinct colour for the Head Mod / Top Mod of a community.

For example:

• Instance Admin: Red
• Head Mod: Yellow
• Other Mods: Green

Kind of like a stoplight system (red, yellow, green).

This would make it easier at a glance to tell who ultimately runs a community, especially in larger mod teams or when reading mod comments in threads.

Totally optional, but I think it could be a nice improvement.

Trying to log on with 1.75.4 and getting the error in the attached image. My guess is something in my profile but I'm not sure what. Thanks!

Voyager has this feature where it can track the number of times you have upvoted a user's post/comment. A similar feature in summit would be neat.

Hi, title. I don't receive push notifications and if I go to see notifications categories, there aren't any.

• App version: 1.74.1
• Android 16
• OneUI 8.0
• Galaxy S25

Hard to describe this and I don't have recreate steps, but I've noticed multiple times since the last update that even when my feed is set to Subscribed it sometimes shows All instead

Whenever Summit tries to load this post: https://lemmy.zip/post/56684650 the app crashes immediately.

Doesn't matter if it is opened directly or just showing up in the feed.

This release is meant to fix a lot of the issues plaguing the app currently.

Sorry, I am leaving AVIF support out of Summit for the time being (some AVIF images will still be supported by the Android OS). The currently AVIF libraries available for Android all have flaws. Including them may fix some AVIF errors but add others. For the time being it looks like adding an AVIF decoder to the app is not worth it since they are buggy and greatly increase the app size.

~~It's expected that the app will increase in size significantly after this release due to adding AVIF support.~~

~~Lemmy servers have starting to roll out AVIF encoded images. Unfortunately, Android 11 and below do not have built in AVIF decoders. In addition, even on Android 12 and up, AVIF support is not good leading to the issue that AVIF images will fail to load on many devices. To fix this issue, an AVIF decoder is being bundled with the app. AVIF decoders are pretty large in size meaning the app size will grow greatly. However, given the alternative (images not loading) this is probably the better option.~~

~~Note that the AVIF decoder only supports Android 24 and up. Unfortunately if you are using a device older than that then you are out of luck when it comes to AVIF images :(~~

In addition, this release fixes the issue where the post feed will fail to load after loading 10 pages of posts on some instances.

Full changelog

• Add support for downloading avif image files
• Add support for pagination via page cursors.
• Fix a crash when loading comments on Android 9 and below.
• Fix a bug where changing feeds will not fetch the correct post feed.
• Fix a bug where PieFed feeds broke.

Update

~~The approximate size increase of the app on the play store is 5MB. When downloading from Github, the installer size is expected to increase 15MB due to the installer needing to support multiple architectures.~~

Update 2

Found a few bugs with the cursor implementation. In addition some users reported some bugs with it as well. Fixing and releasing as v1.75.1.

• Fix a bug where changing feeds will not fetch the correct post feed.
• Fix a bug where PieFed feeds broke.

Update 3

Found more bugs. Addressing then releasing as v1.75.2.

• Hardcode special rule for sh.itjust.works to not use cursors because it breaks on this instance for some reason.
• Remove AVIF library.

Update 4

Cursors are a lot more buggy than I anticipated. As a result I am disabling pagination using cursors by default as instead offering it as a setting that can be enabled. It will be available as Settings > Misc > Use cursors when loading the post feed.

This change will be released as v1.75.3.

It's slightly amusing that this release set out to fix two major issues that were caused by new Lemmy changes: AVIF images and extremely small limits placed on the max page index and both of the "fixes" implemented in Summit had to be reverted because either of these features appear to be ready. AVIF support on Android specifically appears to be poor and cursors, despite having been around for a while are still too buggy to use for production.

• Default to use page indices for post feed pagination. Add setting to switch to use cursors instead.

Update 5

Releasing a fix for a bad bug.

• Fix a bug where there is a race condition between the community being set and fetching posts which can result in fetching posts for the wrong community.

Every picture that I expand automatically dims along with the text. I thought maybe it was only doing this to posts I had already opened but it does it to new content also.

Any known fix?

When browsing comments, some images do not show when clicked on. Others do not show when clicked on but do show when "preview image" is selected such as the link in this comment.

https://lemmy.dbzer0.com/comment/23620706