ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. bluedreamreal: CVE?
  2. bluelike, security stuff?
  3. jreicherWell, almost certainly not the gateway to E-space
  4. bluelol
  5. dreamrealcve spring
  6. nevetCouldn't look that up right now: Maven Central didn't answer.
  7. dreamrealpfft
  8. dreamrealcve log4j-core
  9. nevetCouldn't look that up right now: Maven Central didn't answer.
  10. dreamrealgrrr
  11. dreamrealcve npm:lodash
  12. nevetnpm:lodash: 8 known to OSV, worst CVE-2019-10744 (critical), newest CVE-2025-13465 (medium); OSV lists 4.18.0 as fixing all. https://osv.dev/list?ecosystem=npm&q=lodash
  13. bluedreamreal: release primitives are coming to repopack
  14. blueI believe most of the things that you might need for nevet might become unlocked soon
  15. dreamrealnoice!
  16. dreamrealI'm also adding alternative media to posts (can you say "podcast?" I bet you can if you try hard enough) and jreicher I think i'm going with the filesystem for it and not postgres
  17. blueyes?
  18. dreamreal:D
  19. dreamrealThe feature's deployed but found a hole based on what I want the landing page to have
  20. dreamrealso another backend change, not a severe one, but even so
  21. bluedreamreal: for rp you probably need rp agent to wokr with the claude background server ,correct? you don't use opencode, right?
  22. blueclaude code*
  23. dreamrealI do use claude
  24. bluegood
  25. blueheard
  26. bluedreamreal: this is HUGE https://repopack.com/project/flog/code/blob/docs/release-sets.md?ref=task%2F31-enforce-coherent-workspace-publication-release
  27. bluethis has been an absolute pain with every js package manager I've worked with
  28. dreamrealGOOD, that's dogfooding
  29. dreamrealOkay, pudl support for podcasts is underway. (pudl is the testbed, since it's the main admin mechanism; after it works, primate gets updated and nextjs can kick rocks.)
  30. dreamrealI wouldn't mind someone really good at nextjs taking a crack at updating it to be good, but that's not the guy in MY chair
  31. dreamrealhe lacks investment and knowledge and loyalty in nextjs
  32. bluedo you really need nextjs?
  33. dreamrealno
  34. dreamrealbut the point behind streampack is that it *does not have a UI*
  35. dreamrealand one of the original overriding design goals is that it supports pluggable UIs, and thus, nextjs is one of them
  36. dreamrealthere's no reason to drop it altogether, but there's also no reason to focus on maintaining it
  37. blueI always admire the extent to which you stretch the term ui
  38. dreamreal"what the users are expected to deal with" = ui
  39. * dreamreal shrugs
  40. blueyes. but that's react, or marko, or svelte
  41. bluenextjs, like primate, is a fullstack framework
  42. bluecalling nextjs a ui is a bit like calling spring a ui, is my point
  43. dreamrealwell, nextjs is the thing it was built on, so... the pudl UI would technically be *another* spring UI the way you're framing it
  44. dreamrealso I guess the nextjs thing is actually react
  45. bluewhat you *probably* mean is *client*
  46. dreamrealyeah, fair
  47. bluenextjs (or primate) are indeed clients here, even if they bring servers of their own, here
  48. dreamrealI just don't really care about it much, because UI is not my arena, I think it's funny and fascinating that the *clients* work as well as they do, given that I had my fingers on them
  49. blueyeah I get it, but everytime you call nextjs a ui, I shudder a bit. consider that the same if I called spring a ui :P
  50. blue(the comparison isn't 100% correct: nextjs ALWAYS has user-facing code, because it bundles react; primate, however, doesn't)
  51. dreamrealI thought about doing a masthead for columbus day since it's a federal holiday here in the States but I don't admire columbus much past his one significant achievement, so couldn't really do it well, plus I lack confidence that I could do the three ships justice
  52. dreamrealshuddering is GOOD for you, dude. Keeps you warm.
  53. * dreamreal giggles
  54. bluemein gott
  55. dreamrealhttps://bytecode.news/posts/2026/10/i-paid-people-to-try-and-follow-my-readme
  56. bluedreamreal: bleh, "no humour", you'd need to recall every copy of Beginning Sprint 6
  57. blueSpring*
  58. bluethe best parts of that book are the humour
  59. dreamrealRight, but it wasn't written with STE
  60. bluemaybe STE sucks
  61. dreamrealand yes, see said footnote
  62. blue, then
  63. dreamrealno, STE is AWESOME
  64. dreamrealit depends on what you're trying to do and with whom
  65. dreamrealat $work, I use STE maniacally
  66. dreamrealmostly because my team lead is relatively junior AND is adversarial
  67. dreamrealSTE shuts him up like a shithouse door
  68. bluemhm
  69. dreamreal"I don't understand what this does *whine*" well, STE doesn't give you much effin' room to wonder (I design methods the same way)
  70. blueno humour, no life
  71. dreamrealI did not hire him, and would not have hired him, he would have failed my interview process in multiple ways
  72. blueSTE be damned
  73. dreamrealyes, well, our audience doesn't appreciate humor much either :D
  74. bluewait, what
  75. dreamrealwe have demanding clients
  76. blueyour team lead wouldn't pass an interview with you?
  77. dreamrealno
  78. blueoof, my condolences
  79. * dreamreal shrugs. He has a lot of history with the product and he has a TON of institutional knowledge that he wears like a straitjacket
  80. blueoh gott
  81. dreamrealand he's very precious about that knowledge, so if you change things to work better or whatever, he's like "but you're changing it!"
  82. blueyou are to be grievously to be pitied
  83. dreamreal... yes, that is what changes are
  84. dreamrealhe'll basically complain about ANYTHING that is A) not his B) alters what he knows C) can be imagined to have problems
  85. bluethere is a term in german, Herrschaftswissen
  86. bluedo you know it?
  87. dreamrealand he's not esp observant
  88. dreamrealI do not
  89. blueherrschaft is authority, or command, or mastery
  90. blueyou seem to be describing exactly that trait in that man
  91. blueif you treat knowledge as a power tool, that's bad, especially if you're a team with ohters
  92. dreamrealyeah, he is desperately seeking control over the project, and he's "the architect"
  93. dreamrealthere's another tech architect on the team (the original author) who'll happily just ram changes through
  94. blueheh
  95. dreamrealso the team lead no longer consults with me, because I'll see holes in his designs almost immediately; the other tech architect and I work well together (and he's the one who hired ME)
  96. dreamrealhe and I will argue ferociously sometimes, and he'll even win on occasion, which is fine
  97. dreamrealbut he doesn't win by fiat
  98. blueoh wow, what a dumpster fire, I'm terribly sorry
  99. * dreamreal points to the client base, which is a lot of the problem :D
  100. dreamreallots of military/ex-military
  101. bluejocks
  102. dreamrealin a lot of ways, they're nerds who act like jocks :D
  103. blueyou're describing a joke-nerd chasm
  104. bluejock*
  105. dreamrealbut I win a lot because I have, err, what do you call it, the... oh yeah, DATA
  106. bluebeen known since the 90s
  107. dreamreal"use this, it works" "show me how, given this data that you should have had on your own but didn't but NOW you do"
  108. dreamrealI've told you about the 6:30 gap, yeah?
  109. blueno?
  110. dreamrealoh. We have a few reporting mechanisms: our base report format is in XML. The codebase had two main ones: a W3C DOM-based XML report, and a streaming XML report that, well, streamed nodes out, yeah?
  111. dreamrealSo the DOM report chewed through RAM like nobody's business: we have *thousands* of nodes, it's quite large, so the recommendation was to use the streaming report instead... but here's the thing: the W3C DOM report could do a 250k node report in 20s. The streaming report, SAME INPUT, would have 6:50.
  112. dreamrealNote: the issue that got us to LOOK AT THE REPORTS was... a timeout.
  113. blueoof
  114. bluecrazy
  115. dreamrealI built a THIRD report that took around 25s, but had much better memory characteristics than the W3C dom version... but that 6:50 made me MAD
  116. dreamrealso I took a look at it and fixed it: now it's 23s, same input, verified via tests
  117. dreamrealthrew away my third report as it wasn't necessary, but NOW we have data and the test suite doesn't allow stupid shit through like the team lead apparently allowed for YEARS
  118. bluewow
  119. blueyes
  120. dreamrealand his COMPLAINT: "but tests are slow"
  121. bluebecause 25 > 20s?
  122. blueor well, 23s now
  123. bluehe's complaining about 3 seconds?
  124. dreamrealsorry, "but THE tests are slow" and I laughed and said "yeah, you're right, it's much smarter to have the user accept crap than actually validate that what we do works well."
  125. dreamrealHe was basing his judgment on how he didn't know how to write fast tests
  126. dreamrealthe product was not BUILT to test, so his idea of testing was whole-suite
  127. bluemhm
  128. dreamreallike, our text scanner: it had 12 tests that ran in 8s
  129. blueWHAT
  130. dreamrealHe saw that it had 120 tests after I was done working with it, and said "but that's going to take forever"
  131. bluewhy so long?
  132. dreamrealOCR, mostly
  133. blueoh gott
  134. dreamrealbut guess how long those 120 tests take to run :D
  135. blueOCR, the final boss
  136. blue8/12*120, obviously
  137. blue:P
  138. dreamrealthey take 4 seconds now
  139. blueoof
  140. dreamrealincluding the OCR coverage
  141. bluehow that?
  142. dreamrealI don't test THE WHOLE SYSTEM, I test what I need to test, and I don't run OCR on EVERY FREAKING INPUT
  143. dreamrealI run OCR on image input only
  144. bluemakes sense
  145. dreamreallike, "what am I testing? Hey, here's an idea, why don't I test that"
  146. dreamrealand not all 800 other bits of every other system
  147. dreamrealesp when cranking up the system itself takes about 20s
  148. blueyes
  149. dreamreal... which is how they normally test the app! "I'm working on a module, let me start the whole app and run input through"
  150. dreamrealand they'd eyeball the output
  151. dreamreal... meanwhile I've started the app maybe five times over the last six months
  152. dreamrealand guess who has a better delivery record
  153. dreamrealI get issues filed against the deployments but they're not "it doesn't work" but "oh, the requirements are different thanks to observing the output"
  154. dreamrealand they are unaware that as soon as a better offer that feels convincing comes in I'm *done*
  155. dreamrealI do NOT enjoy having to write STE to work around my idiot team lead: I think it's a useful approach, period, but I don't have a choice because he's a damn fool
  156. blueyou need to work with better people
  157. dreamreali work with some good ones and some ... lesser-skilled ones
  158. dreamrealmost of my team is worthwhile
  159. bluedeuteronomy 25:4, just sayin
  160. dreamrealyeah, well
  161. dreamrealmilitary so proverbs 27:2 gets violated a lot too
  162. blueha
  163. dreamreali don't tell them "look at this cool thing I did," I just show the test results and measurements :D
  164. dreamrealI'd probably be better off if I did the whole "look at me!" dance but ew
  165. bluedreamreal: btw; my personal interpretation of deut 25:4 is somewhat different from the traditional one; my read has always been "don't be the means of undercutting someone's passion"
  166. dreamrealI don't think that's nontraditional
  167. dreamrealtorah is infinitely deep
  168. bluewell, the traditional take is like, pay people properly, kinda like a social justice direction
  169. bluebut I do not read it like that at all
  170. dreamrealI think both versions are acceptable
  171. blueya
  172. dreamrealpeopel SHOULD be paid properly... but also enabled
  173. dreamreal"I wish my field plowed, but I'd like to prevent the ox from plowing." Uh, what?
  174. blueha
  175. blueI think the interpretation is, if your px is ploughing the field, and there's food lying around by that, don't hinder it from eating it
  176. blueor well, the 'literal' read
  177. dreamrealRight, but that's what *encourages the ox*
  178. bluethe one that lead to the traditional interpretation
  179. blueright
  180. dreamrealmost of my "team advice" is built around building strong teams where people enjoy working with each other, even if the work itself isn't all that entrancing
  181. dreamreallike, I think people enjoy when I'm in a meeting and interacting, because I'm intentional about it
  182. dreamrealThey may think it gets silly sometimes, and it IS silly sometimes, but there's a point behind it and a limit
  183. blueyes, makes sense
  184. dreamrealjokes are self-deprecating and *short*
  185. bluesome people are utterly sensitive about jokes
  186. blueit's terrible
  187. blueand exhausting
  188. dreamrealYeah, it is
  189. bluedreamreal: https://flog.run/docs/release-sets
  190. dreamrealnice!
  191. dreamrealOMG this is fascinating https://www.sciencealert.com/secret-of-orange-cats-finally-revealed-after-60-year-search
  192. blueLOL
  193. * dreamreal has a tortoiseshell and a calico cat is the one that nearly killed me
  194. blueclanker did a super good job footerwise here
  195. blue"MIT licensed · built with flog · served by Primate"
  196. dreamreallove the tortie, she's the one who types so badly, and loved the calico as well
  197. blueself-awareness :P
  198. bluelol
  199. bluedreamreal: repopack now forces compaction on >32k bytes of text, in a task
  200. bluethe repopack team has chosen a somewhat different direction on handling conversations, which you may consider interesting: messages can never be *edited* (think irc), you're supposed to post follow-up notes. the natural companion to that is compaction, which is warned at 20k and enforced at 32k bytes (unless you issue --force, for an escape hatch)
  201. bluethis avoids the typical github drift of a very long conversation where you're going, "but what has been decided here?"
  202. blueand it also avoids those terrible forks where people edit messages after the fact, and after people have *already replied to their original versions*
  203. bluethere are exceptions to this, in the form of redactions; but users are very limited in the number of redactions they can use (so as to not destroy conversations), and redactions are all-or-nothing; they remove the entire message
  204. bluethis is to cover the case of personal information etc.
  205. dreamreal*nod*
  206. bluethoughts?
  207. dreamrealI mean, it makes sense to me
  208. bluegood
  209. bluedreamreal: we've hit a significant milestone with repopack, it's now possible to deploy arbitrary *task* branches
  210. bluehttps://pewtxngij-task-213.repopack.app/blog/primate-043
  211. nevetPrimate — Primate 0.43: diamond migrations, deferred navigation and direct SQL
  212. bluethis feature is currently limited to apps that do not need envs/secrets/fixtures, but that will be added as well
  213. bluejust imagine how cool it would be to deploy an arbitary task of nevet :P
  214. bluein that, we've kinda of surpassed what always destroyed me with fly
  215. blues/destroyed/annoyed/
  216. bluethe way it's done is that you define a deployment blueprint: what containerfile to use, what context, what envs etc. and then you set it as a default
  217. bluefrom there, you can do `rp task preview <number>`
  218. blueor if you want to use an alternate blue print, `rp task preview <number> --blueprint <blueprint>`
  219. blueyou can deploy any tasks in ACTIVE, PREVIEW, or even if they're already merged
  220. bluein REVIEW*
  221. bluewhich is nice because then you can go back to "how was this before"
  222. bluephaleth: yo!
  223. bluephaleth: https://pewtxngij-task-213.repopack.app/
  224. nevetPrimate — The Universal Web Framework
  225. blueyou can now deploy any task branch in primate :)
  226. phalethhi blue
  227. phalethcan you also undeploy?
  228. blueyes
  229. blueeither via ui, "stop", or `rp task preview <number> --stop`
  230. bluetask apps' leases expire after 24h
  231. blueand you'd need a new `rp task preview <number>` to recreate them
  232. bluethere's also a security concept in the pipeline, currently all previews are public
  233. bluephaleth: https://repopack.com/project/repopack/tasks/616
  234. blueunder #616, all preview apps will be private by default, public will be the exception. rp and ui get a preauth token (not basic auth)
  235. bluethere will be a --public flag for `rp task preview` with a guarded action and higher permissions than `task.preview`
  236. phalethI think pewtxngij is good enough password
  237. phalethgiven the fact that repopack.app is asterisk domain there is no way to discover those
  238. blueI don't do security by obscurity, you know. besides, you're misreading this. this is a stable short_id (p + ewtxngij), which we're not attempting to hide
  239. bluethe short_id is an identity, not an auth measure
  240. blueit should be assumed known/leaked from the get-go
  241. phalethdo you know what is @rcompat/runtime? https://upaste.de/raw/BD8
  242. blueI mean, we're not showing it anywhere, but it's very likely rp communicates it
  243. blueyes
  244. bluehttps://repopack.com/project/rcompat/code/tree/packages/runtime
  245. blueit's a way to detect what runtime you're using
  246. phalethbut rp communicates that only to the project maintainers?
  247. blueI'm not sure. But I'm not trying to hide the short_id explicitly
  248. phalethok, any clue why flog would not install that package?
  249. blue^ without doing crazy things like `typeof Bun !== "undefined"
  250. bluehm
  251. phalethflog install --ignore-scripts --no-lockfile
  252. blueI assume because it's imported from `/app/primate/packages/primate/lib/bin.js`
  253. phalethinstalled 561 packages and 0 workspace links (431 cache hits, 130 downloads)
  254. blueand possibly not specified in primate?
  255. bluehttps://repopack.com/project/primate/code/blob/packages/primate/package.json
  256. blueweird, it is specified there
  257. bluehold on
  258. blueah wait
  259. blueyou said you're using an old version of primate to test flog, correct?
  260. bluecoudl you verify it has @rcompat/runtime in its deps?
  261. blueif not, then flog is correct there
  262. phalethyeah, I'm trying to get to github but the website is having seizures
  263. blueugh github
  264. phalethwould be nice if repopack just had access tokens at least with read scope and allow download of tar.gz
  265. bluefor downloading flog?
  266. phalethit's there https://github.com/primate-run/primate/blob/master/packages/primate/package.json#L36
  267. phalethfor downloading the source code
  268. bluedunno, gh isn't loading for me, it's showing me some weird rainbow unicorn
  269. phalethyeah
  270. bluesomething something having a bad day
  271. phalethtry again
  272. bluestill down
  273. phalethgotta close the browser and reopen
  274. blueso you need a .tar.gz of the source code?
  275. bluenope, still not working
  276. phalethyeah, already wrote a task for that
  277. blueso you're running `flog x primate build --target=node`?
  278. blue→ ./flog install
  279. blueflog: error: peer dependency missing: @angular/common@22.2.2 requires rxjs@^6.5.3 || ^7.4.0
  280. blueI can't even install things, flog is very strict
  281. phalethtried to run it from the website dir https://upaste.de/raw/kUV
  282. bluedid flog install work?
  283. phalethyeah, I posted above it installed 561 packages
  284. phalethand 0 workspace links
  285. phalethnot sure what 0 workspace links means
  286. blueweird. but I guess you're using an old version
  287. phalethno
  288. bluewhere do you run flog install from?
  289. phalethhttps://upaste.de/raw/WJ7
  290. blueok hold on
  291. blueclanker on it
  292. bluegonna get declankered soon, 2%
  293. blueclanker is fixing
  294. phalethare you gonna revert https://repopack.com/project/primate/tasks/178?
  295. phalethcause flog will not know nub.lock
  296. blueyes. https://repopack.com/project/primate/tasks/209?tasks=status%3Dopen
  297. blueno more nub/pnpm nonsense
  298. phalethI don't see the app hosted at https://pewtxngij-task-213.repopack.app/
  299. nevetPrimate — The Universal Web Framework
  300. bluehow come? even nevet sees it
  301. bluedo you have a firewall or smth that caught `pewtxngij` as a false positive?
  302. blueit does look liek some of those weird chinese scammer urls
  303. bluethat's why I wanted vanity urls, like p-primate-task-213.repoopack.app
  304. phalethI mean in repopack, the app as in the primate project
  305. blueok
  306. blueclick on apps, switch to task apps
  307. blueI know, the ui looks bad
  308. bluewill be dealt with when I have more time
  309. blueyou can also just go to the task, you have controls on the right
  310. phalethcan't see task apps anywhere
  311. bluehttps://repopack.com/project/primate/apps/task-213
  312. phalethTask preview permission required
  313. phaleththat's all the page says
  314. bluedone
  315. bluewhat page said that, btw?
  316. phalethah, ok
  317. phaleththe link you provided said that
  318. bluethe task link?
  319. phalethbut now it works, there is Task Apps and Ordinary Apps switch
  320. bluewait wait
  321. bluethe error was on the task page
  322. blueor on the apps page?
  323. phalethon this page https://repopack.com/project/primate/apps/task-213 I saw Task preview permission required
  324. blueit blocked the entire page?
  325. phalethyeah
  326. phalethcan't see any app delete button
  327. phalethor stop via UI
  328. blue`rp task 213 preview --stop`
  329. blue`rp task preview 213 --stop`*
  330. blueworks?
  331. bluehttps://repopack.com/project/primate/tasks/213
  332. blueyou don't see a stop button here?
  333. phalethoh, on the task page, I was looking for it on the app page
  334. blueI'm fixing this, it's a bit confusing to have both
  335. phalethyeah, just link to app page and have all controls there
  336. bluewell it's nice to at least have the preview button on the task page, but yeah
  337. phalethpreview link does not hurt on task page
  338. blueya
  339. phalethclanker finished the flog x fix, looks pretty straightforward
  340. blueya
  341. bluephaleth: flog#33 is approved
  342. bluerebuild ongoing
  343. blueyou'll probably see some peer providers you need to fix; that's a primate gap
  344. blueflog is much more strict on peers than other package managers, which silently install them
  345. blueit's a feature, not a bug
  346. blueclanker: "So after #33, flog is working as designed. The remaining Containerfile failures require Primate manifest changes, not flog changes. So far these include rxjs, @types/react-dom, @babel/core, and @internationalized/date in their respective consumers."
  347. blueso we probably need a primate task here, phaleth
  348. phalethneed the tar.gz download then
  349. bluewith token, yes?
  350. blueI'm not yet comfortable with making this public
  351. phalethyeah, with token
  352. bluewhat is the security concept around this token
  353. phalethok, now already fails on install
  354. phaleth[1/2] STEP 9/12: RUN flog install --ignore-scripts --no-lockfile
  355. phalethflog: error: peer dependency missing for importer apps/angular (@app/angular): @angular/common@22.2.2 requires rxjs@^6.5.3 || ^7.4.0
  356. phalethError: building at STEP "RUN flog install --ignore-scripts --no-lockfile": while running runtime: exit status 1
  357. blueyes, you need to add those deps
  358. bluethat's what I said
  359. bluethat's a primate gap
  360. phalethno clue how to add them
  361. phalethflog add rxjs@^6.5.3 ?
  362. blueflog install rxjs, ya
  363. bluetry that. I'm not sure add is an alias, you can try
  364. phalethadd is not a thing
  365. blueare you trying to build the website btw?
  366. blueor what are ou currently trying to do with flog
  367. phaleth[1/2] STEP 9/13: RUN flog install rxjs
  368. phalethflog: error: read /app/primate/rxjs/package.json: open /app/primate/rxjs/package.json: no such file or directory
  369. phalethError: building at STEP "RUN flog install rxjs": while running runtime: exit status 1
  370. phalethbuild the website but with primate on pnpm, yeah
  371. blueok. that's a flog gap, I'll fix it
  372. phalethcan you also make it so that it will install those peer dependencies automagically?
  373. bluethey should probably be explicit, I think
  374. bluepeer deps are kinda supposed to be provided by the app
  375. phalethwell, it kinda complicates things
  376. phalethcause pnpm and nub didn't have that problem
  377. phalethand in the previous Containerfile I've found:
  378. phalethRUN bun add @rcompat/assert @rcompat/cli @rcompat/crypto @rcompat/dict @rcompat/env @rcompat/error @rcompat/fn @rcompat/fs @rcompat/html @rcompat/http @rcompat/io @rcompat/is @rcompat/kv @rcompat/runtime @rcompat/source-map @rcompat/string @rcompat/symbol @rcompat/type @marko/compiler marko marked shiki esbuild
  379. blueoof
  380. blueit's easy to add the deps though
  381. phalethwhat about just ignoring them? cause I don't need angular for primate website, it's a slowdown
  382. phalethwould be great if flog could just somehow focus on the packages that are actually needed in the monorepo, and not on angular, react and so on
  383. bluepotentially what you're advocating is the ability to run an install inside apps/web, and only get that
  384. bluecan you create a flog for it?
  385. bluea flog task*
  386. phalethhave flog install --filter=./packages/{pema,core,html,marko,markdown,primate}
  387. phalethI can try to create a task
  388. blueok, thanks
  389. bluebtw I feel like this is unnecessarily complicated, no?
  390. bluewould be nice to just have `flog install --base apps/website`
  391. bluethe deps are already specified in apps/website/package.json
  392. phalethyeah, but then those six packages need to be built
  393. phalethit's at flog#35
  394. bluelook at #36
  395. phalethwall of text
  396. phalethtime to crash :)
  397. phalethI think 35 is less complicated
  398. bluewe need both, we'll start with #35
  399. blueok, added note. will do it soon when I'm recharged
  400. phalethflog is gonna be futuristic
  401. phalethsure, time to crash, see ya
  402. blueciao
  403. blueyup, 100%
  404. jreicherdreamreal: glad to hear you've decided not to put blobs in the DB. :)
  405. dreamrealyeah, I hear databases suck at managing, like, data
  406. jreicherWell databases aren't for storage. It's my slogan that I tell everyone who cares to listen: the primary use case of a database is retrieval. And that means querying. And that means STRUCTURED data.
  407. dreamrealYet even RDMS has managed spatial retrieval of data well since around 2004
  408. dreamrealsqlite? totally agreed. postgres, db2 have been able to manage lobs well for quite a while, and postgres is actually quite good at it now. But there are advantages to using a filesystem HERE.
  409. jreicherI believe pointing to the capabilities of a DB product is not the same as saying those are DB capabilities.
  410. jreicherI think they've been shoe-horned in. Oracle DB has queues, and that's more like a DB function than blobs.
  411. dreamrealI dunno about that. LOBs have been used for quite some time, for JCR and other things like that.
  412. dreamrealBut in THIS case, in particular, filesystems win.
  413. dreamrealshoot, I'm gong to have to reboot my system to get all the hardware states synchronized. Power fluctuations from the storm.
  414. dreamrealgah, it might not have fixed it.
  415. jreicherThat's worrying
  416. dreamrealtWell, audio equipment, tahoe
  417. dreamrealless surprising than it should be, some of this stuff's finicky
  418. * jreicher keeps forgetting to look up the etymology of "finicky"
  419. dreamrealdictionary finicky
  420. dreamrealdict finicky
  421. dreamrealyou'd think I'd remember my own dadgum bot commands
  422. dreamrealdefine finicky
  423. * dreamreal glares at nevet
  424. dreamrealdefine finicky
  425. dreamrealtimeout on the endpoint service :/
  426. dreamreallooks like the service itself might have moved or failed
  427. dreamrealor the CDN's burping
  428. blueshow, not tell -clanker
  429. bluedreamreal: there is an insight to be gained in that that clankers are inherently American!
  430. bluein more than one way, as it turns out
  431. bluean insight? insight!
  432. bluewaiting for codex to reset
  433. dreamrealyp blue
  434. dreamrealgrrr where'd he go
  435. dreamrealjreicher, blue https://bytecode.news/posts/2026/09/it-s-been-a-bit
  436. dreamreal... note the podcast link and widget! It's not a good podcast, and should be deleted but I wanted to show it off first :D
  437. jreicherThat looks good!