Decentralised Social Media - DMeta
Building a New Social Frontier: DMeta, The Decentralized Revolution
Created on 5th July 2023
•
Decentralised Social Media - DMeta
Building a New Social Frontier: DMeta, The Decentralized Revolution
The problem Decentralised Social Media - DMeta solves
FileCoin-Caliberation-testnet Link https://long-math-8400.on.fleek.co/
Sepolia-Etherium-testnet Link https://royal-shadow-2627.on.fleek.co/
DMeta, as a decentralized social media platform, addresses several key problems faced by traditional centralized social media platforms. Here are the main issues it solves:
Privacy and Data Control: DMeta prioritizes user privacy by decentralizing data storage and giving users control over their personal information. Unlike centralized platforms that collect and exploit user data for targeted advertising, DMeta allows individuals to retain ownership of their data and decide how it is shared and accessed.
Interoperability and Data Portability: DMeta aims to establish standards for interoperability among different decentralized social media platforms. This allows users to seamlessly connect and communicate across various networks, while also providing the flexibility to transfer their data between platforms, reducing vendor lock-in.
Trust and Authenticity: Misinformation and fake accounts are prevalent on centralized platforms, eroding trust among users. DMeta leverages blockchain's immutability and cryptographic algorithms to ensure content authenticity and combat misinformation, fostering a more trustworthy social media environment.
Challenges we ran into
Real-time Rendering of Post Likes and Comments:
To achieve real-time rendering of post likes and comments without the need to refresh the page, we implemented the following solution:
React Component and Timeouts: In the client-side implementation using React, we created a dedicated component for post likes and comments. Within this component, we set a timeout function that periodically fetches updates from the server. This ensured that the component automatically refreshed and displayed the latest likes and comments without requiring a manual page refresh.
Friend Request Acceptance/Decline Feature:
To provide users with an intuitive option to accept or decline friend requests, we implemented the following approach:
Secondary Array for Pending Requests: When a user received a friend request, we stored the request in a secondary array specifically designated for pending requests. This array contained relevant information about the user who sent the request.
User Interface for Managing Requests: We designed a user-friendly interface that presented the pending friend requests to the user. For each request, we displayed the necessary details, such as the user's name, profile picture, and any additional relevant information.
Accepting or Declining Requests: Within the user interface, we provided clear and distinct options for accepting or declining each friend request. When a user selected either option, we triggered the corresponding action.
Updating Friends List: Upon accepting a friend request, we moved the user from the pending requests array to the user's friends list, establishing the connection between them. If a user declined a request, we removed the request from the pending requests array altogether.