Teknevra

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.

Hello everyone,

Has anyone ever considered potentially building or launching a platform similar to the Internet Archive but using ActivityPub?

This could serve as a decentralized network to document, preserve, and protect online content from loss, censorship, and other threats, ensuring its availability for future generations.

For those unfamiliar, the Internet Archive is a non-profit that has been preserving digital media and promoting universal access to knowledge since 1996.

It’s famous for services like the Wayback Machine and Archive-It.

Given the importance of preserving digital heritage, especially in the context of censorship and data loss, a Fediverse-based equivalent could fill a crucial role.

The decentralized nature of ActivityPub could provide a robust alternative to centralized solutions.

I'd love to see this kind of project come to life, but, unfortunately, I lack the motivation, time, and energy to take it on alone.

Has anyone else ever considered something similar?

Are there any existing projects that might be interested in this direction?

Internet Archive Wikipedia

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.

I was wondering if there exists a platform similar to Downdetector or Down For Everyone Or Just Me (downforeveryoneorjustme.com), but specifically designed for the Fediverse and utilizing ActivityPub?

These platforms allow users to check if a website is down or if it's a personal connectivity issue.

• Downdetector (https://downdetector.com/):

is a tool that aggregates reports of outages across various services (e.g., internet, social media, streaming platforms) to help users determine if an issue is widespread or isolated.

• Down For Everyone Or Just Me (https://downforeveryoneorjustme.com/):

is a simple service that checks if a website is down for everyone or just the person trying to access it.

If such a platform does not exist for the Fediverse, should we consider creating one?

It would be INCREDIBLY useful for monitoring instance(platform uptime and diagnosing connectivity issues within our community.

Unfortunately, I personally lack the time, energy, and motivation to initiate this project, but I believe it could be a valuable resource for all of us.

If anyone is interested in developing such a service, I personally believe that it could enhance our overall Fediverse experience EXPONENTIALLY.

This might just be me, but I’ve recently been wondering—has anyone ever floated the idea of potentially creating a decentralized and/or federated alternative to the browser engines dominating the market?

Right now, it feels like options are increasingly monopolized, with Google Chromium (Blink) being the backbone of almost every browser, and Mozilla’s Gecko engine fighting to hold on.

While platforms like Mastodon, Lemmy, and others prove that decentralization/federation can work remarkably well for social media, could this model apply to browser engines or even search platform ecosystems?

Maybe something open and community-driven that allows different stakeholders or communities to innovate independently while ensuring compatibility standards?

I recognize this would be a monumental challenge, requiring deep technical expertise, time, and resources.

I’d love to explore it myself, but I just don’t have the energy, time, or knowledge to get such a thing off the ground.

However, I’m hoping to hear if anyone has had similar thoughts, knows of any related projects in development, or has ideas about how this could work.

Imagine a world where browser developers aren’t forced to rely on Google’s Chromium, and instead, we could have a crowd-sourced federated system where each contributor could bring something unique to the table without centralized control.

Would this even be feasible?

What do you think?

Is it worth dreaming about, or are there insurmountable hurdles that make such an initiative unrealistic?

Looking forward to hearing everyone’s thoughts.

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.

Consider creating and sharing video updates about the development progress of Loops and Pixelfed on popular social media platforms like YouTube, Twitch, TikTok, etc.

Rationale:

1. Increased visibility: Platforms like YouTube and TikTok have MASSIVE user bases, providing an opportunity to reach potential new users who may not be familiar with Loops or Pixelfed.

2. Engaging content format: Video content is highly engaging and can effectively showcase new features, UI improvements, and behind-the-scenes development processes.

3. Building community: Regular updates can help foster a sense of community and excitement among existing users, keeping them informed and involved in the project's progress.

4. Inspiration from others: Some developers are already using this approach successfully. For example:

   • Skylight Social (ATProtocol-based app): https://www.tiktok.com/@buildwithtori
   • Neptune (potential TikTok alternative): https://www.tiktok.com/@theneptuneapp

These creators are effectively using TikTok to document their development journey and build interest in their projects.

By adopting a similar strategy, Loops and Pixelfed could:

• Provide regular progress updates to the community
• Showcase new features and improvements
• Offer sneak peeks of upcoming developments
• Share insights into the development process
• Engage with users through comments and feedback

I personally believe that this approach could SIGNIFICANTLY boost awareness of Loops and Pixelfed while keeping the existing community engaged and excited about the project's future.

I've been thinking about how we could potentially enhance the Lemmy experience, and I wonder if anyone else sees potential in incorporating a feature similar to Bluesky's Custom Feeds or Mastodon's Fedialgo?

Here's my thought process:

Why Custom Feeds?

User Empowerment: Custom feeds allow users to tailor their experience, moving beyond the limitations of chronological or "popular" sorting.

Discovery: They can help users find content and communities they might not encounter otherwise.

Flexibility: Users could create feeds based on specific interests, keywords, or even complex criteria.

New User Onboarding: Many new users join Lemmy from algorithm-driven platforms like Xitter, Reddit, Tiktok, Instagram, Bluesky, etc. and may find the manual nature of Lemmy's current feed system limiting. Custom feeds could help to smooth that transition.

Bluesky's Approach

Bluesky's implementation of Custom Feeds is particularly interesting:

Users can create and share their own algorithm-driven feeds

It promotes algorithmic transparency and user choice

The feature has been well-received for its innovative approach to content curation

https://bsky.social/about/blog/7-27-2023-custom-feeds

https://bsky.social/about/blog/3-30-2023-algorithmic-choice

https://www.theverge.com/2023/5/26/23739174/bluesky-custom-feeds-algorithms-twitter-alternative

Mastodon's Fedialgo

Alternatively, we could look at Fedialgo, which:

Allows for custom feed creation within the Mastodon ecosystem

Is open-source and federated, aligning well with Lemmy's principles

https://github.com/ronilaukkarinen/fedialgo

Potential Implementation for Lemmy

User-Created Algorithms: Allow users to define their own feed algorithms using a simple interface.

Shareable Feeds: Enable users to share their custom feeds, fostering community curation.

Integration with Lemmy's Existing Features: Ensure the custom feeds work well with Lemmy's communities and cross-instance functionality.

Open-Source Approach: Keep the feature open-source and possibly federated, in line with Lemmy's ethos.

I, unfortunately, do not have the time, energy, or knowledge to be able to attempt something like this.

What do you all think?

Could this be a valuable addition to Lemmy?

I'd love to hear your thoughts, concerns, or ideas for potential implementation.

I've been thinking about how we could potentially enhance the Lemmy experience, and I wonder if anyone else sees potential in incorporating a feature similar to Bluesky's Custom Feeds or Mastodon's Fedialgo?

Here's my thought process:

Why Custom Feeds?

1. User Empowerment: Custom feeds allow users to tailor their experience, moving beyond the limitations of chronological or "popular" sorting.

2. Discovery: They can help users find content and communities they might not encounter otherwise.

3. Flexibility: Users could create feeds based on specific interests, keywords, or even complex criteria.

Bluesky's Approach

Bluesky's implementation of Custom Feeds is particularly interesting:

• Users can create and share their own algorithm-driven feeds
• It promotes algorithmic transparency and user choice
• The feature has been well-received for its innovative approach to content curation

https://bsky.social/about/blog/7-27-2023-custom-feeds

https://bsky.social/about/blog/3-30-2023-algorithmic-choice

https://www.theverge.com/2023/5/26/23739174/bluesky-custom-feeds-algorithms-twitter-alternative

Mastodon's Fedialgo

Alternatively, we could look at Fedialgo, which:

• Allows for custom feed creation within the Mastodon ecosystem
• Is open-source and federated, aligning well with Lemmy's principles

https://github.com/ronilaukkarinen/fedialgo

Potential Implementation for Lemmy

1. User-Created Algorithms: Allow users to define their own feed algorithms using a simple interface.

2. Shareable Feeds: Enable users to share their custom feeds, fostering community curation.

3. Integration with Lemmy's Existing Features: Ensure the custom feeds work well with Lemmy's communities and cross-instance functionality.

4. Open-Source Approach: Keep the feature open-source and possibly federated, in line with Lemmy's ethos.

I, unfortunately, do not have the time, energy, or knowledge to be able to attempt something like this.

What do you all think?

Could this be a valuable addition to Lemmy?

I'd love to hear your thoughts, concerns, or ideas for potential implementation.

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