Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loom -> Cap importer chrome extension #363

Open
richiemcilroy opened this issue Mar 12, 2025 · 9 comments · May be fixed by #366
Open

Loom -> Cap importer chrome extension #363

richiemcilroy opened this issue Mar 12, 2025 · 9 comments · May be fixed by #366
Assignees
Labels
💎 Bounty Feature New Features Web Things affecting web/cloud version

Comments

@richiemcilroy
Copy link
Collaborator

I'm 99% sure this will need to be a Chrome Extension.

Requirements are:

  • User signs into Cap via Chrome extension (similar auth process as desktop app)

  • Chrome extension asks user to visit their Loom dashboard

  • We allow the user to import one space at a time, so they should select which space they want to import (spaces which they own, not only a member of).

  • We retrieve a list of all of the users members for that space

  • We retrieve a list of all videos belonging to that space

  • We ask the user which space they want to import into, or ask if they want to create a new one

  • We preview to the user what is going to be imported

  • We create the necessary imports, via a new /api/importer prefixed endpoint (from the web app).

  • When creating the video, we can use this url: https://www.loom.com/api/campaigns/sessions/LOOM_VIDEO_ID/transcoded-url, to grab the video .mp4 file. For now, we can leave the actual .mp4 upload to Cap for later. The Cap team will implement this part.

  • For imported videos, spaces, members etc, we should have a column on each that tracks their respective Loom id so know it was imported.

@richiemcilroy
Copy link
Collaborator Author

/bounty $500

Copy link

algora-pbc bot commented Mar 12, 2025

💎 $500 bounty • Cap

Steps to solve:

  1. Start working: Comment /attempt #363 with your implementation plan
  2. Submit work: Create a pull request including /claim #363 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to CapSoftware/Cap!

Add a bountyShare on socials

Attempt Started (GMT+0) Solution
🟢 @neo773 Mar 12, 2025, 6:27:19 AM #366
🔴 @itshaithamn Mar 13, 2025, 3:35:17 AM WIP

@neo773
Copy link
Contributor

neo773 commented Mar 12, 2025

/attempt #363

Algora profile Completed bounties Tech Active attempts Options
@neo773    3 CapSoftware bounties
+ 196 bounties from 32 projects
TypeScript, MDX,
Rust & more
Cancel attempt

@itshaithamn
Copy link

itshaithamn commented Mar 13, 2025

/attempt #363

@neo773
Copy link
Contributor

neo773 commented Mar 13, 2025

@itshaithamn

Hi,
Just a heads up, the issue is already assigned and it's a work in progress, I expect to raise a draft PR very soon.

@itshaithamn
Copy link

itshaithamn commented Mar 13, 2025

@neo773

Hello,
Let me know if you need assistance, I didn't notice the assignees sorry about that. I'll move onto the next issue then.

@itshaithamn
Copy link

@neo773

How's that PR going? Can I take a look at it as well?

@neo773 neo773 linked a pull request Mar 15, 2025 that will close this issue
Copy link

algora-pbc bot commented Mar 15, 2025

💡 @neo773 submitted a pull request that claims the bounty. You can visit your bounty board to reward.

@OmarMcAdam OmarMcAdam added Feature New Features Web Things affecting web/cloud version labels Mar 18, 2025
@animeshd9
Copy link

Does the latest PR close the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💎 Bounty Feature New Features Web Things affecting web/cloud version
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants