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

Ability to save queues #15

Open
gardaholm opened this issue Oct 24, 2024 · 5 comments
Open

Ability to save queues #15

gardaholm opened this issue Oct 24, 2024 · 5 comments

Comments

@gardaholm
Copy link
Contributor

Would be great if queues can be saved and accessed later.
Maybe via a share URL which stays persistent on the server?

I sometimes search for possible projects or for a warmup list while sitting on the couch. And it would be handy access this later. With your filter screen it would come handy

@marcodejongh
Copy link
Owner

Is it good enough for now if we save the queue in the storage of your phone?
I've been trying to avoid doing too many backend things as they can potentially add a lot of work, it's also why the connections between phones run through web RTC (peer to peer)

@gardaholm
Copy link
Contributor Author

I guess having them on the phone is good enough. I normally scan to the list before I start my session or the day before to create a playlist for myself (or for others)

@marcodejongh
Copy link
Owner

@gardaholm How about I just add official Kilter/tension lists support using their rest-apis?
The only caveat is that I would have to store login details in your browser and proxy them through my server, which technically is considered a security risk. However, I doubt anyone is storing anything sensitive/abusable in their Aurora account, but wil lneed to warn users that they shouldnt reuse passwords

@gardaholm
Copy link
Contributor Author

using the tension lists would also be great, I guess!
can't they be accessed with the token alone, without using the credentials?

@marcodejongh
Copy link
Owner

I'd have to ask Aurora for www.boardsesh.com to be added to their CORS Headers which I doubt they'd be willing to do.
Because if they did that, its still the same security problem as they dont control the boardsesh frontend code.
So if I wanted to from teh FE code, I could still compromise peoples accounts.
The real solution to integrating would be to set up some kind of oAuth flow, but thats a big piece of work for them and therefore unlikely to happen.

But climbdex has the same problem, and solves it in the same way.
To get around CORS, I proxy requests through my own backend, the downside of that the user has to trust I dont steal/log their credentials.

But considering it's a climbing board app, not online banking, I doubt it would scare too many people

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants