Teknevra

I wanted to bring to your attention a feature from Voyager for Lemmy that could be a valuable addition to Thunder.

Voyager has a "Migrate Subreddits" tool designed SPECIFICALLY for Reddit users transitioning to Lemmy.

This tool streamlines the migration process by helping users easily find communities on Lemmy that are similar to the subreddits they've subscribed to on Reddit.

The process in Voyager is straightforward:

1. Users log in to their Reddit account and access their subscription list via the "multireddit of your subscriptions" link available in the sidebar.
2. They copy the link and paste it into Voyager, allowing the tool to automatically search for corresponding communities on Lemmy.

This feature significantly lowers the friction for users migrating to a new platform by minimizing the effort required to find and rebuild their communities.

Has Thunder ever considered incorporating a similar "Migrate Communities" feature?

It could be an excellent addition to assist new users transitioning from Reddit, making it easier for them to rediscover and reconnect with the communities they care about most.

Such a feature could also enhance Thunder's onboarding process and attract a growing audience of users exploring alternative platforms.

If this is something Thunder could implement, it might be worth exploring further.

Image of "Migrate Subreddits" Feature on Voyager:

EDIT:

The way that it works is: when you enter the Multireddit link, it will show up like this:

And if you then tap on the link that you just added, you will get this:

And then, if you tap on one of them, depending on whether or not there is a Lemmy community alternative to the subreddit: you will either get this:

This:

Or this:

I wanted to bring to your attention a feature from Voyager for Lemmy that could be a valuable addition to Boost.

Voyager has a "Migrate Subreddits" tool designed SPECIFICALLY for Reddit users transitioning to Lemmy.

This tool streamlines the migration process by helping users easily find communities on Lemmy that are similar to the subreddits they've subscribed to on Reddit.

The process in Voyager is straightforward:

1. Users log in to their Reddit account and access their subscription list via the "multireddit of your subscriptions" link available in the sidebar.
2. They copy the link and paste it into Voyager, allowing the tool to automatically search for corresponding communities on Lemmy.

This feature significantly lowers the friction for users migrating to a new platform by minimizing the effort required to find and rebuild their communities.

Has Boost ever considered incorporating a similar "Migrate Communities" feature?

It could be an excellent addition to assist new users transitioning from Reddit, making it easier for them to rediscover and reconnect with the communities they care about most.

Such a feature could also enhance Boost's onboarding process and attract a growing audience of users exploring alternative platforms.

If this is something Boost could implement, it might be worth exploring further.

Image of "Migrate Subreddits" Feature on Voyager:

EDIT:

The way that it works is: when you enter the Multireddit link, it will show up like this:

And if you then tap on the link that you just added, you will get this:

And then, if you tap on one of them, depending on whether or not there is a Lemmy community alternative to the subreddit: you will either get this:

This:

Or this:

As an Android user, I have been enjoying Summit via the Play Store, and have also explored the GitHub APK option.

However, I was curious if Summit has ever considered the potential possibility of expanding Summit to the iOS platform?

This would likely appeal to a broader audience and open up more opportunities for users across different ecosystems.

Currently, Summit is well-represented on the Android side, and considering iOS compatibility could enhance its reach and user base SIGNIFICANTLY.

I personally believe that this would be a strategic move to grow Summit's presence in the mobile app market.

I wanted to bring to your attention a feature from Voyager for Lemmy that could be a valuable addition to Summit.

Voyager has a "Migrate Subreddits" tool designed SPECIFICALLY for Reddit users transitioning to Lemmy.

This tool streamlines the migration process by helping users easily find communities on Lemmy that are similar to the subreddits they've subscribed to on Reddit.

The process in Voyager is straightforward:

1. Users log in to their Reddit account and access their subscription list via the "multireddit of your subscriptions" link available in the sidebar.
2. They copy the link and paste it into Voyager, allowing the tool to automatically search for corresponding communities on Lemmy.

This feature significantly lowers the friction for users migrating to a new platform by minimizing the effort required to find and rebuild their communities.

Has Summit ever considered incorporating a similar "Migrate Communities" feature?

It could be an excellent addition to assist new users transitioning from Reddit, making it easier for them to rediscover and reconnect with the communities they care about most.

Such a feature could also enhance Summit's onboarding process and attract a growing audience of users exploring alternative platforms.

If this is something Summit could implement, it might be worth exploring further.

Image of "Migrate Subreddits" Feature on Voyager:

EDIT:

The way that it works is: when you enter the Multireddit link, it will show up like this:

And if you then tap on the link that you just added, you will get this:

And then, if you tap on one of them, depending on whether or not there is a Lemmy community alternative to the subreddit: you will either get this:

This:

Or this:

Description:

When users on Summit tap on a post with an image on their mobile devices, it would significantly enhance the user experience if they could swipe upwards to directly navigate to the comments section of that post. This interaction would be similar to how Reddit handles navigation for image posts.

Benefits:

