qyfff

qyfff

new to here
HomeArchives

Further Research on Modification and Deletion of xLog

#xlog75
AI Translation
This post is translated from Chinese into English through AI.View Original
AI-generated summary
The article discusses the modification and deletion processes in xLog, emphasizing that these actions do not affect the original source files. Updates involve assigning a new CID to the cache, while deletions only add a transaction to the blockchain, making the content hidden but still accessible via original links. Users can trace all transactions associated with an account, including comments and content, regardless of modifications or deletions. The blockchain's transparency and traceability can be beneficial and detrimental for individual users. While it allows for easy content creation without strict identity verification, it raises concerns about the potential for harmful content and lack of platform control. Currently, the user base is relatively sophisticated, minimizing immediate issues. The article questions whether blockchain is truly suitable for blogging, highlighting concerns about data ownership and uncontrollable public opinion. Feedback from readers is encouraged.

Previous article:

https://qyfff-5342.xlog.app/xlog-update-delete

View the code for further analysis of the xLog modification and deletion process, the general process is as follows:

image

We can further confirm that the two operations of deletion and modification do not affect the source file at all. Updating involves handing over the new CID to the cache, while deletion can only add a deletion transaction to the blockchain, hiding the article in the front end, but it can still be accessed through the original link.

For example, we can find such information at the bottom of any blog, and by clicking on the owner, we can query all transactions under the owner's account address, allowing us to see all comments, article content, update content, etc. After entering the transaction details, we can find the corresponding IPFS link to locate the original text, regardless of whether the original text has been deleted or modified.

image

image

The blockchain has two properties: transparency and traceability.

You can look up all transactions of an account from the account address, which means you can query all text published by that account on xLog, including modification records and deleted articles.

For individual users, there are both advantages and disadvantages, as content may be traceable. However, on the other hand, the binding relationship between this address and a person is not so strong. In many web2 communities, binding an ID is often required to be allowed to speak. If we no longer want a certain account, we can simply reopen a new one quickly and start outputting text again, whereas in web2, one might face account bans and certain risks.

For the community, I still believe the disadvantages outweigh the advantages; it is too free. If harmful content (hate, rumors, cyberbullying, etc.) appears and the platform lacks control ability, this is bound to lead to chaos.

Of course, at this stage, those who can access this platform are still relatively educated individuals, so the above issues should not arise for now. Additionally, the community aspect of this blog is not very strong; everyone is more focused on managing their own blogs.

Is blockchain really suitable for blogging?

  • Data belongs to oneself, not kidnapped by the platform? Balancing data ownership? Convenience?
  • Data does not seem to fully belong to oneself
  • There is still the uncontrollability of public opinion

I hope to hear your thoughts.

Loading...
Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.