Chat logs of #funderscore for Wednesday, 2024-08-21

09:15 *** Quits: fireonlive/h (fire@hackint/user/fireonlive) (Killed (NickServ (GHOST command used by fireonlive_)))

09:24 *** Joins: fireonlive/h (fire@hackint/user/fireonlive)

09:24 *** moist/h sets mode: +o fireonlive/h

09:38 <f_> In other news, I switched to sway

09:38 *** f_ sets mode: +oo f_[s] f_[x]

09:38 *** f_ sets mode: +o f_[l]/h

09:38 *** f_ sets mode: +qq f_[s] f_[x]

10:12 <f_> *crickets*

10:12 <f_> I used to use dwl, but for the n-th time it broke after an update

10:49 <Mb> duje|X> kde just werks for me

11:09 *** Joins: tweezers[feddy] (~tweezers[@103.108.229.58)

11:10 <f_> duje: I like using window managers :D

11:10 <Mb> duje|X> i too used to use dwm

11:11 <Mb> duje|X> but now im in a stage of life where i need a functioning computer /shrug

11:11 <f_> Yeah I used dwm a looong time ago, ditched it for dwl

11:11 <Mb> duje|X> and ive been through dwl, sway and friends as well

11:12 <f_> Now dwl broke, and I don't want to spend a long time getting it to recompile correctly

11:12 <f_> I have nothing against dwl, just sometimes it's painful :D

11:12 <Mb> duje|X> in other news it seems that duckdns is now somewhat responsive

11:13 <f_> I just need a good statusbar thing

11:13 <f_> need to show battery percentage, network status, and such

11:14 <Mb> duje|X> just use linux mint lol

11:14 <f_> haha

11:15 <f_> definitely better than ....Microsoft Windows :S

11:15 <Mb> duje|X> is there even anything wrong with mint?

11:15 <Mb> duje|X> besides maybe the fact that it uses systemd

11:15 <f_> The fact that it uses systemd is not an issue for me

11:15 <f_> I don't use systemd because I used systemd most of the time and at one point wanted a change

11:16 <Mb> duje|X> same here as long as it works

11:16 <Mb> duje|X> i actually had an issue somewhat recently with it killing caddy on my VPS repeatedly

11:16 <f_> I actually install Linux Mint on others' computers

11:16 <Mb> duje|X> i have it on my laptop

11:17 <Mb> duje|X> workstation is artix

11:17 <f_> At one point I think it would be nice to switch to postmarketOS, maybe have an OpenBSD install on a separate hard drive too

11:17 <f_> because I've been also willing to try OpenBSD at some point

11:17 <Mb> duje|X> only problem with that is im not sure anything is as easy to upgrade as debian based distros

11:17 <f_> Sadly, Wayland support there is meh. But there's work on-going for that

11:18 <f_> duje: I say: Use whatever works best for your workflow

11:18 <Mb> duje|X> apt just does it right, even if its slow and the package format (as in APKBUILD/PKGBUILD) is clumsy

11:18 <f_> apt doesn't use APKBUILD?

11:18 <Mb> duje|X> it doesnt

11:18 <Mb> duje|X> im referring to its equivalent

11:18 <f_> apk you mean?

11:18 <Mb> duje|X> no, i mean apt

11:18 <f_> > apt just does it right, even if its slow and the package format (as in APKBUILD/PKGBUILD) is clumsy

11:18 <Mb> duje|X> i should have said "package build recipe format"

11:19 <f_> ah, ok

11:19 <Mb> duje|X> apt uses gnu make for that

11:19 <f_> Well, I did not look into it, I will say

11:19 <Mb> duje|X> and from what ive seen documentation is kind of meh, though you can find a random blog post talking about how to package stuff for debian

11:20 <Mb> f_|X> But like I said, use whatever you believe will empower your workflows

11:20 <Mb> f_|X> I personally like window managers because of how organised I am while using them

11:20 <Mb> f_|X> er, tiling window managers

11:21 <Mb> f_|X> but you may like KDE for whatever reason

11:21 <Mb> f_|X> :)

11:22 <Mb> f_|X> Hey, I have nothing against others using Microsoft Windows, even, as long as they're aware of its drawbacks.

11:23 <Mb> f_|X> One DE/OS won't be fit for everyone. Choice is important.

11:23 <rx> i find most desktop environments to give me a nonfunctioning computer

11:23 <rx> or, at least a computer that i can't use properly

11:23 <Mb> f_|X> > <rx/rx> i find most desktop environments to give me a nonfunctioning computer

11:23 <Mb> f_|X> rx/rx

11:23 <rx> hi

11:24 <rx> my status bar is this:

11:24 <rx> #include <stdio.h>

11:24 <rx> #include <time.h>

11:24 <rx> #include <unistd.h>

11:24 <rx> #include <fcntl.h>

11:24 <rx> #include <stdint.h>

11:24 <rx> #define MAXLEN 4

11:24 <rx> time_t t;

11:24 <rx> char buf[MAXLEN + 1];

11:24 <rx> size_t len;

11:24 <rx> struct tm td;

11:24 <rx> int fdc, fds;

