Forem: Ebony Louis

5 AI Agents You Need to Know About

Ebony Louis — Mon, 09 Dec 2024 17:30:58 +0000

Artificial Intelligence (AI) is everywhere these days, from powering search engines to creating playlists. For developers like me, AI agents have become indispensable tools—not just for boosting productivity, but for keeping us employed! So to save you the time I spent my free time looking into five popular AI agents—Goose, Replit Agent, Devin, OpenHands, and Swe-Agent-to help you pick the best one for you.

What Are AI Agents?

But first- what are AI Agents? AI agents are software tools designed to execute operations, often without human intervention. Think of them as virtual assistants on steroids—they analyze situations, decide what actions to take, and then handle tasks for you.

These agents can automate workflows, debug code, generate snippets, and more, integrating seamlessly into tools like your terminal or IDE to enable you to work faster and more efficient.

Feature Overview

features	Goose	Replit Agent	Devin	OpenHands	Swe-Agent
Open Source	Yes	No	Yes	Yes	No
Custom LLM Support	Bring Your Own LLM	Fixed LLM (Replit AI)	Limited to GPT-based LLMs	Limited	Fixed LLM
Platform	Terminal, VS Code, IntelliJ	Replit IDE	Terminal	Browser/CLI	IDE/CLI
Key Strength	Flexibility, toolkits, and introspection	IDE integration	Dev-first commands	Multi-language support	Code debugging
Best For	DevOps, multi-tool workflows, customization	Replit-specific tasks	Lightweight coding tasks	Collaboration and tools	Debugging workflows

AI Agents in Detail

Goose

Goose is a flexible, semi-autonomous agent designed for developers who value control and customization. It integrates into your workflow, whether you’re working in the terminal, VS Code, or IntelliJ, and as an open-source tool, it lets you add functionality as needed. Goose also stands out for its ability to support any LLM, making it one of the most versatile options.

Its extensive list of toolkits, ranging from RepoContext to Jira integration, covers a wide range of developer needs. Plus, features like GitHub Actions integration and voice interaction make it a standout choice for those who love flexibility.

Replit Agent

If you’re already living in the Replit ecosystem, Replit Agent will feel like a natural extension of your workflow. It’s built right into the IDE, eliminating any daunting setup steps. The fixed LLM doesn't offer as much flexibility as some other agents, but it’s created specifically for Replit tasks like debugging and pair programming. So if you're a huge Replit Fan than this is the agent for you.

Devin

I love how simple and straightforward Devin is. It's a terminal-first AI agent thats perfect for quick coding task and project automation. It doesn't have all the bells and whistles as some of the other AI agents so for simpler task its perfect. Since it only works in the terminal, along with its simplicity I would reccomed this AI agent to beginners.

OpenHands

OpenHands is also an open-source AI agent that truly makes it easy for collaboration. If you’re working in an environment with diverse programming languages and toolchains, this one is perfect for you. OpenHands is a solid choice for teams that need an AI agent that will help keep everyone on the same page.

Swe-Agent

Swe-Agent the go-to choice for debugging. If you’re dealing with anoying bugs or need an AI agent that thrives in error-heavy environments, this one is perfect for you. With its fixed LLM designed specifically for debugging and strong IDE integration, it’s built to boost productivity which will hopefully make your life easier.

How to Choose Your AI Agent

There’s an AI agent for every kind of developer:

Need flexibility and multi-tool support? Goose’s open-source design offers toolkits and customizable LLM connections.
Living in Replit? Replit Agent feels like a native part of the IDE.
Prefer simplicity? Devin offers a clean, terminal-based experience.
Working with a team? OpenHands brings collaboration and multi-language support.
Fixing bugs? Swe-Agent is the best for debugging troubles.

Final Thoughts

AI agents were created to make your development process smoother, whether you need automation, debugging, or team collaboration. Goose, Replit Agent, Devin, OpenHands, and Swe-Agent each bring something unique to the table. The best choice depends on your workflow, tools, and goals.

For my personal projects, I’ve chosen Goose. I love that its open-source and allows me to bring my own LLM. I’ll be sharing more blog posts about my experience using Goose, so stay tuned!

What about you? Which AI agent are you using or excited to try? Comment below or tweet me your thoughts and let me know if this guide has helped you.

Why Broken Links Are Costing You Brand Deals (And How to Fix It)

Ebony Louis — Tue, 29 Oct 2024 19:56:45 +0000

