<aside> 💡 This page explores best practices for data management specifically in NEAR socialDB, despite that the principles outlined below are highly generalizable to other contexts.
</aside>
GitHub - NearSocial/social-db: Social DB on NEAR
Table of Contents
The world is full of fascinating problems waiting to be solved.
No problem should ever have to be solved twice.
Boredom and drudgery are evil.
Freedom is good.
Attitude is no substitute for competence.
Reference: **http://www.catb.org/esr/faqs/hacker-howto.html**
<aside> 💡 Hyperfiles components and reference objects are stored in the NEAR SocialDB contract.
</aside>
“The world is full of fascinating problems waiting to be solved.”
“NEAR always had an idea to create a user-centric Open Web. Where the users are in control of their data. The data is not siloed in a single instance. The developers don't have to rely on someone else's API permission to integrate with the services. Where the applications themselves are open and can be improved and modified towards one's needs.”
“Blockchains deliver this idea with smart contracts. An always on services that can be used by anyone. But front-end applications are stuck at web2. They are centralized and controlled by a single entity.”
Source: Ethan C. Roland and Pierre Bourdieu
[A.K.A. “Non-financial capital in science” [Link to slides].](https://youtu.be/Cw4opc9ssiM?si=vmwn826u4B1FCT-F)
A.K.A. “Non-financial capital in science” [Link to slides].
Until now…
“… smart contracts were mostly designed for financial applications. This was mostly a technical and monetary limitation of legacy networks. The operations were too expensive to be used for anything else than commercial transactions. Each transaction had to have a monetary value to be worth submitted.
But with creation of NEAR, this limitation was removed. The scalability allowed creating new types of applications. Where the value of a transaction is not a monetary value, but a social value.”