{
  "txid": "b32ecbcc5ac7a82a467b0d17051111a1918809bc17c09e84f2bd6f6ed5482e41",
  "block_height": 706357,
  "time": null,
  "app": "blockpost.network",
  "type": "post",
  "map_content": "# Some suggestions for Blobkpost\n\nBlobkpost is promising. Thank you for the great work.  \n\nI was attracted to it because of its potential for a unique way to manage self-publication. \n\nBy publication, I refer to relatively more serious writing, versus casual social chats on Twitter or other social networks.\n\nCurrently, Blobkpost still lacks content management tools. I hope this will improve in the future. \n\nOnce Blobkpost can provide an adequate way to manage content user features like categories, tags etc., it'd be a big winner. \n\nTry to emulate WordPress. \n\nThanks to its long history, popularity and open source contribution to numerous add-on functions, WordPress has become a very sophisticated system of self-publications.  \n\nHowever, WordPress has a fundamental shortcoming, which Blockpost could overcome.  Let me explain below.\n\nBlockpost already allows the user content be tied to a blockchain payment address (bitcoin address, paymail address or another popular handle).  This is an extremely important function, but no other websites or blog sites have it. It's not that others aren't smart enough to think of it, but that they are all limited by the traditional bank-based payment systems.\n\nOne of the reasons why such a tie to a permanent (although changeable by the user) payment address is important has to do with content ownership right inheritance.\n\nIn WordPress, for example, the user content is either completely in the public domain or can only be managed under a private website under a private domain name.  Should anything happen to the author, the value of such publications is essentially gone as far as the author's family is concerned, and very often altogether to the public if the content was maintained under a paid private domain. It's close to be impossible for ordinary people to have a handle on it. \n\nThe burden is not just the cost of doing things, but more a question of technical know-how. In a typical case, the family members simply do not know how to continue. They don't even know how to find the account that manages the content, much less to actually manage it.  \n\nHowever, if the publication is tied to a specific paymail address (or another popular handle), the ownership and economic rights of the publication will be forever preserved. \n\nA blockchain payment address makes payouts of earnings automatic and easy. But perhaps more important, it creates a hands-free permanency, because a blockchain payment address such as paymail address is free of charge once purchased with a one-time fee.  \n\nIn addition, blockchain content storage can also be free once the initial publication fee has been paid. Even if long-term storage should require a fee in the future, such fees can be set to be automatically paid using the earnings in the payment address tied to the publication. \n\nEverything can be programmed to achieve permanency using smart contracts.\n\nIn contrast, a conventional website under a private domain name needs to be always maintained by paying service and subscription fees, or it will die and all its contents disappear. Again, it is not only a mere matter of cost, but in most cases a matter of technical barrier and lack of automation, which kill the continuity due to a lack of knowledge and skill, or due to a friction that is too high to overcome by most people.\n\n## A further suggestion:\n\nTo further the above advantage, I suggest that you build an automatic inheritance feature. For example, allow the content owner to provide a list of secondary and tertiary addresses for automatic passing down of the ownership in the event of a long period of inactivity of the publication account.\n\nSeeing that Blobkpost is only beta now, I expect great things to come from it in the future.",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "12qjfJJ36LdmEDgicsXdMXruWCNSnZUdma",
  "display_name": null,
  "channel": null,
  "parent_txid": null,
  "ref_txid": null,
  "tags": null,
  "reply_count": 2,
  "like_count": 3,
  "timestamp": "2021-09-25T18:03:50.000Z",
  "media_url": null,
  "aip_verified": true,
  "has_access": true,
  "attachments": [],
  "ui_name": "12qjfJ\u2026Udma",
  "ui_display_name": "12qjfJ\u2026Udma",
  "ui_handle": null,
  "ui_display_raw": null,
  "ui_signer": "12qjfJJ36LdmEDgicsXdMXruWCNSnZUdma",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}