Have you ever watched a creator’s video and thought, "Where did she get that top?" or "I need that protein powder"? You scroll through the comments, only to see the infamous "link in my bio" comment. You rush to click the link, and you're hit with-page not found 😒. I remember once being so desperate that I took a screenshot of the item and reverse-searched it on Google Images. I found something similar but not what I wanted. SO frustrating. Eventually, I gave up and kept on scrolling.

Now, imagine how many potential sales that creator lost because a third-party platform’s server was down. Their metrics won't even reflect those missed opportunities, making it harder to secure brand deals. Who actually has time for that? That’s when I realized I could use Decentralized Identifiers (DIDs) to create my own decentralized link hub utilizing service endpoints. With this setup, all my links and contact info are stored in one place—owned and controlled by me. Even if a service that houses all my links goes down, my links will always be accessible because they’re not reliant on any external platforms to display them. I’m sharing this in hopes that fellow creators won’t miss out on potential brand deals, and I won't have to cry over a top I never got to buy.

Before I show you exactly how you can create your own decentralized link hub, lets answer some of the questions you're probably asking yourself.

What are Decentralized Identifiers (DIDs)?

So, what exactly is a Decentralized Identifier, or DID? Think of it as your username—the one source of truth for everything you do online—except this one is owned and controlled entirely by you. It’s a unique "address", thats verifiable and doesn’t rely on any central authority like Facebook, Google, or any other service. Instead, DIDs give you the freedom to manage your own identity online, without needing to trust a single platform to store or validate your information.

In the context of a decentralized link hub, your DID becomes the hub for all your important links. It’s not tied to any third-party service, which means you never have to worry about followers scrolling simply because your link page isn't working. When you update your links, you only need to do it once, as they're tied to your DID—so they stay consistent across all your social platforms, giving you full control. When you update your links, they stay up-to-date across the web because again they’re tied to your DID—giving you full control.

How are Service Endpoints going to help me?

Now, let’s cover what service endpoints are. These might sound technical, but they’re actually pretty simple—think of them like your digital address/phone book. Remember those huge yellow books you used to sit on at the hair salon? They were filled with phone numbers and addresses, making it easy to find and contact people. Well, service endpoints are kind of like that, except they’re the digital "addresses" for different parts of your online identity. These could be links to your Instagram profile, website, direct messages, or even your affiliate links.

These endpoints live in your DID document. So instead of relying on centralized services like Linktree, your DID acts as the home for all your important links. So when someone resolves your DID, they can access the service endpoints that you’ve decided to share.

You can also easily update and delete these links anytime you need to again without relying on any third-party platform to keep those connections working.

The fix: let's create a decentralized Link Hub

If you’re more of a visual learner, check out my YouTube short where I show you exactly how. For this example we're going to create a DID with two service endpoints. One pointing to my LinkedIn and the other pointing to my X profile.

Step 1: Import web5/dids package

import {DidDht} from '@web5/dids'

Step 2: Create DID with service endpoints

const myBearerDid = await DidDht.create({
    options:{
        publish: true,
        services: [
            {
                id: 'LinkedIn',
                type: 'professional',
                serviceEndpoint: 'https://www.linkedin.com/in/ebonylouis'
            },
            {
                id: 'X',
                type: 'personal',
                serviceEndpoint: 'https://x.com/EbonyJLouis'
            }
        ]
    }
});

Now that we've created your DID with service endpoints leading to your LinkedIn and X profiles.

Step 3: Lets print our entire DID also know as a BearerDid to see our DID document where these service endpoints can be found:

console.log(myBearerDid)

It is important to never share your full BearerDID, it contains private keys that only you should have access to. The holder of these keys can perform private key operations, like signing data. Check out this Key Management Guide to learn how to properly manage your DID keys.

Output:

my bearerDid BearerDid {
  uri: 'did:dht:auontpd44i6rrzrmwry7hsbq8p5seqo7xyz8tnr7fdygsmhykoey',
  document: {
    id: 'did:dht:auontpd44i6rrzrmwry7hsbq8p5seqo7xyz8tnr7fdygsmhykoey',
    verificationMethod: [ [Object] ],
    authentication: [
      'did:dht:auontpd44i6rrzrmwry7hsbq8p5seqo7xyz8tnr7fdygsmhykoey#0'
    ],
    assertionMethod: [
      'did:dht:auontpd44i6rrzrmwry7hsbq8p5seqo7xyz8tnr7fdygsmhykoey#0'
    ],
    capabilityDelegation: [
      'did:dht:auontpd44i6rrzrmwry7hsbq8p5seqo7xyz8tnr7fdygsmhykoey#0'
    ],
    capabilityInvocation: [
      'did:dht:auontpd44i6rrzrmwry7hsbq8p5seqo7xyz8tnr7fdygsmhykoey#0'
    ],
    service: [ [Object], [Object] ]
  },
  metadata: { published: true, versionId: '1729705713' },
  keyManager: LocalKeyManager {
    _algorithmInstances: Map(1) {
      [class EdDsaAlgorithm extends CryptoAlgorithm] => EdDsaAlgorithm {}
    },
    _keyStore: MemoryStore { store: [Map] }
  }
}

