Building websites, playing board games, editing videos.
Will fika βοΈ
Powered by π±
| Personal Website π§ | https://www.hejchristian.com/ |
| Pronouns | He / Him |
| Current Location | π΅πΉ |
Building websites, playing board games, editing videos.
Will fika βοΈ
Powered by π±
| Personal Website π§ | https://www.hejchristian.com/ |
| Pronouns | He / Him |
| Current Location | π΅πΉ |
So I guess I have some learning to do about this recent supply chain attack and npm stuff π
No recent project I'm working on has Axios as a dependency, these in the screenshot are old. But it's time I understood a bit more on how to stay safe. Open to any wisdom!
Found this article regarding the incident
https://snyk.io/blog/axios-npm-package-compromised-supply-chain-attack-delivers-cross-platform/
So from the sounds of it, had I been doing an npm install within that two hour window I could have been affected? just like that? That's scary.
Switching this machine off to go and play a new board game with my favourite person in the world.
Today we're trying Meadow βΊοΈ
I'm silly, I don't know why I didn't expect it to be precise... it's not like I haven't used digital maps before.
I guess it just felt a bit different when _I_ have access to just use it like that, and upon doing so, I got coords right on top of my head.
[2 / 2]
Might approach this in a different way.
A form folks can submit? then I can manually add the pin. But what's to stop someone spamming loads of pins? Make them supply an email too? Easily faked, and GDPR issues again.
Maybe I can just ask people direct message me if they wanted to drop a pin π
... All this is because I don't want to run analytics on my site, BUT I would enjoy to see where folks are broadly visiting from, if they decide to provide that π₯Ί
[1 / 2]
Huh, I didn't expect <geolocation> to be so precise π
https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API/Using_the_Geolocation_API
I had an idea for next weekends web dev project: A digital map cork board map where folks can "pin" their location ( across a grid system so it's not precise coords ) πΊοΈ
I was thinking client-side <geolocation> could be used to try and prevent someone clicking for country A when they're in country B... but I feel like this opens up a whole can of worms for GDPR stuff.
Still got a ways to go - some of the animation states are a bit clunky and need some work. I'm using the Web Animations API but I'm not too good with it.
https://developer.mozilla.org/en-US/docs/Web/API/Web_Animations_API
Also want to load up to 3 tracks per record, and some more sfx βΊοΈ
Some little details I'm happy with:
- The volume level changes the speaker animation scale
- The display has a nice animation (Possible flicker effect too to make it more screen like, but I turned it off for now)
- I like the hover effect on the album covers (need to look into why image gets a bit blurry tho) - All done with just CSS.
- The record itself is entirely CSS too, with a repeating-linear-gradient() making the markings on the record.
Weekend project progress π
- Album meta data display
- Buttons with some sfx
- Volume Control
- Arm/Record animation
- 30 second music previews via iTunes API.