Teknevra

Do you think Lemmy should introduce a feature allowing the head moderator of a community to transfer ownership to another moderator, similar to Discord's server ownership transfer functionality?

What advantages and challenges do you foresee with implementing such a system, and how might it impact community governance and continuity on the platform?

Would adding this feature help foster stronger community management dynamics, or could it lead to potential misuse or instability in some cases?

How might Lemmy balance flexibility for moderators with safeguards to ensure fair and consistent ownership transfers?

As many of you may know, Reddit's r/place is a popular social experiment that allows users to collaborate on a massive digital canvas by placing one pixel every few minutes. It fostered community engagement, creativity, and even some friendly competition between different groups.

Given Lemmy's focus on community-driven content and open-source principles, I'm curious about your thoughts on potentially introducing a similar feature:

Questions:

1. Do you think a Lemmy version of r/place would be beneficial for our platform? Why or why not?
2. How could such a feature be implemented in a way that aligns with Lemmy's values and decentralized structure?
3. What potential challenges or drawbacks do you foresee with introducing this type of collaborative art project?
4. If implemented, how often should such an event occur? Annually, quarterly, or as a one-time experiment?
5. What unique twists or improvements could Lemmy add to make this feature stand out from Reddit's version?

I was curious—has anyone ever thought about attempting a Fediverse-based alternative app store? Something that embraces the decentralized, federated philosophy but applies it to distributing apps.

Imagine an app store combining the best ideas of platforms like F-Droid, AltStore, Aptoide, or Aurora Store, but with the following Fediverse twist:

• Federation: App repositories could be hosted on independent servers that communicate, similar to Mastodon instances, Lemmy, or PeerTube.
• Openness: Developers could host their own apps on their servers, or join community-based app hubs.
• Community Moderation: Users could rate, review, and verify apps collectively to ensure safety and quality.
• Decentralized Privacy: No centralized tracking or data collection—apps could exist in line with the privacy values many of us in the Fediverse cherish.
• Cross-Platform Focus: Not just Android or iOS—this could support Linux desktop, custom ROMs, or a potential future Fediverse OS.

Drawing inspiration from existing app stores like:

• Aurora Store (privacy-focused),
• Aptoide (community-driven recommendations),
• AltStore/Scarlet (sideloading and modded apps),
• F-Droid (free and open-source apps with community involvement),
• or even BuildStore (subscription-based security assurance),

a federated app store could offer something revolutionary in contrast to the monopoly of Google Play/Apple App Store.

Potential Names for This Hypothetical App Store:

1. FedApps – Simple and straight to the point.
2. Appiverse – Merging "App" and "Fediverse" to highlight its federated nature.
3. DecentraStore – Emphasizing decentralization as the core concept.
4. OpenWave – Suggesting an open and free flow of apps across the Fediverse.
5. AppHaven – A safe haven for apps, rooted in community trust.
6. LibreStore – Inspired by "libre," pointing to freedom and openness.
7. FediHub – A central hub for apps, aligned with the federated ecosystem.
8. CommApps – Highlighting the community-driven aspect of the store.
9. NodeStore – Tying it to the networked nature of federated nodes.

Questions for the community:

1. Would something like this align with the ethos of the Fediverse?
2. What would the technical hurdles look like—building decentralized repositories, ensuring verification, and avoiding malicious apps?
3. How would we overcome the challenge of making this accessible to non-technical users? Could it scale to mainstream use?
4. Could such a platform serve as a foundation if the Fediverse community ever developed its own federated operating systems?
5. And just for fun: If you were to create this app store, what features or design principles would be must-haves?

I’d love to see something like this, but I unfortunately have neither the time nor the technical know-how to take it on. However, the idea of a community-driven alternative app ecosystem feels like it could be a natural evolution of the Fediverse’s decentralized ethos.

EDIT: If a federated app store DID gain traction, it could potentially plant the seeds for future Fediverse-powered devices—phones, tablets, PCs, etc. Imagine an entirely federated tech stack.

Looking forward to hearing your thoughts, ideas, and feedback.

Summary:
Please add a feature to Boost 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 Boost for Lemmy for individuals managing multiple accounts. It ensures no notifications go unnoticed and streamlines workflow across accounts, aligning with Boost’s goal of making Lemmy more user-friendly and efficient.

Seamless Navigation from Image Posts to Comments

Description:

When users on Lemmy 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 Lemmy 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, Lemmy 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.

Overview

I would like to propose adding an interactive user profile image feature to Voyager for Lemmy, enhancing the user experience when viewing other users' profiles.

Detailed Functionality

1. Tappable Profile Image Section

   • When users tap on a username and navigate to the profile page, add a dedicated section for the profile image.
   • This section should be prominently displayed and easily accessible.

