Even if they turn them on, many body cams in use store the files locally on an SD card with no authentication or verification of chain of custody, just flat video files. It is trivial to wipe evidence from these Axon cameras especially - https://github.com/xraymemory/haxon
This is really cool. I think it might even be possible to improve it further so opening an issue isn't even needed.
My thinking is you could store the links and the corresponding shortened URL lookups as an element in the HTML source itself. You would have a submit input on the page. User enters the url they'd like to shorten (or is pulled from a param). The JS reads that value and then looks it up to see if it already exists in the element you created for storage. If not, it creates a hash as the shortened 'link' and adds it to a hashmap / element. Now this is the crucial part: have JS call the Github Actions API to trigger a workflow (https://docs.github.com/en/free-pro-team@latest/rest/referen...) that puts the updated hashmap (which is a payload for a custom parameter you defined for the GH Action) into a file e.g. `links.json` or even outputted directly into the HTML source. Then have the action commit this file back into the repo. Thus, the flat file in the repo acts as the storage mechanism for the links. From a UX standpoint, this is a little smoother and more cohesive (same site to input & redirect) than having to open a GH issue.
With this approach, you can still have the nlsn.cf short domain redirect as long as you pass the URL params and get them in JS from the location, which it looks like you already do. I might try whipping up a version of this tonight. Thanks for the inspiration!
Hmm having a GitHub action redeploy the site is not instantaneous and it does take up to 1 minute for the site (and consequently the new short link) to be updated. Nevertheless, that is a sweet idea, and there are other replies that suggested using a static site generator to generate one html file per short link, with each html file containing a "redirect" tag in <head>. This idea can definitely be combined with a GitHub action. Personally I feel that is overkill, because if I were doing something so elaborate, I would have opted for a simpler and more scalable option like Google Cloud Firestore or Firebase URLs
Here's a few places you could try: /r/retrobattlestations on reddit, @foone and associated accounts on Twitter, archive.org (they have a lot of old equipment to aid in preservation and restoration), or Electronic Arts Intermix (https://www.eai.org/about-eai-faq/) which is an arts organization with a focus on media preservation.
I just want to say I recommend everyone try making their own RNG!
Also, it's so wild to me how these renowned Princeton scientists and engineers got so caught up in the search for "psi" or nooetic abilities. I suppose that's what happens when you are eternally curious and always seeking that prime mover.
