A place for developers to talk about building on Farcaster.

/dev

don't store your secrets in a plaintext .env

don't store your secrets in a plaintext .env

https://developer.1password.com/docs/cli/secret-references

𝓵𝓲𝓿𝓲𝓷𝓰 𝓽𝓱𝓮 𝓮𝓷𝓭𝓵𝓮𝓼𝓼 𝓼𝓾𝓶𝓶𝓮𝓻 • building @buoy 🛟 • pfista.com

Nomad Rural LLG, Western Province, Papua New Guinea

look in their labs, they have this cool new thing called 'secure snippets'. less relevant for this use case, but fucking cool

neat, but i wonder why you would need snippets for the use cases here to be encrypted? 

things like email signature, or common replies in support workflows are inherently being shared with someone else

i think you could do the same with raycast too

app.intersend.io | sequence. pimlico. poap. polygon. consensys. paxful. flipside crypto. dash. bridgewater. darpa. secdef. navy. dia | linktr.ee/alexanderchopan

neat, but i wonder why you would need snippets for the use cases here to be encrypted? 

things like email signature, or common replies in support workflows are inherently being shared with someone else

i think you could do the same with raycast too

https://docs.google.com/document/d/1TjWdarf3XH_0vQWpU40Gv0Jk5_Gm49LGYjRDlP6svzQ/edit?tab=t.0#heading=h.mijktdhz910t

Telling jokes without revealing the punchline.

think about it w wallets and if there was a keystore manager. even without, for wallet addresses, recurring pw or something