2. Expandable Image View

   • Implement a feature allowing users to click/tap on the profile image to expand it to a larger view.
   • The expanded view should occupy a significant portion of the screen for better visibility.

3. Mobile Zoom Functionality

   • On mobile devices, enable pinch-to-zoom functionality for the expanded profile image.
   • This allows users to examine profile pictures in greater detail.

4. Desktop Zoom Controls

   • For desktop users, add a dedicated zoom control bar.
   • Include buttons or a slider for zooming in and out of the profile image.

User Experience Benefits

• Improved user engagement with profile content
• Enhanced ability to view and appreciate user avatars and profile pictures
• Consistent functionality across mobile and desktop platforms

Implementation Considerations

• Ensure smooth transitions when expanding/collapsing images
• Optimize image loading to maintain performance
• Consider privacy settings that might affect image visibility

I personally believe that this feature would significantly enhance user interaction and personalization within the Voyager for Lemmy platform.

Perhaps something like this:

(Source: Summit for Lemny)

In the "Summit for Lemmy" app, if you go to a community that you moderate, click on the three dots in the bottom right corner:

then when the Community options pops up:

tap on "Community Info":

Which will give you the "Unsubscribe" / "Instance Info" options, as well as the community Header/Profile Image, Description, Stats, etc.

If you then tap the three dots in the bottom right corner, you end up with the option to edit /delete the community.

PLEASE add a feature similar to the Community Edit/Delete for Voyager.

In the "Thunder for Lemmy" app, when you share a Community/User/Comment, when you tap / click on the share button, a pop-up appears, asking you whether you wish to share via:

https,

via Community Link,

via Home Instance (if applicable),

share Post Image (if applicable),

share Post Media Link (if Applicable),

an Advanced Option (if Applicable),

(Advanced Sharing)

etc.

PLEASE PLEASE incorporate a similar feature into Voyager.

It would make sharing a hell of a lot easier.

I have been attempting to help Reddit Subreddits migrate over to Lemmy, and so far, it has been pretty good.

But one of the of the Subreddits is Religion Based and when I went to JoinLemmy, and clicked on "Join a Server", there is no Religion option.

There is a Religion tab, and you can choose what language, but, after that, it just shows that there are no Religion based Servers, regardless of the language that is chosen.

EDIT: OpenChristian is now up.

I've been exploring various Fediverse platforms and noticed we have alternatives for many popular social media sites:

• Friendica (Facebook-like)
• Pixelfed (Instagram-like)
• Lemmy (Reddit-like)
• Mastodon (Twitter-like)
• etc.

But I'm curious: Is there a Fediverse equivalent to the classic MySpace, or its modern revival, Spacehey?

Spacehey Apple App Store

Spacehey Google Play Store

Spacehey Wikipedia

MySpace

MySpace Wikipedia

I'm talking about a platform that offers:

• Highly customizable profiles
• A focus on personal expression through layout and design
• Music integration
• The nostalgic feel of early 2000s social networking
• etc.

Has anyone come across a project like this in the Fediverse? Or do you think there's potential for developing such a platform?

Alternatively, if that's too much work/hassle, has anyone ever considered reaching out to the SpaceHey team about the possibility of them potentially federating their platform? It could be an interesting addition to the Fediverse ecosystem.

There's been some talk about Spacehey Federation.

I'd love to hear your thoughts, experiences, or any leads on this topic.

Does anyone else feel like the Fediverse could potentially use a centralized, clear, and engaging way to introduce itself and its platforms to new users?

I’ve noticed a recurring trend: on Reddit, YouTube, and other platforms, there are constant questions like "What is the Fediverse?" or "How does Mastodon/Lemmy/Pixelfed work?"

While it’s great to see so much interest, these questions can become repetitive, and they highlight the need for a more accessible and official introduction to the Fediverse.

What I’m proposing is The FediGuide—a centralized, interactive, and approachable platform or website designed to explain what the Fediverse is, how ActivityPub works, and what its platforms (like Mastodon, Lemmy, Pixelfed, etc.) are all about. Here’s how The FediGuide could look and function:

Key Features of The FediGuide

1. Interactive, Child-Friendly Design

• The FediGuide should be so simple and visually appealing that even a five-year-old could grasp the concepts. Think:

  • Bright visuals
  • Interactive animations
  • Step-by-step explanations
  • Simple, jargon-free language

  It should feel as welcoming as picking up a colorful amusement park brochure or summer camp guide.

2. Centralized Hub for Information

• The FediGuide could serve as a one-stop resource for anyone curious about:

  • What the Fediverse is
  • The differences between Fediverse platforms (Mastodon, Lemmy, Pixelfed, etc.)
  • How to join and use these platforms
  • The concept of ActivityPub and why it matters
  • Comparisons to centralized platforms like Facebook/Reddit/Instagram

