Decent Bookmarks is in beta! 

Questions for client devs:
- does API make sense for you
- would you consider including decentralized bookmarks in your FC client
- if not, what would you need to see

TL;DR
- Cast Action adds bookmark, removes if already there
- data encrypted at rest
- clients responsible for UI

1/5

Join my frens in cacc club.

Unforgettable Hair /bcbhshow. FOSS at GH:artlu99.

PFP is a wingding 

2/5

- N entities share perms to read+decrypt
- M entities share perms to write+encrypt
- data stored on my "L4" (a database)
- will settle to L2 or L3, testnet contracts first
- identifier is anonymized via salted hash
- secrets stay offchain

4/5

For more sensitive data, can encrypt the payload with a set of user secrets (more complex UX).

For more public data, can decrease security by skipping encryption. Use cases: PINNED CASTS TO PROFILE, Pinned Casts to Channel.

Bookmarks for fid 6546 are currently open + unencrypted. All others are encrypted

5/5

I commit for rest of 2024 to help migrate any user data to FC if that use case makes it into the protocol.

Links:

- frame to install cast action
- endpoint: GET to read data, POST to add, DELETE to remove
- ask privately for access tokens
- GC to discuss. My DCs are open

https://decent-bookmarks-cast-action.artlu.workers.dev

Join the GC here https://warpcast.com/~/group/AwXkv2N5s4pUw1w34XsoMA

The API is exposed here (your FID will be encrypted)

https://decent-bookmarks.artlu.xyz/?fid=6546

Privacy considerations:
- when any client decrypts, that user's data is revealed and tied to FID
- when keys leak, all encrypted data is open (but not linked with FID) until rotated
- smart contracts can be forked/redeployed with different secrets

In Beta, consider that personal data is OPEN to any developer

3/5