1. Streamlined Navigation: Users can quickly move from viewing the image to reading and engaging with comments, creating a more fluid and interactive experience.
2. User-Friendly Interface: This feature aligns with intuitive swipe gestures that are common in mobile apps, making Summit more accessible and user-friendly.
3. Enhanced Engagement: By simplifying the path to comments, this feature encourages more users to participate in discussions, thereby fostering a more vibrant community.

Implementation Details:

• Swipe Gesture: When a user is viewing an image post on mobile and swipes upwards, the app should transition smoothly to the comments section of the post.
• Visual Cue: Optionally, a subtle visual cue (e.g., a small upward arrow at the bottom of the screen) could be added to indicate this swipe action.
• Animation: The transition should be smooth and visually pleasing, minimizing any abrupt changes.

Impact on Existing Features:

This feature would complement existing navigation and post interaction methods without altering them, ensuring consistency across the app’s interface.

By incorporating this feature, Summit can improve its usability and create a more engaging experience for its users, aligning with the intuitive expectations set by other popular social media platforms.

I was curious, has idunnololz ever considered potentially bringing in volunteers to help contribute to Summit's code or assist with other tasks?

idunnololz could potentially put out a “call for volunteers” on platforms like Lemmy, Reddit, or other relevant platforms/communities, with a focus on people who are passionate about what Summit is doing.

Benefits:

• Reduced burden on idunnololz: By involving more developers, the primary workload wouldn't fall solely on one person.

• Diverse skill sets: Volunteers might bring specialized skills that could benefit specific areas of the app.

• Community engagement: This initiative would foster a stronger connection between Summit and its user base.

• Faster development: More hands on deck could potentially speed up feature implementation and bug fixes.

While you may not be in a position to offer monetary compensation, these volunteers could benefit in other ways:

• Gaining valuable coding experience by contributing to a live project.
• Earning recognition or "special contributor" status within the app or community.
• Access to exclusive features or perks as a form of gratitude for their contributions.
• Exclusive beta access to new features
• Potential for future paid opportunities as the project grows
• Credit in the app's "About" section
• Certificates of contribution for their portfolios

This could potentially foster a stronger community around Summit and help it grow even faster by leveraging the skills and knowledge of passionate supporters.

Of course, there will likely need to be some structure (e.g., guidance, pull request reviews, clear documentation) to make this work smoothly, but it might be a worthwhile avenue to explore.

Whenever I attempt to upload a photo, I always get this message:

UNABLE TO UPLOAD IMAGE DUE TO AN UNKOWN ISSUE

Server error. Code: 500

No matter if I attempt it via URL, via the post itself, etc.

Current Situation

Currently, all notifications, including private messages (PMs), and general notifications,, are grouped together in the main Inbox section. While this centralized approach has its merits, it can sometimes lead to important personal messages getting lost in the mix of other notifications.

Proposed Feature

I would like to suggest the introduction of a separate section SPECIFICALLY for PMs, similar to the model used by Reddit. This new feature would involve:

1. Creating a distinct "Messages", "Private Messages", "Chat", etc. section within the app
2. Separating PM notifications from other types of notifications (post replies, mentions, etc.)
3. Potentially adding a new notification icon or badge specifically for private messages

Benefits

Implementing this feature could offer several advantages:

• Improved organization and clarity for users
• Easier access to private conversations
• Enhanced privacy, as personal messages would be separate from public interactions
• Potential for more robust PM features in the future

User Experience

This change would allow users to quickly distinguish between general notifications and personal messages, potentially leading to faster response times for private communications and a more streamlined experience overall.

Conclusion

I personally believe that this feature would be a valuable addition to Summit for Lemmy, aligning it more closely with user expectations shaped by other popular social platforms while maintaining its unique identity.

Has Summit ever considered potentially implementing customizable navigation styles for Summit?

Specifically, allowing users to choose how they navigate the app based on their preferences and device usage habits. Here are some ideas:

1. Bottom Navigation
   A streamlined, easy-to-access navigation bar at the bottom of the app. This is especially popular for users on modern smartphones, as it keeps key functionality within thumb’s reach.

2. Drawer Navigation
   A sidebar/drawer navigation option for users who prefer a more traditional setup where the main menu can be hidden until needed.

3. Combination of Both
   The option to use both bottom navigation and drawer navigation for those who enjoy having simultaneous access to tools and settings.

4. Other Layouts
   Consider potentially exploring other navigation paradigms, such as gesture-based navigation or tab-based navigation.

Why This Feature Matters

Customizable navigation styles can enhance usability, adapt to different user preferences, and improve accessibility for those with varying needs. For example:

• Users with larger phones may prefer bottom navigation for easier reach.
• Some might prefer drawer navigation for a cleaner interface.
• Offering both options lets users tailor their experience.

Additional Considerations

• Settings Menu: Users could configure their preferred navigation type from the app settings.
• Default Option: Choose a default layout that works for most users.
• Consistency: Maintain design consistency so that each navigation type supports all app features seamlessly.

I personally believe that this addition would make Summit even more versatile and user-friendly, empowering users to interact with Lemmy in the way that feels most natural to them.

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.