This output contains your DID string(uri) thats your "username" along with the services array and some authentication and verification methods. To learn more refer to this DID Document Guide.

Step 4: Now lets look closely at just our serviceEndpoint array:

console.log("personal link hub", myBearerDid.document.service || "No Services Found");

Output:

decentralized link hub [
  {
    id: 'did:dht:xihb478dd7w9cyj33b6g5cjriuw6drwaxrx9ppf3bwn839pmhi6y#LinkedIn',
    type: 'professional',
    serviceEndpoint: 'https://www.linkedin.com/in/ebonylouis'
  },
  {
    id: 'did:dht:xihb478dd7w9cyj33b6g5cjriuw6drwaxrx9ppf3bwn839pmhi6y#X',
    type: 'personal',
    serviceEndpoint: 'https://x.com/EbonyJLouis'
  }
]

How do I share these links?

Now that your DID is in your bio, how do your followers access your links? It's simple- they just need to resolve your DID to see a full list of your shared links:

The resolving of your DID will differ depending on the DID method used to create the DID. In this example we are using the DHT DID method:

// DID in your bio
const didDhtUri = 'did:dht:xihb478dd7w9cyj33b6g5cjriuw6drwaxrx9ppf3bwn839pmhi6y'

// resolve the DID
const resolvedDhtDid = await DidDht.resolve(didDhtUri);

// access the DID Document's service links
const dhtDidDocument = resolvedDhtDid.didDocument.service;

console.log(dhtDidDocument)

Output:

[
  {
    id: 'did:dht:xihb478dd7w9cyj33b6g5cjriuw6drwaxrx9ppf3bwn839pmhi6y#LinkedIn#LinkedIn',
    type: 'professional',
    serviceEndpoint: [ 'https://www.linkedin.com/in/ebonylouis' ]
  },
  {
    id: 'did:dht:xihb478dd7w9cyj33b6g5cjriuw6drwaxrx9ppf3bwn839pmhi6y#LinkedIn#X',
    type: 'personal',
    serviceEndpoint: [ 'https://x.com/EbonyJLouis' ]
  }
]

As you can see, we’ve succesfully set up our service endpoints to point to both my LinkedIn and X accounts. Now it’s your turn to secure the bag, create your own decentralized Link hub! And if you tweet about it, don’t forget to tag me.

To learn more about Decentralized Identity check out TBD's Docs.

Exciting News!: Introducing Our Recognition Program 🚀

Ebony Louis — Fri, 29 Sep 2023 19:13:14 +0000

Today we unveil something special - our very own Recognition Program! ✨

What's this all about?

This program is our way of expressing our deepest gratitude to each and every one of you. We know that our community thrives because of your dedication and contributions, and it's high time we recognize your amazing efforts.

🏆 The Categories:

We've carefully crafted six categories to celebrate different aspects of our community:

Feedback Champion Award 📣: This category honors the individuals who provide invaluable feedback, helping us improve and grow.
Content Creator Award 🎥: Recognizing the creative minds who share their knowledge through content creation, whether it's articles, videos, or other forms of media.
Community Hero Award 🦸: For those who go above and beyond to support and uplift fellow community members.
Rising Star Award 🌟: Celebrating the newcomers who have made a significant impact in a short amount of time.
New Contributor Award 🆕: Acknowledging those who have recently joined us and made their first contributions.
Docs Wizard Award 📖: Highlighting the experts who excel in documentation, making our resources more accessible and helpful.

🎁 The Rewards:

Each category winner will receive gift cards to our TBD swag shop, where they can choose up to 2 items of their liking. It's our small way of saying THANK YOU for your outstanding contributions.

Not only that, the winners will also be prominently featured on our website's community landing page for everyone to see and celebrate their achievements! 🌟

