nostr:nprofile1qqsrs7xetkmms4xr5rfm944hh7dl9zekzc47vsex74fphfcu7w6956gpp4mhxue69uhkummn9ekx7mqpr9mhxue69uhks6tkv46xzmrt9ehx7um5wgcjucm0d5etp66v what do you think?
As our team at Soapbox has grown, we've faced a common challenge in the Nostr ecosystem: how do you enable multiple team members to schedule and publish content without sharing your private key (nsec) with each team member? To solve this problem, we built a bridge that connects Loomly (a content scheduling platform) to #Nostr through Zapier. Zapier is automation tool for connecting the APIs of popular applications. While it's not the most "pure-Nostr" approach and it relies on proprietary platforms, it's a practical solution that actually works for real marketing teams with collaboration needs. We are sharing this solution in case it helps your team, too! #GrowNostr https://soapbox.pub/blog/loomly-zapier-nostr-bridge
Discussion
Try it? not familiar with loomly but I'd code up the zapier section so that we don't put the nsec in, to solve the last mile issue
frostr isn't mature enough yet, other projects to handle multi key management were good ideas but ......sort of abandoned or not maintained, e.g. keycast
I’m up for trying if you think it’s a solution :)
Last case scenario we got the nsec 😅
try out the loomly and see what features it wins at. if its simple enough we just vibe code the UI and then tack on the zapier backend, this should be easy enough
come with a report friday? 😄
Cool!
I sure wish i could clone myself...... too many things to do and not enough time, even with AI 😅
Well, maybe nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft ‘s tenex will allow you to “clone yourself” soon enough 🤪🙃💪
i don't even know what this is
also worth checking out self hosting n8n ....
worst case scenario i cobble together a nostr native version of this somehow together, self hosted
yes we also have the same issue as soapbox does