ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Friday, February 13, 2026

  1. dreamrealIt's just a lot of data to manage for little worthwhile value: each user has a provenance, as does a channel, and you COULD put metadata about timezone there if you didn't want the default
  2. dreamrealbut that's not the purpose of nevet, so it seems like a lot
  3. bluedreamreal: great men do not make excuses!
  4. blueanyway, it's probably not a good idea for nevet to store tzs, I agree. but I don't know that !today is very useful unless you have a timezone reference
  5. blueor at least, add the timezone
  6. dreamrealthat's because you're looking at it as a tool *for users* :D
  7. dreamrealwith that said, though... I dunno, the bot does keep track of identity, there's a potential for an "!about me" that would allow users to do stuff like that
  8. bluedreamreal: I would remove !today and !tomorrow, tbh. I'm not sure it's useful functionality in this form. A different functionality that is I think useful is time lookup using a zone
  9. bluetime Tokyo
  10. dreamrealWell, the edge was that I needed a "ping!" command, but I wanted it to have SOME use and options, and given that Java has solar calendars but not a Jewish solar calendar, I could "do both"
  11. dreamrealtomorrow is mostly a joke and an extension- you mentioned it, and it implied a fix to how "today" worked, so I put it in. :D
  12. dreamrealsorry, lunar
  13. dreamrealsick this week, not at my best
  14. bluemakes sense
  15. bluedreamreal: get well soon m8!
  16. dreamrealI need to finish the blog endpoints, make a UI as a baseline, and then work on stateful operations
  17. dreamreallike, I'd like to have a way to play 21 matches with the bot
  18. bluewhat on God's green earth is 21 matches?
  19. dreamrealSimple takeaway game. Rules: starts with 21 matches. The goal is to make the other player draw the "last match." The way it's played: turns, each player can take 1 to 4 matches.
  20. dreamrealSo... 21 matches. Your turn. How many matches are you taking?
  21. blue1
  22. dreamrealI take 3. 17 matches left. Your turn.
  23. blue1
  24. dreamrealI take 3 again. 13 matches left. Your turn.
  25. blue1
  26. dreamrealI take 3 again. 9 matches left. Your turn.
  27. blue1
  28. dreamrealI take 3 again. 5 matches left. Your turn.
  29. blue4
  30. dreamrealHah! I wrote the rules wrong. You'd have won. Thank you! - it's actually 1-3 matches.
  31. blueoh
  32. bluewell in that you'd have won
  33. dreamrealConcedo. I was playing badly with the rules I wrote.
  34. dreamrealBut yeah, the answer is for the second player to always run 4-other turn
  35. bluewell basically I wanted to leave you with 5
  36. dreamrealso if you take 1, I take 3, and so forth.
  37. blueya
  38. dreamrealYeah, I wrote the rules wrong, it's been a while. But it's a game I used to teach my kids programming and strategy.
  39. dreamrealthe way to win is very simple, so you can focus on how the programming works
  40. blueif it'd been 3, I'd have need to leave you with 4 each tur
  41. bluen
  42. blueneeded*
  43. dreamrealyeah, but with 1-3 matches from each player, player #2 will ALWAYS win unless they make a mistake
  44. blueya
  45. blueso nevet is to be programmed to always win, if it doesn't start, yes?
  46. dreamrealbut for the bot, that means establishing context for each provenance, and state preservation on that level would be useful
  47. dreamrealyeah, the "game" is in the programming, not the playing :D
  48. blueya
  49. dreamreal(a provenance is a conversation stream, so irc://libera/blue is YOUR provenance in the bot)
  50. dreamrealthis channel is irc://libera/#primate
  51. dreamreal(it's not a fully resolvable URL, the scheme is internal)
  52. dreamrealit's ingress+egress point (so "irc" as the service that is involved), authority (none for this), identifer (network is called 'libera' internally) and then the addressee
  53. bluemakes sense. I would use the ircname or so though?
  54. blueor account name
  55. dreamrealyeah, it actually does use the account name
  56. bluenice
  57. dreamrealso it can rely on libera SASL for authentication
  58. bluelibera is always not fully qualified, you might consider
  59. bluebetter irc.libera.chat or so
  60. dreamrealnon-authenticated accounts don't get authentication, you can't just manage to log in on libera and get an authority in the bot
  61. blues/always/also/
  62. dreamreal'libera' there is the internal name for irc.libera.chat
  63. dreamreallike I said, they're not externalizable urls
  64. blueah ok but then you need a mapping table
  65. dreamrealit has one
  66. blueyou can always just ues the cannonical name of the current network
  67. dreamrealit needs one because the console command is something like 'irc join libera #primate'
  68. bluethen you don't need a mapping table
  69. blues/always/also/
  70. bluefor discord you'd use the server id
  71. dreamrealbut then I DO need consistent schemes, and not every ingress/egress uses the same schemata
  72. dreamrealdiscord uses guild ids, not server ids
  73. blueirc://libera.chat.irc/blue is consistent
  74. dreamrealoh, did I tell you I got slack working?
  75. bluediscord://SOME_GUILD_ID/SOME_USER_ID is also consistent
  76. blueyou didn't
  77. bluethat'd be slack:// ?
  78. dreamrealWell now I have
  79. dreamrealyeah
  80. dreamrealI find I DESPISE slack as a programmable environment: establishing the connection is *brutal*
  81. blueslack is generally a dumpster fire
  82. dreamrealbut it's working: it's a total drag to set up, but it works. Once you've set it up, it's workable and it operates just like it does here and on discord
  83. blueq: can nevet now do bridging between irc, discord & slack?
  84. dreamrealI want to get mattermost and matrix up, too, but the blog is the next deliverable, I need to get a front end working. I have the RSS feeds working, although I haven't fully tested them out.
  85. dreamrealyeah, just like the earlier rev
  86. blueif so, I'd like to ask you to bring it into the primate server, and I'd create an irc channel for it? would that make sense?
  87. blueor maybe we'd sync the general channel simply
  88. dreamrealsee pm
  89. blueoki
  90. blueok, how do we link a discord channel to this?
  91. dreamrealso it depends on what you mean by "link"
  92. bluebasically, the idea is that any message here appears on discord as `(irc:USER) MESSAGE`, and vice versa
  93. dreamrealooof, crosspollination
  94. dreamrealum
  95. dreamrealso there's no facility for that... yet
  96. bluegood
  97. bluebut it'd be cool
  98. dreamrealIt's doable: it'd be an operation that watched for specific provenance on input (discord://guild/channel) and routed to a specific OTHER provance on egress (irc://libera/#primate)
  99. blueI can then create a channel #irc on discord, and the two places are synced
  100. blueYES
  101. dreamrealand vice versa, I suppose
  102. blueI can also then inform in the topic of that discord channel, that messages are syned to irc.libera.chat#primate, and vice versa in this topic
  103. dreamrealyeah
  104. dreamrealyour github nick is still earth-based, yeah?
  105. blueyes
  106. dreamrealsee pm again, confirmation
  107. dreamrealdefine blue
  108. nevetblue (noun): The colour of the clear sky or the deep sea, between green and violet in the visible spectrum, and one of the primary additive colours for transmitted light; the colour obtained by subtracting red and green from white light using magenta and cyan filters; or any colour resembling this.
  109. dreamreal:D
  110. dreamrealbridge provenance
  111. nevetirc://libera/%23primate
  112. bot<josephbottinger@discord> ello!
  113. bot<josephbottinger@discord> hello again!
  114. dreamrealdid this work?
  115. dreamrealooo it did work!
  116. dreamrealdefine source
  117. nevetdefine source: source (noun): The person, place or thing from which something (information, goods, etc.) comes or is acquired.
  118. bot<josephbottinger@discord> <@857685522533056522> yo!
  119. bot<blue@discord> wow!
  120. bot<josephbottinger@discord> fixing some QOL stuff now
  121. bot<blue@discord> can you link it with a specific channel here?
  122. bot<josephbottinger@discord> tell irc://libera/dreamreal you're a hosehead
  123. botMessage delivered to dreamreal
  124. bot<josephbottinger@discord> IT WORKED!
  125. bot<blue@discord> wow
  126. bot<josephbottinger@discord> i got a privmsg!
  127. bot<blue@discord> wow
  128. bot<blue@discord> ok, can we bridge him over the <#1471981297487577303> channel?
  129. bot<josephbottinger@discord> let me test the QOL first
  130. bluek
  131. bot<dreamreal> hello
  132. bot<discord://1256590312177012806/%23nevet-test/josephbottinger> it works still!
  133. bot<discord://1256590312177012806/%23nevet-test/josephbottinger> okay, what do you want the connection to be?
  134. dreamreali don't know if tell can figure out usernames on discord, there're some leaky bits
  135. bot<discord://1256590312177012806/#irc/josephbottinger> testing
  136. dreamrealtesting to send to discord
  137. dreamrealokay, connectivity working
  138. bot<discord://1256590312177012806/#irc/blue> yeah, only this channel
  139. bot<discord://1256590312177012806/#irc/josephbottinger> It only allows one participation at a time: this channel can be part of NO OTHER mirroring
  140. bot<discord://1256590312177012806/#irc/josephbottinger> you can't multiplex. A given provenance can be part of one and ONLY ONE mirroring set.
  141. bot<discord://1256590312177012806/#irc/josephbottinger> The mirroring can be one way or two way, however you want it, but it's exclusive
  142. bot<discord://1256590312177012806/#irc/josephbottinger> otherwise it's really easy to get super-abusive and overwhelm the event stream
  143. bluebtw, can you replace 1256590312177012806 with something else? or just drop it? it's irrelevant
  144. bluedreamreal: ^
  145. dreamrealIt's the channel name on discord. I'd LOVE to. Um... I'm not sure how yet. File an issue, please?
  146. dreamrealI did the same thing with usernames, so it should be doable
  147. bluebasically the only info that's relevant is that the message comes from an IRC user, and WHICH user. the rest is irrelevant
  148. bluealright
  149. dreamrealand the thing is: it shows the provenance of the external source. Like, you can see exactly what the full source is, internally: I can send a message to discord://1238716283761/%23irc and it'll get there
  150. dreamrealbut yeah, it's kinda ugly. Not sure yet what the level of granularity needs to be.
  151. dreamrealthe format is: service, authority (usually empty), id, source
  152. dreamrealso discord: empty authority, guild number, channel
  153. dreamrealI need to figure out how to get guild NAME out of that, I guess
  154. dreamrealall right, I'm off for a bit
  155. bot<discord://1256590312177012806/#irc/VExcess> what are people using to irc chat these days? I used to use HexChat because it came preinstalled on Linux Mint. But now Mint doesn't come with HexChat anymore and there's no alternative.
  156. bot<discord://1256590312177012806/#irc/VExcess> this is super cool. I've never seen a irc mirrored to discord. I've only used irc like a total of 3 times though.
  157. bot<discord://1256590312177012806/#irc/blue> irc is mostly dead
  158. bot<discord://1256590312177012806/#irc/blue> but there are some primate users there who are not here, and vice versa. bridging is nice 🙂