Announcement Schedule:

For September: To kick us off, winners in each category will be announced on Monday 10/2nd. Each category will have one winner.
Going Forward: Starting from October, there may be more than one winner in each category, and the category names can change upon community request.
Nominations: You can nominate winners for each category during our monthly dedicated Discord thread, held on the second-to-last Friday of every month. Mark your calendars for October's nominations on 10/20th in our #general channel! 🗓️👥

🤗 Community Involvement:

Our community is at the heart of everything we do, and we value your input. This Recognition Program is a collaborative effort, and you have a say in how it evolves. Categories can change based on community feedback, and we encourage you to actively participate in shaping this program.

This is just the beginning, and we can't wait to kick off this journey with you all. Together, let's make our community even more vibrant and supportive than ever before.

Let the Recognition Program commence! 🥳 #RecognitionProgram #CommunityAppreciation

Stay tuned! Who do you think our September recognition winners are going to be? 🤔

Preptember Diaries: Gearing up for hacktoberfest 2023!

Ebony Louis — Wed, 20 Sep 2023 21:44:44 +0000

Hey there, fellow techies! 🍁 With October rolling in, we're greeted by the crisp orange leaves of fall, the comforting aroma of pumpkin spice, and of course, the much-anticipated Hacktoberfest. Whether you're a seasoned contributor or taking your first steps into the world of open-source, there's something for everyone. And guess what? We've got some exciting news!

🎉 We're Participating in Hacktoberfest 2023! 🎉

This October, it's more than just code and commits; we're spicing things up with exclusive rewards. Be among the first 20 to get their PRs merged and snag some exclusive swag from our TBD shop — we're in the midst of uploading new swag! And for a bit of fun competition? Keep track of your contributions with our leaderboard issues. Ready to climb the ranks?

📅 Mark Your Calendars! Our Hacktoberfest Launch event is on October 2nd. Stay in the loop and don't miss out on any of our events by checking our events-and-updates channel regularly.

📌 What is Hacktoberfest?

For the uninitiated, Hacktoberfest is a month-long celebration of open-source software. It's sponsored by DigitalOcean, GitHub, and other partners.

🔗 Newbies Alert!: Check out Hacktoberfest's official site for more details and to register. Registration is from September 26th- October 31st.

Guidelines for Winning at Hacktoberfest:

Topic Check: Contribute to projects that have the hacktoberfest topic. This ensures your PR counts towards the official Hacktoberfest prizes.
Label Insights:
- Starting with an issue labeled hacktoberfest, no-code, or good-first-issue? That's a solid choice.
- Got the hacktoberfest-accepted label on your PR? WOOHOO! One down, three more to go! 🎉
- Got slapped with a spam label? Reevaluate your contribution.
Code and Conduct: Adhere to our code of conduct and ensure your PR aligns with the repository's goals.
Community Vibes: Engage with fellow contributors on our Discord server for all the Hacktoberfest gossips, and a getting started checklist!
Seek Help: If in doubt, don't stress! Connect with the maintainers by commenting on the issue or ping us on Discord.

🎤 From a First-time Contributor:

I remember my first-time contribution jitters. Every step felt like a monumental task, and the fear of making a mistake? Oh boy! Here’s a snippet from my Twitter thread on my first contribution experience:

"... I made all of the changes locally, and then opened a PR. Looked over it a zillion times, because, you know, it's in the public's eye! Yikes! And despite all the caution, I still goofed up my first PR. 🤦🏾‍♀️ But guess what? The community stepped in, guided me, and boom! PR merged. It was .."

You can check out my complete thread and the roller-coaster of emotions I went through here. If I could do it, trust me so can you!

Hot Tip: Pair up with someone from our hack-together channel on Discord. Two heads (or more) are always better than one.

🎁 Rewards, Events, and Excitement:

Swag Alerts:
- Made it to the top 20 contributors with merged PRs? Secure your swag from our TBD shop. Keep an eye on your progress via our leaderboard issue.
- As for the top 3 contributors, brace yourselves for some custom Hacktoberfest swag. Stay tuned for the reveal!
Event Highlights:
Dive into our bustling Hacktoberfest schedule! Whether you're keen on learning or just here for the fun, we've got you covered:
- September 22nd: Hacktoberfest: best practices live stream is now available on our YouTube channel.
- October 2nd: Set the tone with our Hacktoberfest Launch event!
- October 5th: Brush up with our Intro to Git Workshop.
- Every Friday: Engage with us for PR reviews, live Q&A, and more interactive sessions.
Never Miss Out: Keep a tab on our events-and-updates channel - we're always brewing something new!

