ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
aarch64-bridge has quit [Remote host closed the connection]
aarch64-bridge has joined #aarch64-laptops
<steev> test
aarch64-bridge has quit [Remote host closed the connection]
aarch64-bridge has joined #aarch64-laptops
<steev> oh, god damn it
<steev> i think i know why it isn't relaying into here
<HdkR> +M?
<arnd> I just noticed that I'm registered as founder for that channel on libera and never handed it off to anyone else, assuming it wouldn't actually get used after this one started
<arnd> Should we just shut down the channel on libera?
<steev> arnd: i'd be fine with that, but i also have no problem running a bridge, there's one user there who absolutely refuses to come here because of the registered user requirement
<steev> i just need to actually register the bridge name :)
<arnd> steev: can't robclark just invite that user without requiring registration?
<steev> no idea, but they don't stay connected
<robclark> I assume the user doesn't want to do the registration thing needed for NickServ? Doesn't libra do something similar?
<robclark> I'm fine with the bridge too, as long as it doesn't become a spam bridge ;-)
<robclark> but haven't really seen spam problems since the early post-freenode days
<steev> the idea is/was that it would only do messages, no parts/joins/quits
<robclark> sure, I meant if the libra channel started getting spammed
<steev> oh, i hven't seen any issues there either
<steev> we bridge the kali channels between oftc and libera as well because... the kali community can be fickle
<steev> but that one is a full blown bot with faq responses and whatnot, the bridge would just be the bridge
<robclark> I think the libera channel also requires nickserv identification to speak, which seems to be enough to block spam
<steev> their name is "tables" so it's quite likely someone already registered that nick over here and they're mad about it. had a kali user with a similar issue and wanted me to figure out how to give their name back on oftc... and i had to explain to them that i have absolutely nothing to do with running oftc or nickname registrations
<steev> i gotta say, with lmh in place, it's nice to see that performance bump
<robclark> whois says there is no such nick over here
<steev> honestly, i don't care *that* much. definitely not enough to look into their issue(s), but i figure can at least bridge and know when they pop in and ask a question
pinskia has quit [Remote host closed the connection]
pinskia has joined #aarch64-laptops
norwoodites has joined #aarch64-laptops
pinskia has quit [Ping timeout: 480 seconds]
norwoodites is now known as pinskia
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
macc24 has quit [Quit: WeeChat 3.2]
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops