| 00:19.49 | *** join/#qi-hardware infobot (ibot@208.53.50.136) |
| 00:19.49 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben/atusb 802.15.4 wireless, anelok and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 00:19.49 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 01:40.50 | *** join/#qi-hardware Ben6424 (~Ben64@535351E8.cm-6-4b.dynamic.ziggo.nl) |
| 01:40.50 | Ben6424 | With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ |
| 01:40.50 | Ben6424 | I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ |
| 01:40.50 | Ben6424 | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate |
| 01:40.53 | Ben6424 | A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ |
| 01:41.56 | *** join/#qi-hardware sdx2312 (~sdx23@180.64.100.78) |
| 01:42.00 | sdx2312 | With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ |
| 01:42.03 | sdx2312 | I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ |
| 01:42.06 | sdx2312 | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate |
| 01:42.10 | sdx2312 | A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ |
| 01:48.14 | *** join/#qi-hardware GuntherDW8 (~GuntherDW@187.114.181.233) |
| 01:48.58 | *** join/#qi-hardware dos1 (~dos1@neo900/coreteam/dos) |
| 01:56.05 | *** join/#qi-hardware conno (~conno@cpe-74-72-170-105.nyc.res.rr.com) |
| 01:56.54 | *** join/#qi-hardware Gentle (~Gentle@180.70.132.106) |
| 01:56.58 | Gentle | With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ |
| 01:57.01 | Gentle | I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ |
| 01:57.05 | Gentle | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate |
| 01:57.08 | Gentle | A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ |
| 02:00.55 | *** join/#qi-hardware pskosinski27 (~pskosinsk@222.254.15.220) |
| 02:00.55 | pskosinski27 | With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ |
| 02:00.55 | pskosinski27 | I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ |
| 02:00.55 | pskosinski27 | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate |
| 02:00.59 | pskosinski27 | A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ |
| 02:07.26 | eintopf | :-( |
| 02:08.02 | *** mode/#qi-hardware [+o DocScrutinizer05] by ChanServ |
| 02:08.04 | *** mode/#qi-hardware [+q $~a] by DocScrutinizer05 |
| 02:08.06 | *** mode/#qi-hardware [-o DocScrutinizer05] by ChanServ |
| 02:10.54 | *** join/#qi-hardware dystopia_ (~dystopia_@softbank060070043209.bbtec.net) |
| 02:13.32 | *** join/#qi-hardware Jguy13 (~Jguy@24.61.93.153) |
| 02:15.14 | *** join/#qi-hardware zaratustra8 (~zaratustr@softbank126066177249.bbtec.net) |
| 02:15.51 | *** join/#qi-hardware Praise8 (~Praise@205.185.223.198) |
| 02:26.29 | *** join/#qi-hardware JollyRgrs6 (~JollyRgrs@5.138.218.133.dy.bbexcite.jp) |
| 02:38.53 | *** join/#qi-hardware FiendKing04 (~FiendKing@211.210.191.174) |
| 02:39.31 | *** join/#qi-hardware mist10 (~mist@softbank126114096050.bbtec.net) |
| 02:50.16 | *** join/#qi-hardware BurningPrincess2 (~BurningPr@201.59.156.234) |
| 03:06.55 | *** join/#qi-hardware radiofree25 (~radiofree@190.214.218.223) |
| 03:14.54 | *** join/#qi-hardware nikivi21 (~nikivi@210.108.182.168) |
| 03:19.18 | *** join/#qi-hardware Guest94342 (~lestaty@173.245.203.190) |
| 03:19.50 | *** join/#qi-hardware lynxis6 (~lynxis@183.107.147.172) |
| 03:32.12 | *** join/#qi-hardware purrdeta4 (~purrdeta@209.107.204.86) |
| 03:37.07 | *** join/#qi-hardware musician_pro (~musician_@222.107.137.9) |
| 03:51.06 | *** join/#qi-hardware ripdog23 (~ripdog@156.194.92.92) |
| 04:08.16 | *** join/#qi-hardware eintopf (~eintopf@unaffiliated/eintopf) |
| 04:12.56 | *** join/#qi-hardware zaberdampfer (~zaberdamp@219.23.223.223.megaegg.ne.jp) |
| 04:35.58 | *** join/#qi-hardware sb0 (~lekernel@138019140155.ctinets.com) |
| 04:36.11 | *** join/#qi-hardware eintopf (~eintopf@unaffiliated/eintopf) |
| 04:36.57 | *** join/#qi-hardware basic`15 (~basic`@185.206.225.222) |
| 04:45.17 | *** join/#qi-hardware rwg13 (~rwg@59.2.39.66) |
| 04:55.02 | *** join/#qi-hardware mikedlr0 (~mikedlr@183.98.112.208) |
| 04:58.43 | kyak | these times, when i regret that messages can't be deleted from a channel, like in telegram |
| 04:59.54 | *** join/#qi-hardware jwhisnant19 (~jwhisnant@119.86.198.239) |
| 05:00.31 | *** join/#qi-hardware Matrixiumn (~Matrixium@cpe-72-225-203-214.nyc.res.rr.com) |
| 05:00.58 | kyak | #openwrt doesn't seem to be affected with this spam. They have +s set. I think i'm gonna set it for a while. It will hide the channel from channel list |
| 05:02.27 | *** mode/#qi-hardware [+s] by ChanServ |
| 05:08.58 | *** join/#qi-hardware __idiot__ (~goirc@186-90-177-111.genericrev.cantv.net) |
| 05:09.07 | kyak | +r also sounds like a good idea (Prevents users who are not identified to services from joining the channel.). Let's see how +s will work first |
| 05:32.53 | *** join/#qi-hardware Loki15 (~Loki@c25-191.actv.ne.jp) |
| 05:35.40 | *** join/#qi-hardware hammond4 (~hammond@cpe-174-104-46-50.neo.res.rr.com) |
| 05:51.50 | *** join/#qi-hardware OwenBarfield (~OwenBarfi@i114-189-131-235.s41.a016.ap.plala.or.jp) |
| 05:54.46 | *** part/#qi-hardware rozzin (23963ea3bf@feep.hackerposse.com) |
| 05:57.27 | *** join/#qi-hardware ravioli8 (~ravioli@41.37.37.193) |
| 06:03.19 | *** join/#qi-hardware cheapie27 (~cheapie@125.163.214.13) |
| 06:05.54 | *** join/#qi-hardware ephemer0l_27 (~ephemer0l@202.81.87.52) |
| 06:05.54 | *** join/#qi-hardware MobileMatt (~MobileMat@216.151.183.158) |
| 06:14.09 | *** join/#qi-hardware DLange7 (~DLange@46.246.123.88) |
| 06:15.21 | *** join/#qi-hardware ephemer0l_103 (~ephemer0l@2804:f24:c000:1:a824:720c:dde6:803a) |
| 06:33.39 | *** join/#qi-hardware FiendKing04 (~FiendKing@59.11.201.41) |
| 06:33.43 | *** join/#qi-hardware FastLizard417 (~FastLizar@81.211.101.18) |
| 06:49.59 | *** join/#qi-hardware Guest2809 (~nullcone@nz1l4.bb60246.ctm.net) |
| 07:00.48 | *** join/#qi-hardware marcoslater (~marcoslat@178.46.52.194) |
| 07:06.28 | *** join/#qi-hardware todevil (~todevil@89.190.75.252) |
| 07:38.58 | *** join/#qi-hardware DenSchub19 (~DenSchub@46.29.219.215) |
| 07:55.16 | *** join/#qi-hardware nortoh (~nortoh@58.125.172.92) |
| 07:58.35 | *** join/#qi-hardware Tabmow3 (~Tabmow@203.229.97.28) |
| 08:00.18 | *** join/#qi-hardware idn (~idn@211.178.111.209) |
| 08:12.58 | *** join/#qi-hardware blocked21 (~blocked@192.155.99.3) |
| 08:20.50 | *** join/#qi-hardware prettymuchbryce2 (~prettymuc@118.68.100.229) |
| 08:21.14 | *** join/#qi-hardware sb0 (~lekernel@59.152.213.90) |
| 08:22.18 | *** join/#qi-hardware jwhitmore (~jwhitmore@109.79.190.94) |
| 08:41.35 | *** join/#qi-hardware kaniini_ (~kaniini_@81.171.58.112) |
| 08:45.05 | *** join/#qi-hardware HarryS5 (~HarryS@113.173.216.196) |
| 08:55.57 | *** join/#qi-hardware Kamilion2 (~Kamilion@69.16.147.54) |
| 08:57.18 | *** join/#qi-hardware Menche3 (~Menche@37.79.145.110) |
| 09:08.49 | *** join/#qi-hardware ovoldemorto (~ovoldemor@124.227.196.114) |
| 09:09.49 | *** join/#qi-hardware jwhitmore (~jwhitmore@109.79.190.94) |
| 09:09.57 | *** join/#qi-hardware dos1 (~dos1@neo900/coreteam/dos) |
| 09:12.03 | *** join/#qi-hardware chek18 (~chek@182.31.123.50) |
| 09:18.16 | *** join/#qi-hardware eintopf (~eintopf@unaffiliated/eintopf) |
| 09:30.40 | *** join/#qi-hardware Necrosporus (~Necrospor@unaffiliated/necrosporus) |
| 09:35.02 | *** join/#qi-hardware Chords (~Chords@211.215.245.49) |
| 10:00.50 | *** join/#qi-hardware Neobenedict (~Neobenedi@softbank126116171175.bbtec.net) |
| 10:02.13 | *** mode/#qi-hardware [+r] by ChanServ |
| 10:04.36 | *** mode/#qi-hardware [-s] by ChanServ |
| 11:08.36 | DocScrutinizer05 | +r os nonsense, we already had +q $~a |
| 11:09.09 | *** mode/#qi-hardware [+o DocScrutinizer05] by ChanServ |
| 11:09.11 | DocScrutinizer05 | cmode -r |
| 11:09.13 | *** mode/#qi-hardware [-o DocScrutinizer05] by ChanServ |
| 11:09.31 | kyak | whatever we had, it didn't help |
| 11:09.51 | DocScrutinizer05 | where did it not help? |
| 11:10.04 | DocScrutinizer05 | after [01.08.18 04:08:04] *** DocScrutinizer05 sets mode: +q $~a |
| 11:10.28 | kyak | -!- mode/#qi-hardware [+Cnrt] |
| 11:10.38 | DocScrutinizer05 | huh? |
| 11:10.43 | kyak | huh? |
| 11:10.52 | DocScrutinizer05 | try /cmode q |
| 11:10.52 | kyak | where did you set the mode? |
| 11:11.12 | kyak | what's cmode? |
| 11:11.17 | kyak | [freenode] -!- cmode Unknown command |
| 11:11.37 | DocScrutinizer05 | /mode <channel> q |
| 11:11.57 | kyak | ah! |
| 11:12.25 | kyak | how does $~a mask work? |
| 11:12.49 | *** mode/#qi-hardware [-r] by ChanServ |
| 11:12.49 | DocScrutinizer05 | $ extban, ~ negates, a authenticated |
| 11:13.31 | DocScrutinizer05 | https://freenode.net/kb/answer/extbans |
| 11:13.34 | kyak | so it basically does the same as +r, only in a much more obfuscated and hidden way? |
| 11:14.00 | DocScrutinizer05 | no, +r is a join ban, q is a quiet ban |
| 11:14.28 | kyak | and the difference is.. ? |
| 11:14.39 | DocScrutinizer05 | +b $~a == +r |
| 11:15.07 | kyak | it says that "Prevents users who are not identified to services from joining the channel." |
| 11:15.08 | DocScrutinizer05 | the difference is the one works on join, the other on talking |
| 11:15.34 | kyak | So they wouldn't be able even to join. Since the channel is +n, they wouldn't be able to talk anyways |
| 11:15.56 | DocScrutinizer05 | see FN kb |
| 11:16.38 | kyak | i'm seeing it right here https://freenode.net/kb/answer/channelmodes |
| 11:17.04 | DocScrutinizer05 | so what's your question? |
| 11:17.32 | kyak | Cannot join channel (+r) - you need to be identified with services |
| 11:17.37 | DocScrutinizer05 | q and b bans are explaned there correctly |
| 11:18.49 | DocScrutinizer05 | this was a quoze by you, not a question you put |
| 11:19.13 | kyak | ok |
| 11:19.26 | kyak | what's the point of them joining the channel then? |
| 11:19.43 | DocScrutinizer05 | the point is legit users also can join and listen |
| 11:20.46 | kyak | but in reality, it just spams the scrollback buffer with irrelevant joins/quits |
| 11:21.29 | DocScrutinizer05 | your client has hide join/quit/nicj option for this. If not, get a better client or get over it |
| 11:29.00 | *** join/#qi-hardware captain4225 (~captain42@113.162.174.76) |
| 11:33.28 | DocScrutinizer05 | if you really feel the joins(parts are so disruptive that we prfer to ban legit users than suffering those join/part msgs, feel free to set +r again. It's a question of priorities and style of the particular channel |
| 11:46.11 | *** join/#qi-hardware jwhitmore (~jwhitmore@109.79.190.94) |
| 11:51.35 | kyak | DocScrutinizer05: nah, i'm fine with the way things are now. As an advantage, we will be able to see when the spam wave is over and remove the q $~a |
| 11:57.15 | DocScrutinizer05 | yep :-) |
| 11:59.11 | DocScrutinizer05 | btw the worst spam attack I ever seen on FN |
| 12:00.24 | kyak | yeah |
| 12:00.36 | DocScrutinizer05 | channels like #suse or #kde became defunct until chanops set $~a |
| 12:01.37 | kyak | they should probably handle it on a server level. The messages are not very varying - i don't know if freenode's ircd has network-wide filters |
| 12:01.46 | kyak | unrealircd has it |
| 12:05.44 | DocScrutinizer05 | yeah. Been duiscussed a zillion times with FN staff. The one elephant on the road: FN has an *absolute* "we don't filter your data" policy (even while it's not true - they *do* filter e.g. for color codes) |
| 12:07.02 | *** join/#qi-hardware nickenchuggets (~nickenchu@64.145.79.129) |
| 12:09.21 | *** join/#qi-hardware depleted (~depleted@39.113.13.197) |
| 12:09.59 | DocScrutinizer05 | I suggested to implement a FIFO buffer in the range of 0.1 to 2s (adjusttable) in ircd, to delay pushing-out messages to clients. During that delay, a "fastpath" connection ircd<->sigyn will provide the sigyn/whatever antispam bot with the data early, and a "kline this user" reply from the antispam bot could arrive just in time to purge any posts from the rogue spammer user from the buffer before those posts/msgs get deployed to |
| 12:10.01 | DocScrutinizer05 | regular users |
| 12:11.25 | DocScrutinizer05 | same concept could work on local domain (your irc client) as well, and I'm just looking into concepts how to patch a client or implement a local transparent proxy or even a ZNC plugin for exactly this |
| 12:13.02 | *** join/#qi-hardware Ritche20 (~Ritche@196.46.202.80) |
| 12:13.17 | DocScrutinizer05 | in ZNC I think such FIFO would be already implemented, just you need to make use of it also when the client is connected to ZNC. And you need to add the timers and the cleaning stuff |
| 12:18.57 | *** join/#qi-hardware swarfega1 (~swarfega@FL1-119-239-150-78.hrs.mesh.ad.jp) |
| 12:22.40 | kyak | this sounds complicated. In unrealircd, it is a simple spamfilter that sits in front: https://www.unrealircd.org/docs/Spamfilter |