📂 Dive into Our Repos:

Not sure where to start? Hacktoberfest isn't just about addressing existing issues. If you spot a bug, typo, or see room for improvement, feel free to create a new issue or dive in with a fix! Explore these repos and see where you can make an impact:

developer.tbd.website: MDX, Javascript, CSS, MARKDOWN
- Good First Issues
- Hacktoberfest Guide
dwn-server: Typescript, Javascript
- Good First Issues
- Hacktoberfest Guide
dwn-sdk-js: Typescript, Javascript
- Good First Issues
- Hacktoberfest Guide
web5-js: Typescript, Javascript, HTML
- Good First Issues
- Hacktoberfest Guide

Hot Tip: Not a coder? No worries! We have non-code related issues up for grabs. Check them out on our developer.tbd.website repo.

More Resources for First-Time Contributors:

📖 How to Contribute on GitHub
🛠 Git Cheatsheet
🔍 Projects Participating in Hacktoberfest

🔄 Fellow community managers, did I miss anything? What are you doing for "Preptember" and Hacktoberfest? Share your insights and strategies in the comments! Happy Hacking everyone! & Cheers to Hacktoberfest 2023! 🎉

Let's Connect

💬 Got a question or just want to chat? Leave a comment below or hit me up in discord.
🤝 Fellow community managers or tech enthusiasts looking to collaborate? I'm all ears! DM me on Twitter.
📣 Enjoyed this post? Follow me here on dev.to for more community management tips and all things tech.
🔔 And if you're as excited as we are about Hacktoberfest 2023, make sure to share this post with your network!

Who Really Owns Your Social Media Handles?

Ebony Louis — Tue, 05 Sep 2023 14:38:18 +0000

In today’s age of social media dominance, our online identities have become integral to both our personal lives and professional endeavors. From connecting with friends and family to building brands and businesses, platforms like Twitter and Instagram have given us the power to create digital personas that resonate with others where your user handle serves as a unique identifier in the digital world.

However, recent incidents have shed light on a fundamental question: Do we truly own our user handles on these platforms? Events, such as Twitter's rebranding and the subsequent takeover of the @X handle from a longtime user, shed light on the intricate web of ownership, accountability that revolves around these usernames, and how account models across the web work today.

Borrowing vs. Owning

User handles, also known as usernames, are a string of characters that represent your digital presence on platforms like Twitter, Instagram, and TikTok. While users assume that the handles they create are tied to their accounts, the reality is more complex, often dictated by the terms of service set by the platform. These terms outline the rights and limitations users have over their usernames/accounts, establishing a virtual "landlord and tenant" relationship between you and the platform provider.

This relationship was exemplified when Twitter rebranded as "X," causing collateral damage as the company took repossession of user handles like @X, without notice or monetary compensation. This was echoed in cases like @Music, which was created by a user who curated their digital presence with this handle for more than 16 years.

The notice from Twitter to this account holder reads:

The user handle associated with account @Music will be affiliated with X Corp. Accordingly, your user handle will be changed to a new user handle.

While this is certainly alarming, it’s not illegal. Most people don’t read the fine print of the Terms of Service agreements when joining these applications, and therefore don’t realize how much control these centralized organizations have over our data and digital identity.

The Problem & The Solution

The way the web stands today, each time we engage with online platforms that require accounts, we borrow an identity from them and then proceed to build a reputation and possibly brand associated with this borrowed identity. The recent turmoil experienced by Twitter has thrust the very nature of the web into the spotlight for those who previously might not have contemplated its issues. This is precisely why Decentralized Identifiers (DIDs) bear immense significance.

At the core of Web5's paradigm lie DIDs, which serve as identities that users own and control. DIDs provide individuals with distinctive, universally resolvable identifiers that persist through time and consistently remain under their control. Unlike conventional usernames, DIDs can't be confiscated by platforms, thus empowering users to truly possess their digital identities. This transformative shift adds an identity layer to the web eradicating platform-mediated handles.

Fortunately, Twitter automatically gave the user who created @X a new (albeit way less cool) handle. However, what if the company simply closed that account instead? The user would have lost not just their username, but potentially their entire digital existence on that platform if their profile had been wiped out.

