ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. jreicherI'm a bit surprised to hear you say your name with a soft `g' though. Wouldn't have thought that would be it.
  2. jreicherI'm sure I'm missing something obvious, because I haven't had time to learn about PUDL properly and I might have missed mention here, but why is there both a PUDL and non-PUDL version of BCN?
  3. dreamrealjreicher: https://pudl.bytecode.news/posts/2026/10/updates-for-bytecode-news
  4. dreamrealthere's also a nextjs UI and two basic UIs
  5. bluedreamreal: good narration there
  6. blueone the thing I appreciate about this narration is that it's not a 1:1 rendition of the text; it's an understanding that the spoken word needs to carry a bit more familiarity and flair than a 'dry' written text
  7. blueone thing*
  8. blueany way, do more of these, you have a wonderful voice dreamreal!
  9. blueside note: I've been annoying Z (my wife) to no end, prononuced lever 'LEEver' (which is the accepted UK way); she's sure it's an absolute abomination, and I agree; but I also say `DEBri` instead of `debRI`, for debris, and that's a uk thing as well
  10. jreicherThe oral version elaborates on the written version. Wonder where that idea comes from...
  11. blueprobably by jreicher.
  12. liolocblue: hey! is nub a package manager you made?
  13. liolocoh nvm found it, never heard of it
  14. bluelioloc: hi. no. but also, we're moving to flog, which *is* a package manager I'm making
  15. bluehttps://repopack.com/project/flog
  16. bluehttps://flog.run/
  17. nevetflog — predictable JavaScript package management
  18. bluethe installer won't work yet because repopack doesn't have release primitives yet, but primate 0.43 will move to flog
  19. blueand anyway repopack will have release primitives soon
  20. liolocwhat's the advantage of flog over nub? Seems like nub was kind of similar to your philosophy of not being bound by one specific library
  21. bluenub didn't work as expected, published prelease versions, using otp flows for publishing instead of a web flow, and was generally pretty broken...
  22. liolocah i see
  23. blueand flog adds things I've been missing in a package manager for nearly forever
  24. bluelike this https://flog.run/docs/release-sets
  25. bluesomehow package manager authors think it beneath them to include this feature :P
  26. bluebut this has caused me to publish broken versions in the past, more than once
  27. bluebecause the workspace protocol has no concept of versioning, that's the problem described there
  28. liolocah i see
  29. bluethe workspace protocol is a "trust-me-bro" situation. so flog checks for you that you're not publishing a package in a way that would break stuff
  30. blueanyway, 0.43 will be delayed a bit while we're moving to flog and finishing a few things flog needs in repopack for that, like releases
  31. bluelioloc: btw, repopack can do deploy task branches
  32. bluecan now*
  33. liolocso if you're testing a feature you can deploy it to a specific url?
  34. blueyes
  35. liolocthat's neat
  36. bluefor example, I can deploy your #151 point
  37. bluehttps://pewtxngij-task-151.repopack.app/
  38. nevetPrimate — The Universal Web Framework
  39. blueit will contain your changes to docs
  40. liolocthat's very cool
  41. bluehttps://pewtxngij-task-151.repopack.app/docs/backend/python#desktop-targets
  42. nevetPrimate — Python
  43. bluethis feature is currently limited to apps which do not use secrets or a fixture. but it will be extended to secrets/fixtures
  44. blueso in the future you'll be able to deploy a full app from a branch, seeded with fixtures and secrets
  45. liolocnice
  46. liolocwhat's an example of a fixture that would be added to the deployment?
  47. bluea database import
  48. liolocah yes neat, so you can use a test database for task branches
  49. liolocsomething like that?
  50. blueyes
  51. lioloccool
  52. bluefixtures are actually going to get their repo per project. so they'll be versioned
  53. blueand then when deploying a preview, you'll be able to provide a sha for the fixtures, or just get master
  54. liolocwait a second, i'm getting some interesting ideas
  55. lioloclike in the case of a cms, you could use a versioned fixture as your database no?
  56. blueyes
  57. liolocwow
  58. liolocand you'd be able to rollback to a specific sha
  59. lioloc?
  60. blueya of course. task apps are considered throwaways. but fixtures will be usable by normal apps as well, and you'll be able to deploy with any sha
  61. liolocwow
  62. liolocvery cool
  63. blueya
  64. bluereleases, packages and fixtures are a few of the remaining primitives missing from repopack to be able to cover most use cases
  65. blueand anyway I can already do with repopack now, what I couldn't do with fly before, and that is get a preview of my primate task branches
  66. liolocwhat about hosting costs ? are you using aws btw?
  67. blueusing my own vps
  68. blueon contabo
  69. bluecontabo has an api, so the network will grow mostly automatically, once I have installed the ability to do so
  70. liolocah kk
  71. bluecontabo will not back the only resource provider, could be I use aws in the future too, but reselling margins on aws are brutal
  72. bluewill not be the only*
  73. liolocis contabo better than hetzner?
  74. blueit's much easier to resell resources if you go lower, like vps or better dedis
  75. blueit's probably similar to hetzner, I never used hetzner but contabo has been very reliable
  76. bluerepopack is also going to offer an agentbox feature, which is getting a box for your `rp agent` and opencode/claude code/codex to run on
  77. blueconnected to the chat on repopack.com, of course
  78. blueit would be an alternative to having rp agent and the agent run on your computer
  79. bluebetter isolation, and your computer/server doesn't have to be on all the time
  80. liolochmm wouldn't it be better to let users use their own models with rp agent? I'm asking cause I'm wondering if agentboxes would strain your infrastructure
  81. blueya, rp agent is model agnostic. rp agent is just a bridge to connect your repopack.com chat to your agent
  82. blueyour agent controls what models you use
  83. liolocoh I see, but then what is an agentbox?
  84. bluea computer where rp agent runs on, alongside your opencode/claude code/codex
  85. liolocso its like a docker container for your agent?
  86. blueyes
  87. bluemore precisely, every task gets a docker container
  88. blueand is isolated from anything else
  89. blueit also gets the branch's checkout and instructions via an RP Tool
  90. bluewell, that's the theory, anyway
  91. liolocbut how does a person configure the agentbox? they would need to create a file or something? Like with docker containers?
  92. blueit's all done for you in the background, you buy the agentbox from repopack.com. or you buy your own vps independently and install rp agent and your agent on it
  93. blueyou can either. run it on your comp, on your vps, or via an agentbox from repopack.com
  94. liolocso you have 3 choices for rp agent, 1. buy from repopack.com, 2. buy vps and instsall rp agent on it 3. use your local computer?
  95. blueyes
  96. lioloci feel like most people would just use their own computer, unless you're an enterprise you wouldn't do it
  97. liolocwhich makes sense, since enterprises are better paying customers anyway
  98. bluethat's ok, the agentbox isn't the only source of income anyway, resellgin resources is
  99. blueagentbox is just going to be the least hassle. you add your codex api key to repopack.com and you're done
  100. liolocmaybe agentbox is not the best name, agentcontainer would be better imo
  101. blueya, too long though :P
  102. lioloccause everyone knows what a container is for coding purposes
  103. liolocyeah but the marketing spend you would have to do to tell people what a box is will be quite high
  104. bluecould be just `hosted agents` I think
  105. liolocyeah that's good too
  106. lioloceven better
  107. blueyup
  108. bluebbiab
  109. dreamrealI need to do better music, too. That's very much a trial run
  110. dreamrealpodcast music needs to be flourish and not theme, and that's an actual song of mine
  111. dreamrealand my son said it sounded "very egyptian" :D
  112. blueyou need to do a podcast, with that radiophonic voice
  113. dreamrealoh my voice sucks, and my enunciation is awful
  114. blueI don't know, I like it. you also have a cool accent, slightly southern
  115. bluedreamreal: thoughts on the fixture subrepo?
  116. bluemy only concern is space, if it's used too much for binary stuff, then technically ostree is the superior solution, but I don't know
  117. bluethen again, db dumps are not binary. but db dumps aren't hte only type of fixture people use
  118. dreamrealcould use OCI images for it, they are naturally compressable
  119. blueyou want to use OCI images for *data*?
  120. blueso layered data?
  121. dreamrealI don't WANT anything, but if you're talking data, why not?
  122. blueI'm not against it, I just associatd OCI images with structure/build instructions, not data. but I guess why not
  123. bluethe important part though is that it's easily versionable, that's where git shines
  124. dreamrealeasily managed, easily versioned, easily compressed, easily MOUNTED, cohesive unit...
  125. dreamrealI dunno, maybe that's a dumb idea, I just woke up and I'm trying to come up with new music for the podcast intro, what do I know
  126. dreamrealjust sent you what I was thinking of
  127. dreamrealin discord
  128. bluehow is OCI easily versioned?
  129. dreamrealOCI images are innately versioned, although I don't know what you're asking
  130. blueI'll think about it
  131. dreamrealblue: listen on discord, dang it!
  132. bluedreamreal: scrum week, sorry
  133. bluesoon
  134. bluehi phaleth
  135. bluephaleth: flog can now fully build primate :)
  136. phalethhi blue
  137. phalethI failed to type backticks https://repopack.com/project/flog/tasks/40?
  138. phalethand I noticed, yeah
  139. bluecool
  140. phalethanyway, surprising that flog works this well
  141. blueya, it's amaze sauce
  142. blueand we're just getting started
  143. blue"Clean Primate install improved from approximately 71s to 18s on this host, with byte-identical lockfiles."
  144. blue#40 soon done
  145. blue18s is still too long though
  146. phalethI've tried the trust me bro installer https://repopack.com/project/flog/tasks/42
  147. bluephaleth: yes, this is a known limitation
  148. bluethe flog project needs repopack release artifacts for that
  149. bluehttps://repopack.com/project/repopack/tasks/283
  150. bluethe last comment is by the flog agent
  151. blueand shows the way forward
  152. phalethwall of text
  153. phalethok, I will just put back the artifact url
  154. blueya
  155. blue#40 is solved
  156. phalethtwo jobs at once running
  157. blueya
  158. phalethit got a bit faster, nice
  159. phalethwould it be difficult to publish flog to npm?
  160. phalethI don't think the trust me bro script would work during image build
  161. blueprobably not
  162. blue(about publishing to npm)
  163. phalethok, then how to figure out the url to latest build? https://repopack.com/api/v0/jobs/1/runs/28/artifacts?project=flog
  164. phalethwithout knowing that the number 28 is latest
  165. bluechecking
  166. blueI'm afraid you'll have to wait for #283 to land for that
  167. blueI'll priortise it
  168. phalethok, no hurry
  169. bluelioloc: https://pewtxngij-task-213.repopack.app/blog/primate-043#native-desktop-launchers-and-sidecars
  170. nevetPrimate — Primate 0.43: diamond migrations, deferred navigation and direct SQL
  171. bluephaleth: I seriously hate how those task apps look. I'm going to make short_id electable
  172. bluemaybe `t-primate-213
  173. bluewhere primate is the short_id
  174. bluet-primate-213.repopack.app looks good; and is also a deterministic way to prevent people from using anything that starts with `t-` for normal apps
  175. phalethyeah, but at least they are not scrapeable
  176. phalethlike imagine somebody wanting to share the link publicly and then somebody else guessing the name of their project and trying out all task numbers
  177. blueyes, but almost all task apps will be private
  178. blueyou'll need to explicitly share them with a one-time link, or use --public (with special permissions)
  179. bluethe default mechanism won't be generally accessibl
  180. bluee
  181. phalethone-time link, but what if they wanna navigate the page or just accidentally close browser?
  182. phalethI think it's totally fine the way it is
  183. blueI think exposing task apps to -world- has all kinds of bad implications
  184. blueand those urls look like some chinese spam website
  185. blueanyway, task apps are almost exclusively for developers wanting to preview things
  186. phalethyeah, but the project maintainer can always create a named app where they can deploy whatever
  187. blueyes
  188. bluethat's exactly what I was going to say
  189. blueif you just want a system where you have some people preview features, then create a normal app for it
  190. bluethe task apps are just a way to preview a task without having to download and deploy it all locally, including setting up a db and whatever
  191. phalethok, that means you can somehow hide them behind login, but they are not on the same domain as repopack.com
  192. phalethand traefik just routes trafic straight to containers
  193. blueya, I think that can work
  194. blueanyway they are also shortlived phaleth
  195. bluethey currently expire after 24h, unless you redeploy
  196. blueI'm thinking of reducing that massively
  197. bluemaybe 8h
  198. bluemaybe less
  199. phalethcan I take this one? https://repopack.com/project/primate/tasks/214
  200. phalethok
  201. phalethI'll just do that before clanker takes it
  202. phalethyeah, I cannot take it
  203. phalethwell, assign works
  204. blueyes
  205. bluejuts selfassign
  206. bluephaleth: https://repopack.com/project/flog/tasks/43
  207. blueaccording to clanker:
  208. blue- Resolution: 13.33s → 4.50–5.11s
  209. blue- Full warm-cache install: ~18s → 11.06s
  210. blueand he's not done yet, this is incremental
  211. phalethok, I can revise 214 afterwards
  212. phalethit invented the word packuments
  213. bluewhat's that?
  214. phalethdunno, nobody reads the crap it comes up with
  215. bluelol
  216. phalethelectron-to-chromium@1.5.454 was published during review :)
  217. phalethit looked through those files just to find that, crazy
  218. bluedreamreal: BCN intro is GOOD
  219. blueforgive my preposterous delay
  220. dreamrealheh
  221. bluedreamreal: another thing I thought about: you reading the article aloud is gonna shut down good all those trolls on HN that say the website is completely ai-generated
  222. dreamrealYeah, imagine someone actually writing decent diction
  223. dreamrealbut I'm not worried about the trolls
  224. dreamrealreading it aloud also shows some inversions of thought process, which may feed into the posts themselves
  225. dreamrealLike, as a writer I know I'm going to get there, but as a speaker, you close some gaps sooner than you might otherwise have
  226. bluemhm
  227. bluedreamreal: jreicher: https://www.youtube.com/watch?v=L01w2jJJGek
  228. nevetYouTube: John Butler Trio - Media | Because Music