Chat Logs

  1. * skillbot joined #primate
  2. * skillnews joined #primate
  3. * lioloc joined #primate
  4. bluelioloc: hey!
  5. bluehttps://repopack.com/project/primate/tasks/153
  6. nevetRepopack · Sign in
  7. bluecheck out that, will be part of 0.43
  8. bluedreamreal: primate 0.42.1 is out, including updates to @primate/core and @primate/marko. It is a security-hardening and stability release, I recommend updating
  9. dreamrealgah, sorry, underway
  10. bluewell, you don't need to update *now*
  11. blueit's just a general info
  12. dreamrealI'm bad about enduring old versions when I know a fix is out there
  13. dreamreal... another reason to vastly dislike windows
  14. * lioloc joined #primate
  15. blueyou know, there's a tension between having a lockfile, and receiving updates. I strive to try to diffuse this tension in some form with repopack, with trusted publishing (npm is also going in that direction), but the fact of the matter is that lockfile prevent you from receiving updates simply by redeploying a service
  16. bluelockiles*
  17. bluewhich somewhat defeats the purpose of patch updates, as per npm policy
  18. bluenpm is generally very problematic from a security point of view, but their solutions never feel like they've thought them through. they are most reactive, much less proactive
  19. blues/but/and/
  20. dreamrealTrying to update the nextjs repo now, which is always a drag. The dependency audit for nextjs is great fun: "this is a mandatory update but BTW nothing will work if you apply it"
  21. dreamrealgee, I wonder why I agonized over switching to something different for all of 15 ninutes.
  22. bluenextjs is just not worth it
  23. blueI sent you the video by lioloc where he compares them
  24. bluenextjs is very, very heavy
  25. bluelioloc: so cool, your branch can start a desktop app with gtk 4 on linux. but a revision was still requested
  26. liolocwill take a look
  27. bluelioloc: btw https://primate.run/blog/primate-042#production-diagnostics
  28. nevetPrimate — Primate 0.42: Virtual route groups, structured forms and production diagnostics
  29. bluethis was missing from the original blog post
  30. blueit's kinda nice :)
  31. liolocneat
  32. liolocvery cool!
  33. bluewe're gonna use it on repopack.com, that when an error 5xx is generated, we report it automatically
  34. bluewe might show the user an id for reference
  35. liolocwhat a great idea
  36. lioloci'll have to try it myself
  37. blueyup
  38. bluedreamreal: whilst reviewing primate:
  39. blue"Error: cyber_policy: This content was flagged for possible cybersecurity risk. If this seems wrong, try rephrasing your request. If you’re doing authorized security work that requires more cyber permissive safeguards, apply for Daybreak access via https://platform.openai.com/settings/organization/status-and-access before retrying."
  40. bluegreat, now I can't even review my own OSS code
  41. blueidiots
  42. dreamrealblame aggressive demands by the US government, and idiots trying to use AI to break others' code maliciously
  43. dreamrealSorry, man
  44. dreamrealhits me too, and that's actually MY INDUSTRY - I have access to models that do not have those safeguards but I literally have to be in a military base to use them
  45. dreamrealand thus I do not use them
  46. blueand the annoying thing is that they now flagged the entire session. which is OK, I can start a new one and rp is pretty good at bootstrapping, but yeah
  47. dreamrealoh, that reminds me: do you want #primate's logs to be public as well?
  48. blueyes, it's ok
  49. bluethanks for asking
  50. dreamrealI actually need to sanitize the logs some
  51. bluebut I am bound by these network's policies to advertise that, btw
  52. blue(as are you, if you have it on any of your channels, btw; be advised)
  53. bluebest is to put it in the topic, which I will do now
  54. dreamrealhmm, hat might be an interesting feature: "here's the logs, filter for potentially insecure/illegal content and sanitize profanity"
  55. bluedreamreal: https://bytecode.news/logs?provenance=irc%3A%2F%2Flibera%2F%2523primate
  56. nevet#primate, October 7, 2026
  57. blueis this the shortest url I can get?
  58. blueit is rather ugly, I must confess
  59. dreamrealYES, darn it!
  60. blueok
  61. dreamrealit is ugly, yes, because provenances are ugly
  62. dreamrealhmm
  63. bluenicer: bytecode.news/logs/irc/libera/primate
  64. blueyou can map this with a [...].ts route in primate
  65. blueand yes, I know there are # and ## channels, and that is an abomination to map to a url, where # means the hash/anchor
  66. dreamrealyeah, primate's not the only option here, and I'm going to file an issue against all three UIs, and damn it nextjs sucks and I'm considering deprecating it for maintenance
  67. dreamrealthere are actually FIVE UIs, but two of them are BADLY outdated because I don't give a single crap about them and they're not even deployed live
  68. bluethis is *rather* easy to in primate. create a route as thus described above. then: const `[protocol, server, channel] = request.path.toJSON();`
  69. bluesorry, the opening backtick should be been before the const
  70. blueshould have been*
  71. bluedreamreal: https://libera.chat/policies/#public-logging
  72. nevetNetwork policies
  73. bluejust fyi; I will make sure this is properly advertised in the topics of #primate and #repopack; you take care of your flock
  74. bluejust so we're transparent about it, the public logging by nevet for this channel is authorised by me (channel owner) until indicated otherwise
  75. dreamrealI'm working on the issue, have a few other things in the queue
  76. blueno worries
  77. blueI'll change the topic as soon as you're up with the prettified url
  78. blue... or with the non-prettified one if you decide elsewise
  79. dreamrealI'm working on it, issue has been filed and shouldn't be long
  80. blue+1
  81. dreamrealdang it you casually created six issues for streampack :D
  82. blueyes well, you're carrying too many frontends :P
  83. dreamrealOnly two issues are in the front ends, nextjs gets ignored for this one
  84. bluewhat are the other four?
  85. dreamrealbut this is WHY I wanted multiple front ends, to get the backend API solid
  86. dreamrealnextjs [deployed, deprecated], primate [deployed and is the 'main site'], spring [pudl, deployed and is sort of the 'admin site'], spring (basic) [undeployed, unmaintained, was the proof for the design as a balance against...], reference (nextjs) [undeployed, was the 'site' before the nextjs 'main site' was built]
  87. bluebtw dreamreal, I feel like both things can be true at the same time. repopack exposes an API (for `rp`), *and* it has a very fast direct path for the ui. there is an inherent sync problem that arises from this, but the dividends for the direct path, eliminating the costliness of API requests, and enabling a direct db access essentially, is huge
  88. dreamreal*nod*
  89. blueI'm not saying you *need* to go there, it's your decision. but a two-path'd approach can pay out
  90. blueyour design*
  91. blueof course, the fact the backend is written in kotlin makes it very hard for you to port it to primate. hence I was thinking about a @primate/kotlin wasm bridge
  92. dreamrealI'm not sure what you mean: streampack DOES have a direct API. You mean such that UIs have access to the data directly?
  93. blueessentially yes. on repopack.com, the first load is always *one* request; on bytecode.news too, by masked by another fetch request in the background, to the api
  94. bluebut masked*
  95. dreamrealAh, no
  96. dreamrealI totally understand and it WOULD make everything faster
  97. dreamrealNO ARGUMENT THERE at all
  98. bluebut it would break your API design, I get it
  99. dreamrealbut the intent was NEVER actually for me to maintain UIs that didn't directly interest me
  100. blueya
  101. dreamreallike, I can see me being directly invested in the pudl UI, but honestly, I'd far rather SOMEONE ELSE maintain the primate API because it's not my strength area
  102. dreamrealand that means trusting users to not be damn fools
  103. dreamreallike, there ARE secrets in the database: they're encoded and you could capture the database without having secrets exposed, BUT someone could THEORETICALLY spend a lot of computing power on those secrets
  104. bluethe question here is a matter of coupling. you have a very loose coupling at the moment, but it comes at some price. I am thinking if you can keep it decoupled to your heart's content, and still get the benefits of traditional stronger coupling
  105. dreamrealblue: right, but that comes with TRUST. I could do that with pudl, as the interested maintainer. But not with the other UIs.
  106. dreamrealRight now interactions are pretty fast, and having a common API gives me not only viability tests for the API but common reference points
  107. bluehow so? trust that the server implementation isn't compromised, you mean?
  108. dreamrealTo be clear: you're wrong exactly 0%
  109. dreamrealno, trust in the maintainers of the UIs
  110. bluebut *you* are the maintainer
  111. dreamrealright now there is no trust, and there's no need for it: the UIs can't even pretend to have write access because there is no access
  112. dreamrealright
  113. dreamreal... of pudl
  114. dreamrealand technically primate as well
  115. dreamrealbut I really, really want BCN to have enough critical mass to break that pattern
  116. blueanyway, there are other challenges as well. I'm not sure how much kotlin wasm is ahead, and there are also to my knowledge some limitations with wasm java
  117. bluebut I must confess I have been eager to try out java wasm since java 25
  118. dreamrealwait until the next major release comes out
  119. dreamrealthe java LTS releases are quite something, compared to the history
  120. bluebut 25 is LT
  121. blueLTS, no?
  122. bluesupported until 2033
  123. bluethe next lts seems to be 29, sept 2027, that's some ways off
  124. dreamrealyes, but the next LTS is gonna *rock*
  125. dreamrealI'm staying on 25 until the next LTS but they keep adding features the community's been wanting and needing since, like, 2006
  126. bluethere's also the question of whether it makes sense to do a @primate/java or a @primate/kotlin first
  127. * dreamreal has no recommendation there, not enough experience with WASM in the field
  128. blueya
  129. dreamrealblue: backend is being merged for release now
  130. bluedreamreal: nice!
  131. dreamrealand now it's being set for deployment
  132. dreamrealprimate update following, but it needs backend deployment because the API is changing
  133. bluewith the latest primate updates?
  134. blueah ok
  135. dreamrealand yes, it's going to have the latest primate updates
  136. dreamrealalthough I'm not migrating the *code* very much
  137. bluethere's no code changes in 0.42.1 to be done
  138. blueshould be 100% transparent
  139. dreamreal*nod* just being clear, because I'm not using the route groups, etc
  140. blueI know
  141. bluethe route groups have got some stability fixes
  142. bluebut they're still opt-in, and will remain so
  143. * nevet joined #primate
  144. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  145. bluedreamreal: https://repopack.com/project/primate/tasks/153
  146. nevetRepopack · Sign in
  147. dreamreal+1
  148. dreamrealGrrrr, trying to get some tuning issues resolved, HOLD ON. One step at a time. The backend deployment needs to work before we progress.
  149. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  150. * nevet joined #primate
  151. bluethere's an asset chunking bug, though it's not surfaced on bytecode.news
  152. * nevet joined #primate
  153. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  154. * nevet joined #primate
  155. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  156. dreamreal*nod* Sorry for the join spam, the AI model interaction changed :/
  157. dreamrealit's rejecting "thinking" because I'm not turning it off properly yet
  158. * nevet joined #primate
  159. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  160. * nevet joined #primate
  161. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  162. dreamrealgolly, it's WORKING now but still not right
  163. dreamrealgrrrr
  164. * phaleth joined #primate
  165. * nevet joined #primate
  166. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  167. dreamrealOkay, the new AI stuff works, and the openapi endpoints have been cleaned up. Now the primate and pudl updates for the logger entrypoint.
  168. phalethI thought pudl is just a design lang
  169. dreamrealit's an implementation as well, and in THIS context, it's a UI that uses pudl
  170. * skillbot joined #primate
  171. * skillnews joined #primate
  172. dreamrealit's also the most pessimistic consumer of the openapi spec, which is why it's a gate
  173. phalethok, I never understood the openapi spec, all I know is that primate has https://openapi.primate.run/manifest.json
  174. phaleththis UI that uses pudl uses pudl at build time I hope
  175. phalethright?
  176. dreamrealerr... no, no
  177. dreamrealthe bytecode API that uses openapi is talking to api.bytecode.news
  178. phalethoh, there is a SwaggerUI, and I was just like curious if you have SwaggerUI and you really do
  179. dreamrealI do, yes
  180. phalethwell, anyway, openapi is like I read odata and microsoft and I'm like "nah, I've had enough of that"
  181. dreamrealit's a drag, yes, but it's probably the best drag available
  182. phalethI also think that odata is one of the good things that microsoft has done, but still
  183. phalethbunx is used to run proby in the primate monorepo, that means it's still vendor locked in
  184. dreamrealblue: zeroing in, found a gap in pudl's endpoints
  185. dreamrealbackend is stable, so closing the gap and then fixing primate
  186. dreamrealAND THEN https://bytecode.news/logs/irc/libera/primate should work
  187. bluevery very good
  188. bluewe have a @primare/core patch coming up
  189. dreamrealwhen and for which? The migration thing?
  190. blueno, a 0.40 thing
  191. dreamrealanything that would affect BCN's deployment?
  192. blueno
  193. bluejust optimising network request size
  194. bluetrimming fat
  195. dreamrealok
  196. dreamrealblue: https://bytecode.news/logs/irc/libera/primate
  197. nevet#primate, October 7, 2026
  198. blueawesome
  199. dreamrealand thank you for the suggestion
  200. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly monitored at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  201. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  202. phalethdreamreal: the pudl frontend also feels kinda lightweight, which is nice
  203. dreamrealboth it and primate are pretty zippy
  204. phalethyup
  205. dreamrealpudl just uses an application paradigm, which isn't what most users would want or need
  206. dreamrealand then contrast it to nextjs.bytecode.news
  207. dreamrealwhich isn't sluggish but is *by comparison*
  208. phalethyeah, these windows are kinda odd on a website
  209. bluedreamreal: you are welcome
  210. dreamrealphaleth: for *writing* it's fantastic, I use the pudl endpoint for all admin access, AND it gives you a console :D
  211. phalethblue: optimizing network request size?
  212. blueyes, removing the names of chunks from json transfer objects
  213. phalethdreamreal: cool, I like CLIs
  214. phalethblue: nice, every byte counts
  215. dreamrealphaleth: see discord, #offtopic
  216. phalethdiscord? I'll pass
  217. dreamrealscreenshots, tho!
  218. phalethheh
  219. dreamrealI could paste one here but, um
  220. dreamrealsrsly, check it! Just this once!
  221. phalethmaybe later
  222. dreamrealit's the impressive! ... dang it
  223. dreamrealblue: do you see it? Are you not entertained?!?!
  224. bluesee what
  225. dreamrealI guess I could use an image pastebin, but I don't know of any
  226. dreamrealblue: discord, primate, #offtopic
  227. blueah, I saw now, yes
  228. dreamrealWhen I write on the pudl api, NOT ONLY does it have a "suggest tags" and "update tags" feature in the editor, but I can also just crank up a console and type into it just like I would here
  229. dreamrealcalc 42*pi
  230. nevetThe result of 42*pi is: 131.94689145077132
  231. dreamrealopenapi
  232. nevetopenapi is a vendor-neutral, machine-readable spec for HTTP APIs (formerly Swagger): describe the paths and schemas once, generate clients, servers and docs from it. URLs: https://www.openapis.org and https://spec.openapis.org/oas/latest.html
  233. dreamreal(this output is in the screenshot phaleth so CALLOUSLY refuses to see)
  234. dreamrealcalendar hebrew
  235. dreamrealcaloh
  236. dreamrealtoday hebrew
  237. nevetToday is Wednesday, 26 Tishrei, 5787 (Hebrew)
  238. dreamrealtoday
  239. nevetToday is Wednesday, October 7, 2026
  240. dreamrealI'm going to eventually move the factoid suggestion stuff into primate too but it's admin-only, as most of the AI stuff is gated to admins
  241. dreamreal(one aspect of the factoid derivation is heuristic, not AI, but the most useful features leverage AI)
  242. dreamrealI am, BTW, adding a filter for the backend such that it has patterns in URLs to ignore, so I can add "repopack.com/project" and have it not echo those url titles
  243. bluethat's AWESOME
  244. blue(however, there is the intention to make some semblance of public projects on repopack.com; although as phaleth noted, we will be limiting the ability of bots to get the entire js bundle from that, and that's a task for primate to solve)
  245. dreamrealWell, the thing is, the intent is to say "ignore urls that match THIS PATTERN" - not just a string, but a pattern - and also ignore urls that have text like "log in" or "sign in"
  246. blueya
  247. bluephaleth: I've deleted most of my stuff on github, and it'll be moving to repopack soon
  248. bluein particular scld and others I'm going to start creating projects for
  249. blueprimate is going to stay for a while, rcompat will move over completely soon (I already closed most issues). rcompat will be archived and eventually deleted
  250. blueI'm gonna commit fully, I don't see a way forward if I don't
  251. phalethok, it's up to you, let me know when I should get rid of gitea
  252. dreamreal*nod*
  253. bluesoon
  254. phalethalso make sure the UUIDv7s are in the db before anything
  255. bluewe're not going to GA any time close, uuidv7s will be in before that
  256. bluebut they might need to land in primate first
  257. blueI mean, they already are in primate. I'm just not sure the translation in @primate/postgresql is
  258. phalethyeah, makes sense
  259. dreamrealblue: check discord, it is to amuse
  260. dreamrealI'm still giggling
  261. dreamreallike, "holy cow, are you ... what... what's wrong with you"
  262. dreamrealI know giggling isn't manly but... come on!
  263. blueyes
  264. dreamrealand that fool knows the history and visibility
  265. dreamrealand apparently hasn't actually thought "gee, when someone says something they MAY ACTUALLY mean it"
  266. bluetrue
  267. * nevet joined #primate
  268. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  269. dreamrealIt's back! and I'm adding log moderation capabilities to the UIs now
  270. blueAwesome sauce.
  271. blueYou're on FIRE on nevet today, dreamreal!
  272. dreamrealblue: can you join #nevet so I can intentionally abuse you and trigger the reports?
  273. * jreicher joined #primate
  274. dreamrealjreicher: found the problem for openliberty BTW
  275. dreamrealjreicher: https://github.com/OpenLiberty/openliberty.io/issues/4367
  276. nevetAtom feed republishes the ArgoCD drift post with a new id on every site build · Issue #4367 · OpenLiberty/openliberty.io
  277. jreicherAnd there was indeed a problem?
  278. jreicherAhah.
  279. dreamrealjreicher: there was, but it wasn't nevet!
  280. * nevet joined #primate
  281. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc