⬜⬜⬜⬜ ⬜⬜
Gets the brain going a bit more than Wordle - fun game all round!
* turns out hacker news doesn't like green / yellow square emojis though
445 karma · joined June 30, 2019
Typescript primarily.
Interested in video automation, gaming, crypto, fintech - feel free to connect with me.
dave [[[at]]] weatherall.io
⬜⬜⬜⬜ ⬜⬜
Gets the brain going a bit more than Wordle - fun game all round!
* turns out hacker news doesn't like green / yellow square emojis though
Currently building my startup replays.lol but looking to take on work on the side
Most common stack: React, Typescript, Sass, Node, Electron, Jest, graphql, DynamoDB
Excited to work in fintech, video automation, web3 projects, but open to any industries!
Daily rate of £600 (~$812) per day - Happy to quote on a per project basis instead if you prefer.
Contact: dave [at] weatherall [dot] io
Daily rate of £600 ($819) per day - Happy to quote on a per project basis instead if you prefer.
Contact: dave [at] weatherall [dot] io
[1] - https://www.unihertz.com/collections/all-products/products/t...
Interested in fintech, video automation and blockchain, but open to any industries!
Daily rate of £600 ($819) per day - Happy to quote on a per project basis instead if you prefer.
Contact: dave [at] weatherall [dot] io
I'm a full stack Typescript Developer, specializing in React and Electron applications. - I have over 5 years experience working on javascript / typescript applications.
Interested in fintech, video automation and blockchain, but open to any industries!
Daily rate of £600 ($819) per day - Happy to quote on a per project basis instead if you prefer.
Contact: dave [at] weatherall [dot] io
Location: Remote (UK)
I'm a full stack Typescript Developer, specializing in React and Electron applications. - I have over 5 years experience working on javascript / typescript applications.
Interested in fintech, video automation and blockchain, but open to any industries!
Daily rate of £600 ($813.74) per day - Happy to quote on a per project basis instead if you prefer.
Contact: dave [at] weatherall [dot] io
But I'm also using this code in a consumer focused desktop client, for gamers to record their own gameplay and review it back (replays.lol)
The obs-studio-node integration code can be found here: https://github.com/davidweatherall/replayslol-obs-recorder/b...
The purpose of this code is to find the active league of legends executable, create a 'Game Capture' source with the league of legends window as the input, and then add that source to a 'Scene', and then start recording when triggered, and stop recording when triggered.
The function (setupScene) on line 55 is the interesting OBS stuff.
Unfortunately this doesn't include any overlay stuff, but it's all done in a similar way, where I add a source with a locally hosted server as a 'Browser' Source on top of the gameplay, with the parameters of the URL telling the server what information I want to be displayed on the website.
The overlay is just a website, with a transparent background, and content determined by the parameters. - Here is what the website base code looks like - https://gist.github.com/davidweatherall/68e6d4422ce4c0b6fbcc...
I run a few channels similar to this one, which provide value by showcasing how the top-end League of Legends players play the game:
https://www.youtube.com/channel/UCMvtjPFhJR0BeErid-s1Zbg/vid...
Manually curating all of these videos would take a lot of time and effort.
In order to record these videos, I have scripts set up that load high level games ready to spectate, start watching via the League of Legends spectator client, play the replay back, start recording using OBS, programmatically adding an overlay to the videos showcasing information (which would be much harder to do post-production as this would require re-encoding a full 25-50 minute video each time), stop recording with OBS, and then upload to YouTube with relevant title / description / thumbnail.
I could (and have looked into) hooking directly into windows APIs to do the recording, and editing of the videos, but it is much easier with OBS.
I wonder what results you would see for something like yahoo, the daily mail, reddit, or other sites that heavily rely on ad revenue, which attempt to force the user to accept the cookies through non-obvious no buttons, or long processes to opt out of cookies.
Isn't this the point of the legal process that FB is doing? FB aren't the ones to decide whether a domain is bad or not, it's down to the judge.
I strongly believe if you asked the majority of users with an engineering background if they thought whatsapp kept a log of "all your contacts and group names, past and present, covering multiple phones you've connected to the account, plus your account info" - they would say yes. These seem like pretty normal things for a messenger app that's focused on UX rather than security to store?
Relative pathing can be useful depending on file structure.
It avoids issues with directory / page naming conflicts. E.g. my images are stored at /assets/img/image.png - but if I wanted to create a page at example.com/assets this would require me to then place an index.html inside my assets directory - which doesn't seem logical.
Overall, mostly personal preference of me disliking the index.html inside directory method - It just doesn't seem like it's the "right" way to access a page. If I have a example.com/about page - I expect them to be hitting an about.html file.
Earlier today I modified the popular jakejarvis s3 sync github action to allow for this during my CI/CD process.
https://i.imgur.com/BspPL2H.png https://whatsmybrowser.org/b/JZAUZ62
Appears to be caused by using 100vw, which doesn't factor in the width of the scrollbar.
Notably on the selectors:
[control="LandingPage"] .hero-header
and [control="LandingPage"] .platform-information .info-sectionInterestingly enough, about 2 clicks around their site and you realise they didn't even put the effort into setting up their Shopify site correctly... - https://unicornrides.com/collections/all
[1] - https://unicornrides.com/pages/unicorn-shipping-update
I agree X years after creation sounds like a much better system though.