<<Prev Next>> Scroll to Bottom
Stuff goes here
L1[12:32:29]
<getItemFromBlock> %lua for i=1,15 do
print(i) end
L2[12:32:30] <MichiBot> 1 | 2 | 3 | 4 | 5 |
6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15
L3[12:33:05]
<getItemFromBlock> Interesting, it put the
values between pipes
L4[12:40:11] <Amanda> Yeah, IRC doesn't
support multi-like messages, and she's an IRC bot. Also sending
lots of lines at once can trigger network's anti-spam
L5[12:40:24] <Amanda> Multi-line
L6[12:41:25]
<RedstoneParkour> isn't there an IRC
extension for multi-line messages?
L7[12:41:52] <Amanda> I don't think so? But
it's been a hot minute since I looked
L9[12:42:38]
<RedstoneParkour> seems like its a
work-in-progress spec
L10[12:42:57] <Amanda> There was a hack
that some clients did that wasn't reliable of just sending \n since
the IRC protocol uses \r\n as a end message delimiter
L11[12:43:23] <Amanda> But some clients and
servers didn't like that so I think it fell out of favor
L12[12:44:01] <Amanda> Ah, I've not looked
at ircv3 stuff in years
L13[16:54:02]
<getItemFromBlock> Well pipes are still
better than nothing 🤷
L14[16:54:58]
<getItemFromBlock> Oh btw how do you see
discord emoji, do they translate to something like :.shrug: ?
L15[16:56:37]
<Forecaster> It depends on the
client
L16[16:56:42]
<Forecaster> And the emoji
L17[16:57:10]
<Forecaster> It will send :emoji_name: and
then it's up to the client what to do with that
L18[16:57:44]
<Forecaster> If it's a standard emoji and
the client supports those it may display it, if it's a custom one
it likely won't
L19[19:04:51]
<getItemFromBlock> I see, thx
L20[22:34:56] ⇦
Quits: Lizzy (~Lizzy@bode.theender.net) (Quit: whoops)
L21[22:34:56] ⇦
Quits: Forecaster (~Forecaste@bode.theender.net) (Quit: EnderNet
BNC)
L22[23:57:20] ⇨
Joins: Forecaster (~Forecaste@znc.theender.net)