THE TAKEOVER (web5)

AN IDEOLOGY BEHIND WEB5 EXISTENCE

I understand web5 as a stolen authorization in matters that concerns public and private life, let's take for instance the social media as example where the codes/commands embedded in a particular app are strictly for a particular function which can not be manipulated by anybody except the writer (software developer/owner of the app) who coupled the code together to realize the app that gave rise to many users who has put out both there personal lives, business, career and so on, out there but for some reason there do not want that particular aspect of there lives to be out in public anymore, so it let them to delete such data from the app but unfortunately the codes/commands that governs the app doesn't legitimatize the complete deletion of such data from the data base which means that the software developer can still incur the data or basically still have right to such data so with web5 it will allow you have full control over who can access your data.

AN OVERVIEW ON WHAT WEB5 IS ALL ABOUT

The Internet 🛜 Of Today Your software program revolves around data algorithms, they are basically nothing without a data.

Web5’s core idea is to “put you in control of your data and identity” – a core tenet of Web3’s decentralized identity systems. Instead of inviting users to sign up for an account on a centralized platform (like an Instagram account), Web3 protocols reference users by their crypto wallet addresses. Protocols like the Ethereum Name Service let users turn their wallet’s garbled alphanumeric string into a word or phrase (like amara.eth) similar to how Domain Name Service (DNS) allowed websites to have addresses like amarachi.com rather than a long string of numbers like 54.235.191.121. Decentralized data storage is a concept already in existence and is provided by platforms like Filecoin and IPFS.

Instead of an internet that relies on accounts provided by companies that hold customer data “captive in app silos,” Web5 pushes for “a new class of decentralized apps and protocols that put individuals at the center.”

In doing so, Web5 sounds like an attempt to rid Web3 of the centralized actors that Dorsey credits with sullying the mission of decentralization. Zion, a self-described Web5 app, uses Bitcoin’s base layer to help content creators work together with fans. But avoiding corruption is, of course, difficult

The other thing that is different from Web3 is that Web5 works with existing Web2 services; it does not seek to replace them entirely. Web5’s pitch deck provides the example of Groove adding a playlist to a Web5 user’s decentralized identifier, which another music service, Tidal, can use to fashion its own playlists within the app. The decentralized identifier prevents the user from having to recreate their preferences on another platform.

other example of Web5 in action involves one user granting her hotel, airline and rental car provider the ability to add information to her database about her trip. The user can revoke access at any time and choose another service to “help her visualize her itinerary.” Again, the idea is to tie data that’s usually locked inside centralized services – something that calls “a massive, unworkable mess” – to a single user-controlled identity. Think of it as similar to how many sites and apps leverage a user’s Google account to log in, but in this case it will be a single login with a decentralized network of nodes.

Web 5 Features

● Managing your own node other example of Web5 in action involves one user granting her hotel, airline and rental car provider the ability to add information to her database about her trip. The user can revoke access at any time and choose another service to “help her visualize her itinerary.” ● Building a server less application. An application simply sends a request to your DWeB node, not a server managed by a centralized authority. An application does not need to worry about data management.

YOUR ROLE AS A DEVELOPER/NONDEVELOPER

● Frontend Developer: Working with a framework like React.js, you can build any type of application that requires user data. You are building any application ready to communicate with the backend. No change. ● Backend Developer: APIs: With the current Web 5.0 JavaScript SDK, you can utilize various APIs to create applications that seamlessly communicate with the backend.to fetch user data in real time from DWeb nodes so as to render or use on the frontend. It does not alter the usual application development flow. ● UIX designer and other non-tech roles: Your roles are intact- ensuring a great user experience. Note: From the explanation above, the significant change is how a backend developer communicates/fetches the user data. In summary we are simply building a web that revolves round: ● Self-owned identity: No more email, password managed by Google. Your DID is a unique identifier that resolves your identity, directly mapped to your data (public , encrypted). ● User control over their data Learn more Documentation (https://developer.tbd.website/docs/web5/learn/decentralized-identifiers/) Build examples (https://developer.tbd.website/docs/web5/build/apps/dinger-tutorial/)

In conclusion, Web5 aims to revolutionize the internet by empowering users to take control of their data and identity. With decentralized identifiers, enhanced privacy, and seamless data management across various platforms, Web5 has the potential to transform the way we interact with the digital world, benefiting both developers and users alike.