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

Feature Request - add sharing Wherigo Cartridges with c:geo #146

Open
JakeDot opened this issue Jan 5, 2025 · 7 comments
Open

Feature Request - add sharing Wherigo Cartridges with c:geo #146

JakeDot opened this issue Jan 5, 2025 · 7 comments

Comments

@JakeDot
Copy link

JakeDot commented Jan 5, 2025

Now that c:geo has Wherigo support, it might be nice to allow users to transfer cartridges directly from a PC to the phone via send2cgeo without having to use some file transfer method and manual copying/moving the cartridge on the phone.

This would be extremely helpful whilst developing cartridges and also useful for normal users.

@eddiemuc
Copy link
Member

eddiemuc commented Jan 8, 2025

I am not an expert for send2cgeo but I assume that it is meant for small pieces of data only (eg coordinates), not larger things like wherigo cartridges

Edit: I also just saw that the technology used by send2cgeo would not allow this (is it a browser extension only). Or do you simply want the script to send wherigo urls from when one is browsing the www.wherigo.com website?

@capoaira
Copy link
Contributor

capoaira commented Jan 8, 2025

I really like the idea, but afaik it's only possible to send GC codes.

Javascript can handle files and send it via an api. But I think downloading cartridges could be difficult. I assume cgeo can download, so it is enough to just send the link.

So sending files and links needs server side chages, but the server side code isn't public.

@mucek4
Copy link
Member

mucek4 commented Jan 13, 2025

The only thing that is stored in send2c:geo is GC code. Sending links could be security issue.
So no files, links or any other data.

@capoaira
Copy link
Contributor

Is it currently possible to send a larger string than a gc code? In that case, we could send the WIG cguid.

@eddiemuc
Copy link
Member

eddiemuc commented Jan 13, 2025

Is it currently possible to send a larger string than a gc code? In that case, we could send the WIG cguid.

This would only help for downloading published cartridges (only those have a cguid). It would not help for cartridge development

@capoaira
Copy link
Contributor

This would only help for downloading published cartridges (only those have a cguid). It would not help for cartridge development

True. But I understand the security concerns about uploading cartridges to a server.
Maybe we can use an external service like Dropbox. Then, the data would be uploaded to the users' Dropbox and downloaded from there.
In that case, the security risk is with the users, like exchange files directly.

Btw, is it possible to open gwc files with cgeo?

@eddiemuc
Copy link
Member

Btw, is it possible to open gwc files with cgeo?

Yes. As of now you need to copy them into the cgeo/wherigo folder. Then they will be shown in list of available cartridges in c:geo

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

4 participants