11:24 <rx> time_t t1;

11:24 <rx> int main()

11:24 <rx> {

11:24 *** rx was kicked by f_ (no spam)

11:25 <f_> runxi doesn't like pasting to a pastebin :P

11:25 <runxiyu> i forgot i was on your channel

11:25 <runxiyu> https://git.sr.ht/~runxiyu/rxbar

11:25 <runxiyu> i think that's the url

11:25 *** Joins: rx (ntpsec@netadmin.irc.runxiyu.org)

11:25 <runxiyu> oh  ican ctrl+shift+u to type unicode?

11:25 <runxiyu> nice

11:25 <f_> > rxbar, Runxi's Stupid Status Bar

11:25 <rx> yes, it is very stupid

11:25 <rx> i wrote it to avoid shell scripts

11:26 <rx> because calling printf and cat takes too many resources for somehing that runs every second

11:26 <f_> I have a neat notification center on my sway env

11:26 <rx> nice

11:27 <rx> i just use my ancient dunst setup

11:27 <rx> from the dwm days or something

11:27 <f_> https://github.com/ErikReider/SwayNotificationCenter

11:27 <f_> I used dunst as well

11:27 <hax[xor]> rx: how does this not implode?

11:28 <rx> hax[xor]: why would it implode

11:28 <rx> yes the timing is still broken but i don't really care

11:28 <hax[xor]> rx: buffer overflow

11:28 <rx> hax[xor]: eh?

11:28 <rx> oh

11:28 <hax[xor]> char buf[MAXLEN + 1]; pread(fdc, buf + 1, MAXLEN, 0); %s, buf

11:28 <rx> off by 1

11:28 <rx> my bad

11:28 <rx> it doesn't implode for me :P

11:29 <rx> it'll probably implode on openbsd

11:29 <rx> er, openbsd doesn't have /sys so it'll implode anyways

11:29 <hax[xor]> probably because pread only ever returns up to three characters there

11:29 <rx> eh? valgrind is not compaining

11:29 <rx> no, i have pread return 4 before

11:29 <hax[xor]> on /capacity?

11:29 <rx> yeah

11:29 <rx> 100\n

11:30 <hax[xor]> is it at 100% rn?

11:30 <hax[xor]> oh yeah \n

11:30 <rx> not right now

11:30 <rx> charging, 47%

11:30 <hax[xor]> then that's why valgrind isn't complaining rn

11:30 <rx> yeah

11:30 <rx> i guess that explains why my status bar crashes every month

11:30 <rx> it's always monday though

11:31 <hax[xor]> well, it probably doesn't actually cause any problems bc alignment

11:32 <f_> In other other news, I'm working on a matterbridge API thing

11:32 <rx> f_ has same color as rx

11:32 <rx> that confuses me

11:32 <f_> rx: me too

11:33 *** f_ is now known as funderscore

11:33 <funderscore> Now I no longer do :S

11:33 <funderscore> :D

11:33 *** f_/oftc is now known as funderscore/oftc

11:33 <hax[xor]> f_ and rx are different colors here

11:33 <hax[xor]> funderscore/oftc and rx are the same color however

11:33 <hax[xor]> but the length makes it a bit obvious :p

11:33 <funderscore> because Wee Enhanced Environement for Chat uses a different algo

11:34 <rx> Weeeeeeeeeeeeee

11:34 <rx> slow

11:34 <hax[xor]> also nicely rx and runxiyu are the same color :P

11:34 <rx> WeChat[tm]

11:34 <hax[xor]> lol

11:34 <funderscore/oftc> WeeChat™

11:37 <rx> ouch

11:37 <rx> so... senpai -debug writes debug information into the *current* buffer

11:38 <rx> rather than the server buffer

11:38 <rx> that's... kinda unusable

11:45 <hax[xor]> hey, at least it's not throwing it to stdout :D

11:46 <rx> wait

11:46 <rx> i think i could actually do that

11:46 <f_/h> There's a reason why it's not enabled by default

11:46 <f_/h> and why it's called... "debug"

11:47 <rx> weechat's /server raw puts things in a separate raw buffer

11:47 <hax[xor]> f_/h: doesn't mean they have to pick the least usable option available

11:47 <rx> which is very useful if i want to use irc normally and occasionally check the raw lines

11:57 <Mb> f_|X> rx: ask #senpai

12:50 *** funderscore/oftc is now known as f_/oftc

12:56 *** Quits: tweezers[feddy] (~tweezers[@103.108.229.58) (Ping timeout: 240 seconds)

13:37 *** f_[x] is now known as f_

13:37 *** f_ is now known as 100AAAALZ

13:38 *** 100AAAALZ is now known as f_[x]

15:08 *** Joins: tweezers[feddy] (~tweezers[@103.108.229.74)

15:11 *** Quits: tweezers[feddy] (~tweezers[@103.108.229.74) (Quit: Leaving)

15:25 *** Joins: tweezers[feddy] (~tweezers[@103.108.229.74)

15:59 *** Quits: tweezers[feddy] (~tweezers[@103.108.229.74) (Ping timeout: 240 seconds)