While X's actions towards these users might not have violated any legal boundaries, is this the way we truly want the web to be? Social media has transcended its original purpose of mere social interaction; it now intertwines with our livelihoods. When signing up for a new platform many of us adopt the same usernames. These usernames serve as both personal and professional branding tools, encapsulating not just our individual identities but also the essence of our businesses.

Web5 will revolutionize data ownership by restoring it to us, the users, while allowing applications to focus solely on enhancing our user experience. If you're eager to delve into the world of Web5, our documentation serves as an excellent starting point. For those seeking to contribute, we invite you to explore our contributing guide or head on over and checkout our projects in GitHub. We warmly welcome you to join our Discord community and embark on this exciting journey with us.

Authentication With Web5

Ebony Louis — Tue, 05 Sep 2023 14:19:30 +0000

With the emergence of Web5 comes the exciting possibilities for individuals seeking more control over their online identities, data and content. With Web5, traditional authentication methods are no longer the sole means of verifying identity and ownership. Instead, users can leverage Decentralized Identifiers (DIDs) to establish their digital presence while retaining full control over their data. Let's explore how this revolutionizes authentication and content ownership as we know it.

Decentralized Identifiers, or DIDs, lie at the heart of Web5's identity management. DIDs provide individuals with unique and globally resolvable identifiers that are persistent and always under their control. By using a DID, users establish their online presence, similar to a username. This paradigm shift empowers individuals to manage and control their personal information, granting them the freedom to partake in various online platforms all while owning the content and data they share.

Web5 applications eliminate the need for centralized authorities to authenticate us through methods such as two-factor authentication or username/password combinations. Instead, DIDs, alongside data associated with DIDs like Verifiable Credentials, become the foundation of trust. When users interact with Web5 applications, they present claims associated with their DIDs as proof of identity. These applications can verify the authenticity of the user's attestations without the need for traditional username/password authentication.

How It Works

Let's delve into the technical aspects of this. When you acquire a DID, it comes with a public-private key pair. Your DID can be resolved by anyone into a DID document, containing your public key, similar to a username that can be copied and pasted into a login screen.

However, to prove that you are the rightful owner of the DID and it is indeed you logging in, your private key becomes crucial. Your private key should never be shared, and it allows you to generate a digital signature. Whenever you author a message, it automatically carries a digital signature. To verify the same message, it requires the public key. For example, when logging into example.com, sending a message and successfully authenticating it, the online platform will utilize your public key for verification. If the verification process is successful, they can confirm that you are the rightful owner of the given DID, without ever needing your private key.

With Web5 authentication, you can effortlessly create an account, free from the hassle of coming up with a new handle or hoping your existing usernames are available. Instead, you can embrace the simplicity of using your DID. Your DID becomes a personalized "username" that you can use to log into any supporting app's login screen.

Your DID serves as a URI (Unique Resource Identifier) that leads to your DID document, acting as a special hub providing a glimpse into your digital identity. Within your DID document, the application utilizes the URIs as guideposts, leading them to your DWNs (Decentralized Web Nodes) which store your content and data.

This user-friendly approach relieves you from the burdens of creating new content or manually downloading from one platform to upload on another. All the content to which you have granted the application access to will be readily available for the application to read/write to, simply by logging in with your DID.

Benefits of Authentication with Web5

One of the biggest benefits of this is the shift in content ownership. In traditional web applications, content is often stored on centralized servers, placing it under the control of the service provider you've created an account with or you're logged into. However, in Web5, individuals maintain ownership and control over their content. When users create and publish content within a Web5 application, their DIDs are linked to that content, establishing a clear link between the creator and their work. The user's content is stored in their own datastore, a DWN, as opposed to stored on the platform they’ve logged into. This ownership grants users greater autonomy and enables them to decide how their content is shared, used, and monetized.

Another benefit is the enhanced security this type of content ownership and authentication provides. With traditional web applications, data breaches and unauthorized access are a common problem that pose a significant risk to the user and the company that holds this data. In Web5, the distributed nature of the infrastructure gives the users full ownership over their data/content that is stored and protected in their DWN. By reducing the reliance on centralized servers, where multiple people have access to a user’s data the impact of potential security breaches is lower. Empowering users to have more confidence in their online interactions.

Web5 represents a significant leap forward in the evolution of the web, redefining its landscape as we know it. If you're eager to delve into the world of Web5, our documentation serves as an excellent starting point. For those seeking to contribute, we invite you to explore our contributing guide or head on over and checkout our projects in GitHub. We warmly welcome you to join our Discord community and embark on this exciting journey with us.