Chat logs of #funderscore for Friday, 2024-08-16
08:09 <dujem/oftc> f_: besides https
08:14 *** Quits: tester (~tester@tor/onion) (The TLS connection was non-properly terminated.)
08:14 *** Joins: tester (~tester@tor/onion)
09:00 *** Joins: webirc-2d4j42n (~webirc-2d@webirc/webirc-2d4j42n)
09:14 <f_/oftc> dujem: Intentional to work on older browsers?
09:16 *** Quits: webirc-2d4j42n (~webirc-2d@webirc/webirc-2d4j42n) (Connection closed)
10:19 <dujem/oftc> f_: indeed
11:25 <f_> dujem: nice
11:26 <dujem/oftc> rx: to be fair i still need to make the website HTML4 compliant
11:26 <dujem/oftc> if you have any resources on how to write compliant HTML4 please do let me know
11:26 <runxiyu> good morning
11:26 <runxiyu> f_ was talking, rx is my other account's nick
11:27 <runxiyu> and is the name of our IRC network
11:27 <f_/oftc> Yeah, rx here is a relaybox
11:27 <f_/oftc> relaybot*
11:27 <dujem/oftc> ah good to know
11:27 <f_/oftc> I know I keep complaining about the matrix bridge, but I will say
11:27 <f_/oftc> I hate relaybots
11:28 <dujem/oftc> xmpp is obviously the supreme chat protocol, what else to say
11:28 <Mb> f_|X> I also hate them for this.
11:28 <f_/oftc> Yup. This is matterbridge -> pylink-relaybot -> oftc...
11:28 <runxiyu> dujem/oftc: I agree to disagree; XML is not appropriate for chat protocols
11:29 <Mb> f_|X> chat@conference.vitali64.duckdns.org by the way.
11:29 <dujem/oftc> runxiyu: XML or not it works fine for me
11:29 <Mb> f_|X> Oo forgot to update the topic here
11:30 <f_/oftc> runxiyu: yeah works fine for me too
11:30 <f_/oftc> Though IRC is also my favourite
11:30 <runxiyu> can we agree that matrix sucks
11:30 <dujem/oftc> absolutely
11:31 <dujem/oftc> this is fun, i just cant join the MUC
11:31 <dujem/oftc> getting a "This address is not reachable." on gajim
11:31 <dujem/oftc> f_: do you use a VPS or selfhost?
11:31 <f_/oftc> VPS
11:32 <f_/oftc> dujem: can you `ping vitali64.duckdns.org` and see what it gives?
11:32 <dujem/oftc> ah, no better here
11:32 <dujem/oftc> f_: took a while to resolve the domain from my workstation
11:32 <f_/oftc> IPv6 should be 2001:1600:10:100::4b9 and IPv4 should be 195.15.242.30
11:32 <dujem/oftc> and pings dont work
11:32 <f_/oftc> weird
11:32 <dujem/oftc> ipv4 is correct, ipv6 i actually do have but only through teredo
11:33 <f_/oftc> Maybe it's trying IPv6 and failing?
11:33 <dujem/oftc> nope
11:33 <Mb> f_|X> 💯
11:33 <dujem/oftc> ~ ping vitali64.duckdns.org
11:33 <dujem/oftc> PING vitali64.duckdns.org (195.15.242.30) 56(84) bytes of data.
11:33 <dujem/oftc> ^C
11:33 <dujem/oftc> --- vitali64.duckdns.org ping statistics ---
11:33 <dujem/oftc> 34 packets transmitted, 0 received, 100% packet loss, time 33813ms
11:33 <dujem/oftc> ~ ping -6 vitali64.duckdns.org
11:33 <dujem/oftc> ping: vitali64.duckdns.org: Address family for hostname not supported
11:33 <f_/oftc> ah ok
11:33 <f_/oftc> I don't think it responds to pings
11:33 <f_/oftc> But I just wanted to see if it resolves fine
11:33 <dujem/oftc> i also use duckdns for my little home server (hardly ever powered on nowadays) and i sure have issues with it
11:34 <dujem/oftc> also related to how long DNS queries take, if they even succeed
11:34 <f_/oftc> yeah I have issues with DuckDNS all the time
11:34 <f_/oftc> But the VPS itself is extremely stable
11:34 <dujem/oftc> alright, the VPS was even able to resolve the domain
11:34 <dujem/oftc> not without one timeout though
11:35 <dujem/oftc> and its no better than workstation with pinging
11:35 <dujem/oftc> curl works though
11:35 <f_> yeah, it doesn't respond to pings.
11:36 <f_> PING vitali64.duckdns.org (195.15.242.30) 56(84) bytes of data.
11:36 <f_> ^C
11:36 <f_> --- vitali64.duckdns.org ping statistics ---
11:36 <f_> 5 packets transmitted, 0 received, 100% packet loss, time 4062ms
11:36 <dujem/oftc> does this thing not cache DNS responses though?
11:36 <f_> That's to be expected
11:36 <dujem/oftc> really?
11:36 <f_/oftc> yep
11:37 <f_/oftc> But that doesn't mean it's dead
11:37 <f_/oftc> I mean, it doesn't respond to pings.
11:37 <f_/oftc> intentionally. Not sure why though
11:37 <dujem/oftc> you mean ICMP is blocked at provider level?
11:37 <f_/oftc> ¯\_(ツ)_/¯
11:37 <dujem/oftc> that makes perfect sense for home networks, not for this though
11:38 <f_/oftc> Anyway. It is indeed alive, my IRC bouncer is hosted there.
11:38 <f_/oftc> DuckServ: HELP
11:38 <DuckServ> ****** DuckServ Help *******
11:38 <DuckServ> DuckServ gives netadmins and normal users alike the ability
11:38 <DuckServ> to annoy everyone on the network, cause protcol violations,
11:38 <DuckServ> and a whole lot more. It is the successor to the vdoIRC bot.
11:38 <DuckServ>
11:38 <DuckServ> The following commands are available:
11:38 <DuckServ> TEST Sees if a sentence is true or false
11:38 <DuckServ> SPAM Repeats a message to a target <n> times
11:38 <DuckServ> RAW Sends a raw message to the server
11:38 <DuckServ> PING Sees if a sentence is true or false
11:38 <DuckServ> HELP Shows a list of commands
11:38 <DuckServ> EJECT Punishes a user for abusing me
11:38 <DuckServ> CLEAR Clears a channel
11:38 <DuckServ> ****** End of Help *******
11:38 <DuckServ> If you're having trouble or you need some additional help, do it yourselfâ„¢.
11:38 <f_/oftc> DuckServ too
11:39 <dujem/oftc> take 2 with the MUC
11:39 <Mb> f_|X> hi duje
11:39 <Mb> duje|X> 🎊
11:39 <Mb> duje|X> message timestamps seem a bit odd though
11:39 <f_/oftc> where?
11:39 <Mb> duje|X> https://uploads.dujemihanovic.xyz:5281/file_share/3bfe1716-807f-43fe-847b-105393a55fb3/a5d77014-40ac-4614-9edf-2b34f86410c4.png
11:39 <f_/oftc> Here?
11:40 <f_/oftc> Eh, that's a really hacky bridging setup I have.
11:40 <Mb> duje|X> sure
11:40 <f_/oftc> I don't like it
11:40 <Mb> duje|X> i got a bit carried away regarding what i wanted to do right now
11:40 <f_/oftc> In one hand, PyLink properly creates stateful server-side puppets on irc.runxiyu.org
11:40 <f_/oftc> In the other hand, it just does relaybot on other IRC networks
11:41 <f_/oftc> In the 3rd hand, it can't do XMPP so I have to glue in a matterbridge
11:41 <runxiyu> is it possible to join #funderscore@rx.trans.xmpp.vitali64.duckdns.org or whatever that is
11:41 <Mb> f_|X> runxiyu: yeah but it's not really native XMPP
11:42 <runxiyu> well, true
11:42 <Mb> f_|X> and I want native XMPP...
11:43 <Mb> f_|X> Not that the XMPP bridge is bad, in fact, unlike the Matrix bridge it's extremely good.
11:43 <Mb> f_|X> but that's just asking people to join the channel using a "3rd party" bouncer that happens to be controlled from XMPP
11:44 <f_> Still, bridging 10 million stuff together also might not be the best idea :P
11:45 <f_> see: #funderscore-sucks - there are 16 f_'s there, counting all alt connections I use.
11:45 <f_> and also counting aop[f_] on EFnet
11:47 <f_/h> aop[f_] is a ZNC that autoops people on EFnet, because EFnet has no ChanServ whatsoever :D
11:48 <f_/h> I'm not seriously running channels on EFnet by the way. I wouldn't seriously rely on EFnet for my channels..
11:58 <Mb> duje|X> does anyone in this room have native ipv6 at home? just curious
12:02 <runxiyu> me
12:02 <runxiyu> djue: ^
12:02 <runxiyu> duje ^
12:03 <runxiyu> duje: IPv4 is quite unstable for me though
12:03 <runxiyu> duje: IPv6 works fine
12:03 <Mb> duje|X> v6 working better than v4 is a first for me
12:21 <Mb> duje|X> here is one more interesting fact, it seems like public ipv4 addresses are quite a sizeable portion of VPS prices at least for one particular provider im currently checking out
12:21 <Mb> duje|X> specifically, a v4/v6 VPS with 1 vcore, 1gb ram and 25gb disk costs 2.90e per month there
12:21 <Mb> duje|X> on the other hand, that same provider offers a v6 only 2 vcore, 2gb ram and 75gb disk VPS for just 9 cents more
12:36 <f_/oftc> hah
12:52 <runxiyu> duje: That makes sense
13:00 <Mb> duje|X> runxiyu: well, hasnt there been a shortage of v4 addresses for more than a decade by now?
13:01 <runxiyu> exactly
13:01 <runxiyu> and I'm shamefully using four of them
13:38 *** Quits: f_[l] (thelounge@andrewyu.org) (Impostor removed.)
13:38 *** Joins: f_[l] (thelounge@andrewyu.org)
13:38 *** irc.andrewyu.org sets mode: +oq f_[l] f_[l]
14:32 *** Quits: tester (~tester@tor/onion) (The TLS connection was non-properly terminated.)
14:33 *** Joins: tester (~tester@tor/onion)
18:58 *** Quits: tester (~tester@tor/onion) (Ping timeout: 240 seconds)
19:12 *** Joins: tweezers (~tweezers@45.130.200.124)
19:14 *** Joins: tester (~tester@tor/onion)
19:25 *** Joins: tester1 (~tester@tor/onion)
19:25 *** Quits: tester (~tester@tor/onion) (Ping timeout: 240 seconds)
19:41 *** Quits: tweezers (~tweezers@45.130.200.124) (Ping timeout: 240 seconds)
19:43 *** Joins: tweezers (~tweezers@103.108.229.58)
21:17 *** Quits: tweezers (~tweezers@103.108.229.58) (Ping timeout: 240 seconds)
21:19 *** Joins: tweezers (~tweezers@103.108.229.74)
21:32 *** Quits: tweezers (~tweezers@103.108.229.74) (Ping timeout: 240 seconds)
21:32 *** Joins: tweezers (~tweezers@103.108.229.58)
23:25 *** Quits: tweezers (~tweezers@103.108.229.58) (Ping timeout: 240 seconds)
23:27 *** Joins: tweezers (~tweezers@103.108.229.74)
Generated by irclog2html.py 3.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!