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

Create a component in the remotehack.space site where we can show who's currently on the hackday #208

Open
lpmi-13 opened this issue Jan 27, 2024 · 3 comments · May be fixed by #227
Open

Comments

@lpmi-13
Copy link
Contributor

lpmi-13 commented Jan 27, 2024

it would be cool to have a map (maybe D3 or otherwise) that show dots on a big world map for who's hacking on the last saturday of every month (not even necessarily restricted to only the one we do connected to this website. If anyone at all is hacking during the hackday, it would be cool for the city/country/etc to show up on the map.

Also wanted to use cloudflare KV (https://developers.cloudflare.com/kv/) on the edge to store this state, and what we could do is just let anyone set the values for a country (probably only let the workers switch from false => true for a specific place), and then just have a github action to wipe the values on the first of every month.

Not super sure how we keep the values from being written on not the last saturday of the month (probably just some hacky if blocks or something), but would also be nice. I suppose we could just only have the worker spin up at midnight on the last saturday of the month and maybe that entire problem goes away. Then we can kill at midnight of the same day and also wipe the KV state.

@jake-walker
Copy link

It would be cool to have a Discord bot to set locations too

@lpmi-13
Copy link
Contributor Author

lpmi-13 commented Jan 25, 2025

Love it. Ship it!

@jake-walker
Copy link

https://github.com/jake-walker/remotehack-livemap-api
https://github.com/jake-walker/remotehack.github.io/tree/livemap

@jake-walker jake-walker linked a pull request Feb 4, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants