Geocache organization ideas #13
Replies: 3 comments
-
|
您好!您的邮件我已收到
|
Beta Was this translation helpful? Give feedback.
-
|
One solution that is pretty easy to implement, doesn’t require any auth providers (self-hosted or otherwise): https://github.com/Greenheart/pagecrypt This is password protection for html pages that is easy to incorporate into static sites. You provide a password/phrase/etc, the page is encrypted with that key, then when you visit the page you get a little dialogue box. “Inspect page” just gives you the dialogue box and a bunch of encrypted gobbledegook. I usually specify a header in the .md, e.g. ‘password_protect: true’, then grep for it and run those pages through pagecrypt after build but prior to publication. Provide the passphrase as an environment variable, easy to switch out after a cache has been found and you want to rotate keys. Would have to have that repository private, probably use a subdomain, or use a GitHub Action on this site to pull the md from elsewhere, so the beans aren’t spilt by looking at the source code of this repo. One workflow would be to have a QR code with a long passphrase per geocache, which takes you to a special page with further instructions and some Easter eggs, maybe a printable QR code with the next planned key for that cache. You can also include the passphrase as part of the URL params, so you get shareable URLs that don’t require the user to actually type anything in. Or you could skip all of this and make it so the QR code just takes you to a regular contact page with a prefilled token (something the mail filters could keep an eye out for), which you submit and then get an email from JB asking if you have any vids/pics to share, via whatever barbaric method is most preferable for the user. Of course, a little FastAPI/htmx/etc action is always great. :) |
Beta Was this translation helpful? Give feedback.
-
|
Convo in matrix (src):
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
So, geocaches have been floating around the network for the past couple of weeks and talk of having a way for JB to organize that. While I love the hand-crafted, in-person updates that happened (https://podverse.fm/clip/8NdMyaRuS) 😅, I figure a way of automatically including this in some website would make it easier to track. I figured creating this issue could help consolidate ideas in one location and allow people to vote for the ideas they like best.
Based on the latter part of the clip above, identifying a way for listeners to submit requests for JB swag so they can put a geocache near them would be a requirement as well.
Beta Was this translation helpful? Give feedback.
All reactions