Enjoying™ running Steam Big Picture on Windows. Best bit is when it forgets the controller exists (often immediately after I've been playing a game WITH THE CONTROLLER) and I have to find the keyboard and mouse to click things.
No, tell a lie, best bit is when it randomly task-switches mid-game back to Big Picture. Really helpful in, say, Rocket League.
If I could get the games I play on a console, I'd dump this godforsaken mess in the bin.
@purplepadma There's a species of frog in Australia called the Banjo Frog - also known as the Pobblebonk Frog - and their call sounds a bit like twanging a thick rubber band.
@CTD What kind of output / layout / effect are you after? The chunks of white space do look a bit “empty” and probably want to minimise those (even if that’s what you’d maybe get with an organic drop / throw of real cards.)
@CTD You'd have a bottom layer of 40-50% of the cards, then another layer for 20-30%, maybe another 10-20% layer, and then a final top layer of what's left. If you were after a pyramid kind of layout, then you'd generate the dots in smaller chunks around the centre for each layer upwards.
@alex Ah, I forgot about that, should have mentioned it. make build worked for me. I'll see if I can fix up the make issues at some point and send them a PR.
@jpmens Had the same problem with Hugo’s livereload websocket. Solved it by creating a cookie after the first successful login and using that as an alternate authentication method. Not ideal at all but the only way I could find to avoid this with Safari.
@jpmens Yeah, auth/realm should probably match the other locations.
I can definitely see my cookie from my site in the Safari devtools under Storage/Cookies. No idea why it wouldn’t show up other than maybe there’s a filter applied? Although it disappears if I hit the refresh icon, weirdly, but comes back if I access the page again.
Today I am trying to work out which books I read on the Kindle in 2023 by looking at the timestamps of the cover images in its application data directory. Because this is pretty much the only damn way you can find out (other than keeping a manual log which I eventually started doing from about April.)
(Don’t even think you can get this info from the device itself either.)
@cdamian Still effectively manual for Kindle Unlimited reads, I think, which have been the majority this year. Because why would you want to keep track of those? Stupid nonsense.
You’ll never guess who broke 5 of his bots by putting ... 2>&1 | tee $HOME/bin/logify >> logs/xyz in his crontab.
I have not yet determined the precise mechanism of breakage but the evidence is damning - everything with that rogue tee broke on the same day and they’ve all started working again now I’ve removed it.
Most peculiar. I can’t even immediately see why it would break the shell script rather than just write the output to that file and also the log.
@pgl Could be. Will have to experiment because it is baffling (but will probably turn out to be something like "bash doesn't work if you fribble the output non-terminally from cronjobs" that was broken in 1998 and never fixed.)
I should set up a keyboard macro because I keep typing the same sentiment over and over
"Replacing the whole system would take years, and honestly a total rebuild may never be top priority for as long as the old system keeps ticking over. It’s probably more pragmatic to gradually make the old system redundant by building better features in newer systems, so that eventually no-one uses the old system, and then it can be retired."
@Kiwicoder@flameeyes There's also "you can find developers in the old language but it's an omnishambles of catastrophe that no-one understands or can work with" but you're still better off replacing problem areas one-by-one rather than attempting a full rewrite in a new language.
@resuna Yeah, I was just looking on the internet for a USB3 USB-C cable and there's an amazing number that are limited to 480Mbps without a hint of shame.
Today is yet another demonstration that I do not function well in an environment where everything needs to be released yesterday and there's no documentation for any of the services you're expected to change in fundamental ways and people are too busy to properly review things and you can't do any testing locally which means you have to wait for PRs to be approved, merged, and the deployment queue to finally put it onto the dev environment.