Chat Logs

  1. dreamrealIt's the same thing.
  2. dreamrealHow do you CANCEL a person? What kind of return from that is possible?
  3. jreicherI think it's a way of disguising an ongoing ad hominem attack as something more acceptable.
  4. blueThe funny things is that Dems have been nearly forever saying "freedom of speech doesn't mean freedom from consequence". That hit them HARD after Charlie Kirk.
  5. bluething*
  6. blue(In fact: freedom of speech actually DOES mean freedom from consequences... that's the point, but Dems are too thick to get it)
  7. dreamrealWell, it's funny what happens when you can't restrain your glee. But no, it doesn't quite mean freedom from consequence: it means you might have the freedom to say something and that something might actually serve as a lever.
  8. dreamrealBut you DO have the freedom to be a jerk... and be seen and treated like a jerk.
  9. blueI think Dems are absolute hyenas for mocking his death, but should they lose their jobs over it? not SPECIFICALLY; I mean, if I were their employer I'd honestly ask them if you feel glee at the death of another person, and if they do, I'd strongly consider terminating them on account of differing values
  10. dreamrealOr an evil person. It's not isolated to the dems, it's just that right now the GOP is ascendant so they're crying a lot more than usual.
  11. dreamrealblue: yeah, well. That's the dildo of consequences! It's hard to lube.
  12. blueThis isn't consequences per se: this is me discovering a side of you that I didn't know exist, and that I don't know if I want to interface with anymore
  13. blueregardless of that, I don't know who's stupid enough to glee over someone's death on SM with his real name
  14. blueI mean, you gotta understand that's gonna come back at you, SOMEHOW, SOMEWHEN
  15. dreamrealWell, plenty of examples desperate to make sure their friends know they're the GOOD ONES for celebrating the RIGHT MURDER
  16. dreamrealmidwits thinking murder's surely abstract, we see enough of it on TV
  17. blueand then you get your typical "this guy was for guns so it's cosmic justice". is THAT how we do things now?
  18. dreamrealwell, it's how they think
  19. dreamrealthat's the corrosiveness, everything's reduced to soundbites because they can't hold two things, especially contrasting things, in their heads at one time. Again, not a democratic problem, just a problem they seem eager to display because stupidity is an easy disability
  20. dreamrealsorry, democrats, I don't lie about what I think easily
  21. dreamrealI'd rather someone recoil in horror at something I say if it's a true representation
  22. dreamrealbecause if it's horrible and I think it, well, show me where I'm wrong
  23. dreamrealplease
  24. dreamrealtikkun olam is important to me, to provide as well as receive
  25. blueand next point is, "I didn't agree with the guy, but he didn't deserve to die"
  26. blueWHY do you need to disclaim THAT?
  27. bluenot wishing people die shouldn't be contingent upon agreement of views, you're creating an evil link
  28. dreamrealWell, not only that. But the funniest thing is that when you ask them what they actually disagreed with, it's someone else's summary of something he didn't quite say
  29. dreamreal"he said two paragraphs, the short version is 'guns yay'" when, uh, no
  30. blueyou making it sound like this: "if I only said I didn't deserve he died, then I agree with his views"
  31. blueah... no?
  32. blueyou're just saying you don't think people should be gunned down
  33. dreamrealHis defense of guns was pretty in-depth and he did in fact say some things that are unpleasant about tradeoffs
  34. bluehe didn't dserve*
  35. dreamrealblue: yeah
  36. dreamrealI mean, I think neither he nor anyone else should be murdered, although there are exceptions to the "I hope they don't die" statement
  37. bluethen point is, such a dislaimer is basically you talking about yourself: you're saying: I don't want to be associated with this guy... but I still don't wanna come across like a jerk. but congrats, you just did
  38. dreamrealI still can't celebrate bin laden's death, or sinwar's, but ... is the world really worse off since they found their way to sheol? uhh... no
  39. dreamrealblue: no doubt
  40. bluewell that's the thing, right
  41. dreamrealaight, good shabbos
  42. dreamrealSorry, it's ... well... shabbos
  43. bluegood shabbos! I need to sleep anyway
  44. blueya no worries
  45. bot[jottinger/bytecode.news] New issue #128: Feature discovery endpoint for UI clients - https://github.com/jottinger/bytecode.news/issues/128
  46. bot[jottinger/bytecode.news] New issue #127: Make OIDC optional via Spring profile - https://github.com/jottinger/bytecode.news/issues/127
  47. bot[jottinger/bytecode.news] New PR #129: Updating to make OIDC configuration a runtime profile - https://github.com/jottinger/bytecode.news/pull/129
  48. bot[jottinger/bytecode.news] New PR #133: Bump hono from 4.11.9 to 4.12.3 in /frontend - https://github.com/jottinger/bytecode.news/pull/133
  49. bot[jottinger/bytecode.news] New PR #132: Bump qs from 6.14.1 to 6.15.0 in /frontend - https://github.com/jottinger/bytecode.news/pull/132
  50. bot[jottinger/bytecode.news] New PR #131: Bump minimatch in /frontend - https://github.com/jottinger/bytecode.news/pull/131
  51. bot[jottinger/bytecode.news] New PR #130: Updating for prep for opening repo - https://github.com/jottinger/bytecode.news/pull/130
  52. * dreamreal!~dreamreal@about/java/dreamreal changed the topic to: This is the channel for the development of the software that runs nevt: https://github.com/jottinger/bytecode.news
  53. * dreamreal!~dreamreal@about/java/dreamreal changed the topic to: This is the channel for the development of the software that runs nevet: https://github.com/jottinger/bytecode.news
  54. bot[jottinger/bytecode.news] New issue #134: IRC adapter: auto-deop when opped - https://github.com/jottinger/bytecode.news/issues/134
  55. bluedreamreal: https://nevet.repopack.app/
  56. bluenow I gotta wire it up, let's see how well that works
  57. dreamrealwoot!
  58. dreamrealI'm going to work on a feature to expose whether OIDC is configured or not in a few minutes, fixing an IRC problem
  59. bluenice
  60. dreamreal(Working on 134 now, 128 is next)
  61. * nevet joined #nevet
  62. * dreamreal!~dreamreal@about/java/dreamreal changed the topic to: This is the channel for the development of the software that runs nevet: https://github.com/jottinger/bytecode.news
  63. bot[jottinger/bytecode.news] New PR #135: Adding autodeop feature for IRC services - https://github.com/jottinger/bytecode.news/pull/135
  64. dreamrealNOICE.
  65. bluedreamreal: this is exciting; I get redeployment times for the primate app of <10s. I still need to optimise the nevet Containerfile, but I think I can get it to redeploy quite fast, hopefully
  66. bluedreamreal: can we add a GET /version endpoint that is not auth'd?
  67. bluethat would be the fastest way for frontends to test connectivity
  68. dreamrealis there one that IS authed now?
  69. dreamreal(the answer is, of course, yes, but I need to understand scope)
  70. blueno. I don't think there's one at all
  71. dreamrealfile an issue - actually, the feature endpoint (for 128) might serve.
  72. bluethere's a /feature endpoint?
  73. blueoh, it's an open item
  74. dreamrealNot for the next ten minutes, at least!
  75. dreamrealI mean, I'm working on it AS WE TYPE right now
  76. dreamrealwill expose what services and operations are in the runtime, as well as OTP, OIDC settings (like "are they there," not "how are they configured")
  77. blueI don't really care about WHAT it does for NOW, only that I can access it unfettered
  78. blueand also, I need to figure out how to redeploy nevet itself
  79. bluethat being said, phaleth did an excellent job on this one, as always
  80. dreamrealI'm working on it, and not being gated is *definitely* a hard nonnegotiable requirement
  81. bluewdym with gated?
  82. dreamreal"no security requirements for /feature"
  83. dreamrealor /features i guess
  84. dreamreali.e., what you asked for!
  85. blueI asked for a simple GET route that I don't need anything for
  86. dreamrealyep
  87. dreamrealexactly
  88. dreamreal100%
  89. blueand that is a problem.. because?
  90. dreamrealit's not a problem
  91. blueoh, ok
  92. dreamrealIt's a hard requirement
  93. dreamrealas in, the feature does not work if that isn't met
  94. bluemy point was only, that this GET route would satisfy:
  95. blueAuth: None
  96. blueyou already have Auth: None routes. just no GET
  97. bluebut I think we're talking about the same thing, anyway
  98. bluelike 90% we're too smart for each other, this is a real problem
  99. blueanyway, back to how to redeploy nevet fast
  100. dreamrealI'm almost done with this
  101. dreamrealand this will be GET /features
  102. dreamrealIt's very useful because things like this expose some inconsistencies in the adapter implementations
  103. dreamrealmost of them are really minor: things that can be corrected with a few lines of code
  104. dreamrealand nearly all because of the rolling nature of the design
  105. dreamrealservice-blog is naturally the worst offender :D
  106. dreamrealrunning full tests now
  107. dreamrealrunning full tests now: curl http://localhost:8080/features yields:
  108. dreamreal`{"version":{"name":"nevet","version":"1.0","commit":"3fb508b","branch":"feature/128-feature-discovery-endpoint","buildTime":"2026-02-28T17:08:12Z"},"authentication":{"otp":true,"oidc":null},"operationGroups":["21-matches","ask","cal","calc","dictionary","factoid","github","hangman","hangman-admin","karma","poetry","rss","safecracker","sentiment","specs","tell","urltitle","version","weather"],"adapt
  109. dreamrealers":["console","discord","http","irc","mailto","slack"],"ai":true}`
  110. dreamrealthat actually does reflect the state of the instance that was run against
  111. * nevet joined #nevet
  112. * dreamreal!~dreamreal@about/java/dreamreal changed the topic to: This is the channel for the development of the software that runs nevet: https://github.com/jottinger/bytecode.news
  113. dreamrealversion
  114. nevetnevet 1.0 | 90f413a (main) | Built 2026-02-28 12:15:36 EST
  115. bot[jottinger/bytecode.news] New PR #136: Adding /features endpoint - https://github.com/jottinger/bytecode.news/pull/136
  116. blueMerge pull request #136 from jottinger/feature/128-feature-discovery-endpoint
  117. bluedreamreal: seems like I'm at the tip
  118. bluenow it's showtime
  119. blueoh lord
  120. blue => [builder 4/4] RUN --mount=type=cache,target=/root/.m2 ./mvnw clean package -DskipTests 63.3s
  121. bluestill going, let's hope that's cached next time
  122. blueok, 137.8s
  123. bluedefinitely room for improvement there, but for an initial build acceptable
  124. bluenow doing a rebuild
  125. dreamreal-DskipTests=true
  126. blueok, all cached, rebuilt in 4.3s
  127. bluenow let's try to redeploy
  128. blueFeb 28 18:34:17 nevet-be java[55]: 18:34:17.084 [main ] INFO com.enigmastation.streampack.NevetApplication - Started: nevet 1.0 | cc4bfa1 (master) | Built 2026-02-28 18:
  129. blue30:36 CET
  130. blueGOOD.
  131. bluenow let's try to wire the features -- just return whatever they return
  132. bluedreamreal: I present: https://nevet.repopack.app/features
  133. blue"commit":"cc4bfa1"
  134. dreamrealnoice!
  135. bluenot entirely sure which commit that is supposed to represent
  136. dreamrealversion
  137. nevetnevet 1.0 | 90f413a (main) | Built 2026-02-28 12:15:36 EST
  138. bluenote that I'm purely rebasing against your branch
  139. blueI'm not rewriting your history, so I think I should be seeing 90f413a as well...
  140. bluemaybe I messed up something
  141. blueare you sure the features endpoitn shows correct data?
  142. dreamrealif you're on a differen repo, though
  143. bluemy repo's history is the same as yours, just with a few commits on top
  144. bluehow are you getting the commit info?
  145. dreamrealif you have commits, that'd be it
  146. bluemy last commit is 5cef64e67be89cda0ebf16b270f35549176e5a6c though...
  147. bluemaybe it's some commit inbetween
  148. blueI'll rebuild nevet
  149. bluehm, now it's running the maven phase again, damn
  150. blueI did change it to -DskipTests=true
  151. bluenot sure how to cache it
  152. blueok, now it's 5cef64e, yippie
  153. bluethe maven build took 100s
  154. dreamrealwell, the *actual* way you should do it is run mvn outside of the container and just copy app.jar in
  155. dreamrealbut nooooo everyone's like "docker is the best, why not use docker to build, it'll be great"
  156. dreamrealbut yes, there're lots of modules to go through, it's a pain
  157. dreamrealand if I ever do native builds it'll be WORSE
  158. bluethat way is never gonna be properly deployable
  159. blueI'm gonna try -T 1C
  160. bluein-container build should be just as fast with nspawn
  161. * dreamreal nods
  162. bluedreamreal: -T 1C got it down to 66s
  163. blueI'm gonna build again, just to see if that's anywhere reliable or just a fluke
  164. blueI mean, the first build was 130s. the one with the m4 cache (no redownloading of mvn packages) was 100s. now we're at 66s. we're getting *somewhere*
  165. bluehm, this was fast, 4s. so probably everything cached
  166. blueI'll try pushing out a git commit
  167. blueyeah, a single commit, even if it's inside apps/primate, totally busts the mvn cache
  168. bluewhat a dumpster fire
  169. dreamrealWell, don't copy in the user stuff then!
  170. bluewhat user stuff?
  171. dreamrealcopy the pom.xml, app, service*, operation*, lib*
  172. blueI just do `COPY repo/. ./`
  173. blueai said it's a multimodule maven build and that I should copy everything
  174. blueand since I have no idea how this works, I listened to it
  175. bluewhat's it matter what I copy, anyway? shouldn't the builder just build what's necessary?
  176. dreamrealBecause of the way docker layers work
  177. dreamrealwhen you change a layer, the cache is invalidated
  178. dreamrealthe AI is right WRT maven, wrong because you're changing bits of it
  179. dreamrealso you copy in WHAT THE BUILD NEEDS and nothing more
  180. dreamrealthe maven parts are ./pom.xml, app, lib*, service*, operation*, I think
  181. dreamrealI've tried to follow a rough convention for them all
  182. blueheck, I'm not changing ANYTHING
  183. blueI pushed to apps/primate, which is no java code, at all
  184. blueand it still busted the cache
  185. dreamrealright, if you change the filesystem in the docker image, that's the cache broken
  186. dreamrealso you copy in WHAT THE CACHE NEEDS, nothing else
  187. dreamrealit is known
  188. bluesomehow the cache isn't broken for npm...
  189. dreamrealdunno what to tell you, man
  190. blueI think it's a maven issue, not a docker issue
  191. dreamrealthis is pretty standard for the OCI stuff
  192. bluethis is somewhat beyond me, but luckily, I don't need to redeploy nevet itself SO often
  193. dreamrealI'll have a change for you soon! factoid updates.
  194. bluedreamreal: https://nevet.repopack.app/otp/request
  195. nevetPrimate app
  196. blueunfortunately... mails don't get sent
  197. bluewhich is ANOTHER fire I need putting out
  198. dreamrealmail configuration is a drag, yes
  199. blueRP has an email service
  200. bluewhich I guess, I will use, I just need to figure out the credentials
  201. blueok, need host & port
  202. * blue goes on a search
  203. bluepretty sure phaleth had that configured for gitea...
  204. blueapp.ini
  205. blueew ew ew
  206. blueapp.ini--
  207. nevetapp.ini now has karma of -1.
  208. blueapp.ini--
  209. nevetapp.ini now has karma of -2.
  210. blueapp.ini--
  211. nevetapp.ini now has karma of -3.
  212. blueapp.ini--
  213. nevetapp.ini now has karma of -4.
  214. bot[jottinger/bytecode.news] New PR #137: Adding factoid audit tracking - https://github.com/jottinger/bytecode.news/pull/137
  215. bluehmpf
  216. blueI can't see any MAIL daemon being configured
  217. * nevet joined #nevet
  218. * dreamreal!~dreamreal@about/java/dreamreal changed the topic to: This is the channel for the development of the software that runs nevet: https://github.com/jottinger/bytecode.news
  219. dreamrealidea
  220. nevetIDEA is one of the "big two" Java IDEs, and probably the most popular of them. Has a free and commercial edition, and has capability to work for many, many, MANY languages. URL: https://jetbrains.com/idea Tag: ide
  221. dreamrealidea.stats
  222. nevetidea has been accessed 1 time, last accessed at 2026-02-28T18:18:11.940047Z.
  223. dreamrealidea
  224. nevetIDEA is one of the "big two" Java IDEs, and probably the most popular of them. Has a free and commercial edition, and has capability to work for many, many, MANY languages. URL: https://jetbrains.com/idea Tag: ide
  225. dreamrealidea.stats
  226. nevetidea has been accessed 2 times, last accessed at 2026-02-28T18:18:27.636040Z.
  227. dreamrealNoice.
  228. dreamrealOkay, that's it for today for me. Have a good one.
  229. blueI FOUND IT!
  230. bluehave a good one
  231. bot[jottinger/bytecode.news] New issue #138: Documentation lookup operation (!javadoc, !jsdoc, !pydoc) - https://github.com/jottinger/bytecode.news/issues/138
  232. bluedreamreal: will never respect SMPT_PASSWORD?
  233. bluenevet*
  234. blueas well as SMTP_SECURITY=force_tls
  235. blueI have all the credentials
  236. blueI just don't know if it's gonna respect them
  237. bluebbiab
  238. dreamrealblue: https://www.baeldung.com/spring-email
  239. dreamrealWe may need to expose more properties to the config
  240. bluewell tell me when you do because this blocks me a bit, I don't have a simple smtp mail
  241. blueI have a few improvements for primate that messing around with nevet has exposed, so I have enough to do for now
  242. bluebut I have this set-up for quick iteration now, so I can report back any blockers to you
  243. blueonce I got the primate app in a not-sorry state, I'll send you a PR
  244. bluelayla tov