Teknevra

Randomly, when posting, I will get this message:

Stating that there is an Instance Mismatch.

It also happens on other accounts, as well.

The weird part about it is that both of them are the same Instance, just that one is Capitized.

I wasn't sure if this was a bug, or what.

Currently, users need to visit the Lemmy server website each time that they want to create a new community.

While this works well enough, it can feel a bit inconvenient and disrupts the otherwise smooth mobile experience your app provides.

By adding a Community Creator section to Summit, users would be able to:

• Quickly and easily create new communities without leaving the app.
• Customize the settings, descriptions, and rules of their community directly from their mobile device.
• Enjoy a streamlined experience that matches the interaction they’re already used to in the Summit app.

This would not only improve the overall user experience but also encourage users to create new communities and engage more deeply with the Lemmy ecosystem.

I would like to propose an enhancement to the user dashboard on Summit for Lemmy to improve the handling and presentation of deleted posts.

Currently, when a user deletes a post, it remains in their dashboard’s list of posts with a small red dustbin icon, and tapping on the post displays a deletion notice at the bottom.

While this feature provides transparency, it can lead to clutter and confusion for users managing their content.

Below is a detailed request for improvement.

Current Issues:

1. Deleted Posts Still Visible in Dashboard:

   • Deleted posts remain listed alongside active posts in the "Posts" section of the user dashboard, creating unnecessary clutter.
   • The red dustbin icon indicates deletion, but the post remains interactable and visually indistinguishable from active content.

2. Federation-Specific Challenges:

   • Due to Lemmy's federated architecture, deleted posts may still appear across federated instances, but the local dashboard behavior can be optimized for clarity.

Proposed Enhancements:

1. Remove Deleted Posts from the Main "Posts" Section:

   • Once a post is deleted, it should no longer appear in the main list of posts on the user dashboard. This will improve the user's ability to manage and view existing content.

2. Add a Separate "Deleted Posts" Section:

   • Introduce a new tab or section in the user dashboard labeled "Deleted" (or something similar) alongside the existing "Posts," "Comments," and "About" sections. This section could:
     • Display all deleted posts in one place.
     • Provide transparency for users to review their deleted content if needed.
     • Allow users to access and potentially manage metadata about these deleted posts.

3. Ensure Clear Visibility of Deletion Status:

   • Within the "Deleted" section, posts can retain a deletion indicator (e.g., the dustbin icon) along with a clear notice explaining the federated nature of Lemmy and why the post may still appear elsewhere.

Benefits of Implementation:

1. Improved User Experience:

   • Users will have an organized and decluttered dashboard, making it easier to manage active content without deleted posts interfering.

2. Enhanced Transparency:

   • The dedicated "Deleted" section provides users with a clear overview of their deleted content while reinforcing Lemmy’s federated limitations on complete deletion.

3. Alignment with Federated Principles:

   • Acknowledging the challenges of deletion across federated instances, this solution balances clarity with technical feasibility.

Suggested Implementation Notes:

• The "Deleted" section should emphasize that while posts are marked as deleted locally, content might persist in federated instances due to the limitations of the ActivityPub protocol.
• Consider providing an additional warning during deletion to ensure users understand this federation-specific behavior.

Thank you for considering this feature request.

I personally believe that these changes will SIGNIFICANTLY enhance the usability of the user dashboard while addressing user concerns about managing deleted posts.

Request Details

In the Reddit/Discord-style side taskbar where users can see the communities they are subscribed to, I would llike to suggest adding a separate section specifically for communities that users moderate. This would create a clearer distinction between communities users participate in and those that they manage.

Proposed Layout

• Community Subscriptions: This section would continue to display all the communities that a user is subscribed to, as it currently does.
• Moderated Communities: A new section that would list all the communities for which the user has moderation powers. This would help moderators quickly navigate to the communities they need to manage.

Benefits

1. Improved Organization: Moderators would be able to quickly identify and access communities they manage, reducing time spent searching.
2. Enhanced User Experience: This organization would help reduce clutter and improve navigation for both moderators and users alike.
3. Efficiency: Moderators could more efficiently fulfill their roles by having their managed communities highlighted separately.

Thank you for considering this feature request. I personally believe that it would GREATLY benefit users and moderators on your platform.

Summary:
Please add a feature to Summit for Lemmy where, if a user is logged in with multiple accounts, they receive a visual indicator (e.g., a symbol, badge, or number) on the inactive accounts when a new notification or inbox message arrives on them. This would help users quickly identify that they have notifications on other accounts without needing to manually check each one.

Problem:
For users managing multiple Lemmy accounts (e.g., for different communities or purposes), it’s easy to miss notifications or messages on inactive accounts when they’re logged into just one. Currently, users need to switch between accounts periodically to check for activity, which is both inconvenient and easy to overlook.

Proposed Solution:
Introduce a cross-account notification system where:

• When logged into Account A, and a new notification or inbox message arrives on Account B, a small indicator (like a numbered badge or icon) appears next to Account B in the account-switching menu.
• The badge could display the number of unread notifications or simply alert users that attention is needed on the other account.

Benefits:

• Improved User Experience: Users don't have to "guess" if there's activity on their other accounts.
• Increased Engagement: Notifications will ensure users are prompt in responding, especially if the other account is for managing a community.
• Time-Saving: Users can focus on one account without manually checking others unless they know there’s something pending.

Optional Features:

• Customizable Notifications: Users can toggle cross-account notifications on/off for specific accounts.
• Sound/Push Alerts: Optionally allow a subtle sound, vibration, or push notification when activity is detected on inactive accounts.

Conclusion:
This small enhancement would GREATLY improve the usability of Summit for Lemmy for individuals managing multiple accounts. It ensures no notifications go unnoticed and streamlines workflow across accounts, aligning with Summit's goal of making Lemmy more user-friendly and efficient.

I was curious:

Have you ever considered potentially incorporating some of the highly-praised UX elements, theming capabilities, and overall user experience from Sync for Lemmy into Summit?

Many users, including myself, have found Sync's interface and customization options to be exceptional, as well as leagues ahead of the competition (no offence).

However, there are concerns in the Sync community about Sync's closed-source nature, as well as the developer's loonngg periods of inactivity.

Given Summit's open-source ethos and active development, do you see an opportunity to potentially fill this gap by bringing some of Sync's most loved features to Summit, while maintaining your commitment to transparency and regular updates?

If done right, Summit could potentially become the new Sync, but open-source, and with active updates.

I'm curious about your thoughts on this, and whether or not it aligns with your vision for Summit's future development.

I'd like to start a discussion about a potential feature for our platform.

As someone who moderates religious-based communities here on Lemmy, I've encountered a recurring issue: frequent brigading by anti-religious users.

This got me thinking about community management options.

Currently, Lemmy allows communities to be public or mod-only.

However, I personally believe that Lemmy could potentially benefit from additional options similar to those available on Reddit:

1. Restricted Communities: Where anyone can view, but only approved members can post/comment.
2. Private Communities: Where only approved members can view and participate.

Questions for discussion:

• Do you think these additional privacy options would be beneficial for Lemmy?
• How might this impact the overall user experience and community dynamics?
• Could this help address issues like brigading in sensitive topic areas?
• Are there potential downsides or concerns about implementing such features?
• How would this align with Lemmy's philosophy and goals as a platform?

I'm interested in hearing your thoughts, experiences, and perspectives on this matter.