• It could also include video tutorials, either normal Youtube/PeerTube videos, or ones similar to interactive training videos you see at workplaces for employees, infographics, and even community-generated FAQs to clarify common concerns.

3. Interactive Tutorial Platform

• The FediGuide could take inspiration from onboarding tools like:

  • Guided tutorials that mimic real-world actions (e.g., "Here’s how you create your first post on Mastodon!")
  • Engaging quizzes like “Which Fediverse platform is right for you?”

• For a truly immersive experience, it could be built as a fediverse-based platform itself, where users could "try out" ActivityPub principles in action.

4. A Fediverse-Based Clippy

• Imagine a friendly, helpful virtual assistant (think Clippy from Microsoft Word) that pops up on different platforms to explain features and answer user questions. For example:

  • Someone joins Mastodon for the first time → the assistant helps them learn the interface and suggests accounts to follow.
  • The assistant could live on The FediGuide website but also integrate with Fediverse apps.

  This assistant could provide context-sensitive help and guide users toward relevant parts of the Fediverse.

Maybe name it Fred if it's a boy, and Fredi if it's a girl, or something similar.

5. Easy to Share and Reference

• The FediGuide should be easy to reference and share, with:
  • A memorable name and URL (e.g., “www.TheFediGuide.org”)
  • Compatibility with multiple languages, ensuring accessibility for a global audience.
  • Integration within Fediverse platforms, where users can easily point others toward the resource.

Why This is Needed:

1. The Learning Curve: While the Fediverse is an exciting decentralized alternative, its concepts can be intimidating or confusing for new users.
2. Constant Repetition: People across various platforms keep asking the same questions, which suggests the need for an official, consistent source of answers.
3. Community Growth: Making the Fediverse easier to understand will lower barriers to entry, helping it grow and thrive.

Potential Obstacles and Solutions

• Obstacle: Many Fediverse projects are run by volunteers with limited resources.

  • Solution: The community could work together to crowdsource the content and development of The FediGuide. Alternatively, organizations backing the Fediverse (e.g., Mastodon gGmbH, Pixelfed, etc.) could potentially allocate resources to this idea.

• Obstacle: Ensuring the information remains up-to-date as platforms evolve.

  • Solution: Treat The FediGuide as an open-source project, with regular contributions and updates from the community.

Potential Next Steps'

If this idea resonates, here’s how something like this might potentially move forward:

1. Gather Feedback: Discuss what features or content would be most helpful. Would a website, platform, or both work best? How simple/interactive should it be?
2. Identify Developers & Contributors: Call for volunteers or organizations in the Fediverse ecosystem to support this idea.
3. Choose a Platform: Decide whether The FediGuide will be a standalone website, an ActivityPub-based app, or both.
4. Launch in Phases: Start with a basic explainer website, then add interactive features like tutorials, a Clippy-style assistant, or even gamified learning modules.

What do you all think?

Does The FediGuide feel like a useful addition to the Fediverse?

I would consider doing something like this, but, unfortunately, I do not have the time, energy, or knowledge.

Hey everyone,

I’ve been thinking about how the Fediverse handles user accounts and logins for a while now, and I had a question.

Right now, users have to create accounts on specific instances on various platforms, which works but can sometimes feel a bit fragmented—especially when someone wants to interact across multiple instances or migrate to a new one.

Would it make more sense for the Fediverse to adopt a login system based on encrypted keys, like how NOSTR operates (or something similar)?

In such a system, users could have a single "universal" private key that serves as their identity across the network.

Here are some potential benefits I see:

• Single Identity Across Instances: Users wouldn't need to create multiple accounts for each instance, making it easier to interact across the Fediverse.
• Seamless Migration: If your home instance shuts down or you switch to another one, your identity and data could remain intact since it’s tied to your key, not the instance.
• Decentralization Boost: It might make the Fediverse feel even more decentralized, as user identities wouldn’t depend on a specific instance's infrastructure.
• Improved Privacy: Keys could also enable stronger controls over data sharing and access at the individual level.

Of course, there are likely challenges to this approach, such as handling lost keys, onboarding non-technical users, or ensuring compatibility with existing protocols.

But it seems like a conversation worth having.

What does the community think?

Are there reasons this wouldn’t work for the Fediverse, or could this idea help address some existing pain points?

Looking forward to hearing your thoughts.

EDIT:

I suggested this over on r/Fediverse and a Redditor gave me this:

https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

https://microformats.org/wiki/rel-me

So I guess that it is being worked on Fediverse - wise.

https://nostr.com/get-starthtml

https://www.nostr-ruby.com/core/keys.html