Intro to NFT Metadata
Twitter Clone Owned by Users
Build a user-owned Twitter where you control your own feed.
It might be much easier than you would first guess
- Build an app where a user’s identity is their .eth domain (or pub address if lacking). See withBackdrop for example.
- When a user logs into the app, it would look into a dapp table (e.g. the developer table for the dapp) for that users address and link to the user owned table. i.e. rows in dev table look like
pub address: owned tweets table, owned following table
- Owned table conforms to my schema. e.g.
id, text, reply_to, etc, etc.
- They also must own a table that conforms to a schema for following. e.g.
follow_addr, name, follow owned tweet table. name could just be an optional nickname that you self assign people you follow if you like
- When you load the app, it loads up all the followers from table in 3, it loads up all those owner's tables from 2 and compiles a tweet feed.
If said owner now wants to tweet their own, they just write to their own table.
Not the most elegant thing compared to a centralized DB, but pretty sweet you could build it so simply as a starting point. We wouldn’t recommend taking the exact configuration above to a production example, but it’s a great starting point to learn!
You’d see the world from your own small view. also cool is you could load the world from other people’s pov (for example, I could embed my view of the twitter clone world into my homepage)
- Create a dApp that prompts users to log in using Metamask.
- When the user logs in, create two tables that will be owned by the user.
- Table 1 with schema: `post:text, parent_id:text`.
- Table 2 with schema: `following_addr: text, posts_table: text`
user_addr, user_table1_id, user_table2_id
- A user doesn’t have to be in this table to use the app ^. they may be able to store similar index information, for example, in their ens domain entry.
users-eth-addr...owner in 1.