#openbsd supplying an embroidery file to an embroidery machine. OpenBSD acts as a huge usb fob. The advantage here is you can see the thread colors more easily in Xpdf than by looking at the color code, in the tiny lcd, on the embroidery machine.
"if you're using bongo.rs to parse http headers, you will need to also install bepis to get buffered read support. but please note that bepis switched to using sasquatch for parallel tokenization as of version 0.0.67, so you will need the bongo-sasquatch extension crate as well."
old-time programming is like,
"i made a typo in this function in 1993. theo de raadt got so angry he punched a wall when he saw it. for ABI compatibility reasons, we shan't fix the typo."
@saddestrobots Funny and I agree with the overall sentiment, but #OpenBSD breaks ABI with every release.
I don't know Theo de Raadt, so can't say whether he would punch a wall, but he would likely have responded so gruffly as to make the typoist punch a wall.
I was doing some project work for a client and had to change some DNS settings at the registrar they use. I couldn't get past the login - seems that they launched a new control thingy that requires webassembly :flan_nooo:
@transip please get your act together.. WASM for a DNS panel is utter madness.
(and yes, right now, I can still use the old panel by entering the URL manually, but that is besides the point)
By default, browsers on OpenBSD aren't able to access ~/.ssh, ~/.gnupg and other sensitive userdata. Which makes so much sense - as a browser has grown into such a complex beast that a browser exploit could have disastrous consequenses. #OpenBSD limits this thoroughly.
I suspect that disabling WASM helps this OS-level sandboxing, but currently searching for the commit or more background I can link you.
Changed my #OpenBSD writing-dedicated box from running #cwm to #i3wm -- I like cwm, but it's still a bit too mousey for my taste.
I also changed all of my fonts (both xterm and i3/i3status) to be bitmapped (the "fixed" font), so everything is looking REALLY crisp.
Maybe I'm getting quite crochety, but at this point, I think I'd much rather have a lower res screen with crisp bitmapped fonts than a crazy high-res screen and vector fonts.
The only thing I'm missing is #emoji. My i3status looks like
cpu 31% | load 0.80 | mem 9% | dsk 13.4% | net Gallifrey 82% | chrg 89% 0.00W | Sun 2024.05.26 06:42 AM
instead of
cpu 05% | 📈 load 0.29 | 28.5% | disk 59.7% | Gallifrey 67% | Sun 2024.05.26 06:42 AM
> @rl_dane I have tried dealing with suckless software and patches, and the more patches you bring into st the more wacked out it becomes, it starts having weird issues, some of the patches don't gel well with each other, and hand merging them are not that much fun.
@thelinuxcast recently compared Gnome (needing extensions to be usable) to suckless' tools (needing patches to be usable), and now I see how that can go both ways (positive and negative). One time 5 years ago when I was trying to get along with Gnome, I had two conflicting extensions that filled up /var (which was /, derp) within minutes with log messages. sigh. As an old friend would say rather dismissively in these situations, "NEXT VICTIM!"
> Xorg is great, it still works, and you can pry it out of my cold dead hands, I don't see the value of wayland, sure it does things differently, but in my experience, even after well over a decade of work on it, it still doesn't really work well, it makes things harder for no good reason just "security" well if someone gets so into my box that they can execute code on it I'm screwed no matter what I have on there, I just don't really get it.
>
> Maybe some day it will catch up, but today, no today is not that day :p
I have recently re-tooled EVERYTHING to #Wayland: #i3wm -> #sway, and #KDE#Plasma 5.27 to Wayland(-mode), even though it's a touch buggy, and there are things I rely on like Xbanish that just have no replacement in Plasma+Sway. My only XOrg box now is my #OpenBSD box (now running i3, formerly #cwm).
Other than the issue of screen tearing when watching videos, and some purely theoretical performance improvements, I'm no better for being 99% Wayland now. Sway is great, and does absolutely everything I need (even though it's very slow to reload compared to i3wm for some reason), but that's only because the Sway community has done a lot of hard work to re-implement everything that the i3 community needed/wanted (or provide hacks/scripts to do the same). KDE+Wayland is not nearly as nice an experience.
So... uhh.. Wayland is THE WAVE OF THE FUTURE, but just as we have been suspecting for the past decade, the future kinda sucks. :P
Well, there is a reason I neither use GNOME, nor DWM, or ST :p
I have recently re-tooled EVERYTHING to #Wayland: #i3wm -> #sway, and #KDE#Plasma 5.27 to Wayland(-mode), even though it's a touch buggy, and there are things I rely on like Xbanish that just have no replacement in Plasma+Sway. My only XOrg box now is my #OpenBSD box (now running i3, formerly #cwm).
Exactly, there is the reason why I stay on Xorg, there is no real compelling reason to switch.
Other than the issue of screen tearing when watching videos, and some purely theoretical performance improvements,
Yeah, I've heard a lot of people talking about that, haven't really seen it in practice, might be that my brain just learned to compensate from watching too many ultracompressed, full of artifacts videos when I grew up :p
So... uhh.. Wayland is THE WAVE OF THE FUTURE, but just as we have been suspecting for the past decade, the future kinda sucks. 😛
Well I guess I'll leave the future up to the youngsters :p They can enjoy it as they want to, I'll stay here using my old tools for the time being at least :p
With Microsoft pushing their supercharged spyware soon, today is - like any other day - perfect to make the switch to #OpenBSD. The sane, well-documented, secure OS that isn't bloated and doesn't spy on you.
Another work week and another Monday morning ahead. :flan_hacker: Gonna need my morning #coffee and my #OpenBSD 7.4 shirt to keep me in good spirits. :flan_coffee: :puffer: :runbsdBg: