< oharvey20>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< darkmage6>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< wloncom>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< vhasi22>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< Al_lA>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< zig>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< fanquake>
sipa / wumpus / luke-jr ^
< lithammer>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< gwillen>
fwiw I am a relatively experienced chanop, an op in #bitcoin and related channels, highlight on ! ops, and willing to ban people who need it, should this channel be desirous of more ops
< gwillen>
although it seems that the network is mostly taking care of these particular ones as they appear
< alephnull2>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< bvitnik8>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< luke-jr>
fanquake: I don't see a good ban mask that would work :/
<@gwillen>
I think this is a legit botnet unfortunately, so there probably isn't one
<@gwillen>
it's targeting freenode, not us
<@luke-jr>
I suppose if it gets bad enough, we can just set the channel to only allow registered users : /
<@gwillen>
a temporary +i, +k, +r would work
<@gwillen>
yeah
<@gwillen>
I would suggest setting +r for a few hours and then taking it off
<@gwillen>
but also, spam in the middle of the night is really only messing up scrollback, so maybe it's not worth it
< gmaxwell>
it's pretty harmless overall.
< gmaxwell>
you can quiet unregisterd, though people tend to forget to turn it off
<@gwillen>
*nods*
<@gwillen>
elsewhere I have done "ban unregistered with exemptions" but that seems unmanageable at the size of this channel
< poopster17>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
< distantorigin>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
<@luke-jr>
hm, if they only post one message, kicking may not be useful
<@luke-jr>
how do we quiet unregistereds?
<@gwillen>
let me find the syntax for that
<@gwillen>
+q $~a
< nightfrog28>
read about the new exciting pedo-friendly linux distribution https://exherbo.com/
<@luke-jr>
gwillen: ops still see messages, right? so if someone wants to talk, we can make the exception?
<@gwillen>
now we do
<@gwillen>
(this is what +z does)
<@luke-jr>
cool
<@gwillen>
only people with channel mode +o though (@), not people with chanserv access
< wumpus>
oh no
<@fanquake>
wumpus bit of a pain
<@fanquake>
in the mean time though, #15510 should be mergable.
<@fanquake>
I'm ~ given we haven't had anyone else report. If you think it's still worthwhile I'll grab that change and put it across all *BSD docs.
< wumpus>
I'd prefer not to make the change, it seems wrong
<@fanquake>
The original issue in 14404 also hasn't received any more follow up.
< wumpus>
it's necessary to work around a specific bug in automake/autoconf on BSD, but if it was solved I'd prefer not to "pollute" our docs with a strange work-around like this
<@fanquake>
Fair enough. I'll close it for now, and might follow up in 14404
< wumpus>
agree that's the best course of action for now
< wumpus>
good, it worked; [bitcoin-git] is logged in as bitcoin-git
<@fanquake>
Is #15453 a blocker for the 0.18 branch off? The issue should be constrained to self compiling with qt 5.7 (debian 9.x).
< gribble>
https://github.com/bitcoin/bitcoin/issues/15453 | Starting bitcoin-qt with -nowallet and then opening a wallet does not show the wallet · Issue #15453 · bitcoin/bitcoin · GitHub
<@fanquake>
Ideally any fix (potentially #15453) should be backportable.
< gribble>
https://github.com/bitcoin/bitcoin/issues/15453 | Starting bitcoin-qt with -nowallet and then opening a wallet does not show the wallet · Issue #15453 · bitcoin/bitcoin · GitHub
< wumpus>
no, I don't think that needs to block the 0.18 branch-off
< wumpus>
it's always backportable if needed
< meshcollider>
agree
< wumpus>
I don't think I'm going to wait for #15486 and #15402 either
< gribble>
https://github.com/bitcoin/bitcoin/issues/15486 | [addrman, net] Ensure tried collisions resolve, and allow feeler connections to existing outbound netgroups by sdaftuar · Pull Request #15486 · bitcoin/bitcoin · GitHub
< wumpus>
looks like both still have very active review going on, haven't stabilized enough for merge
<@fanquake>
ack - should both be backportable
< bitcoin-git>
[bitcoin] darosior closed pull request #15511: RPC : More user-friendly services field in getnetworkinfo and getpeerinfo (master...services_for_humans) https://github.com/bitcoin/bitcoin/pull/15511
< wumpus>
ok, going to branch off 0.18 in a minute
< bitcoin-git>
bitcoin/master c9985c8 Wladimir J. van der Laan: build: Bump version to 0.18.99
< instagibbs>
\o/
< instagibbs>
no idea what this message is about, but got it on 0.18 : 2019-03-02T14:22:33Z GUI: QXcbWindow: Unhandled client message: "_COMPIZ_TOOLKIT_ACTION"
< wumpus>
I think it's okay, that doesn't look like anything generated by our code at least, looks like simply an unhandled hint from the window manager to the client