This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?
wink posted Aug 29, 2024
TFW you deploy and then notice that you don't know where you deployed to.
Good thing is that it's just a static webpage, so a couple files...
Problems can be classified by difficulty into either be p, np, or npm.
Remember to keep pirating Disney content so they aren't allowed to kill your wife
PRO TIP: if you’re trying to pitch a rewrite of an old library, write down in your document that it’s from “the late 1000’s”. It doesn’t really do anything for your case but your leadership is going to make REALLY funny faces
wink posted Jul 30, 2024
What the actual fuck, Grafana?
> To Unsubscribe, please click on the unsubscribe link in a Grafana Labs email that you received
> You may also be seeing this message as a result of an ad blocker or disabled javascript/cookies. Please email REDACTRD and we will manually unsubscribe you.
Http needs a status code for grudging acceptance. We have 202 Accepted. We need 222 Tolerated.
For when the client is doing it wrong, but you've decided to be the bigger person and deal with it anyway.
wink posted Jul 17, 2024
First evening back from vacation and already had to read so many bad takes. Maybe I should filter out boosts.
wink posted Jul 2, 2024
I have this coding setup at home where I run an x server on a Debian WSL VM via mobaxterm and connect to my Arch VM on my home server via virt-manager. (Yes, it sounds complicated and no, it's really not).
Because of the ssh thing I just did a `pacman -Syu` this morning and now I have Plasma 6.1 on Wayland where I believe it was Plasma 6.0 on X before that.
First thing I noticed is that my `xrandr --newmode; xrandr --addmode` custom resolution doesn't work anymore but, much worse, now the connection seems to have this tiny bit of VM lag you probably all know, whereas before that this was the best VM experience I've had in my life. No difference to working locally.
And this is just one more example of "this is why we criticize Wayland adoption." Now I have to spend time figuring this out, can only hope I can fix it and before everything was working perfectly.
Yes, maybe it's Arch's fault for setting some weird defaults, maybe it's my own fault for running anything but a normal system on a normal laptop, but in the end it broke the principle of least surprise and the only obvious thing that has changed is Plasma 6.1 on Wayland.