ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Community

Chat Logs

Sunday, October 11, 2026 (America/New_York)

  1. * jreicher quit (Quit: In transit)
  2. * jreicher joined #nevet
  3. * dreamrea1 joined #nevet
  4. * dreamreal quit (*.net *.split)
  5. * jreicher quit (Quit: In transit)
  6. * jreicher joined #nevet
  7. dreamrea1feed add https://shkspr.mobi/blog/2026/10/i-paid-people-to-try-and-follow-my-readme/
  8. nevetAdded feed "Terence Eden’s Blog" with 20 entries
  9. dreamrea1suggest https://shkspr.mobi/blog/2026/10/i-paid-people-to-try-and-follow-my-readme/
  10. nevetSuggested draft saved from https://shkspr.mobi/blog/2026/10/i-paid-people-to-try-and-follow-my-readme/.
  11. bot[streampack-dev/streampack] New issue #192: RSS rating guess: a rubric deployments can change, and a read-only list of guesses - https://github.com/streampack-dev/streampack/issues/192
  12. bot[streampack-dev/streampack] New PR #193: RSS rating guess: a rubric deployments can change, and a list of guesses - https://github.com/streampack-dev/streampack/pull/193
  13. * dreamrea1 is now known as dreamreal
  14. * nevet joined #nevet
  15. * 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/streampack-dev/streampack | This channel is logged: https://bytecode.news/logs/irc/libera/nevet
  16. dreamrealfeed add https://www.cockroachlabs.com/blog/experiment-running-hospital-code/
  17. nevetAdded feed "Blog posts | RSS Feed" with 100 entries
  18. bluedreamreal: any possibility to have nevet scan for [name]#[number], then look it up on repopack's public API, and show task title?
  19. blue(NB: the api does NOT exist yet. this would be a FIRST use case for it. would still require a token though)
  20. blueor maybe that already exists via the normal task api, hm
  21. dreamrealI mean, repopack would just be a forge
  22. dreamrealthe answer is "of course, it just needs a specification and an issue"
  23. dreamrealalready support github vs gitlab, and other forges are just specific implementations against the forg
  24. bluebut you don't currently detect #<number>, is my point
  25. dreamrealSo that's just an operation
  26. dreamrealthe API is already there, we detect URLs, nothing says another operation couldn't look for specific types or formats of URLs
  27. bluek
  28. bot[streampack-dev/streampack] New issue #194: operation-specs: `cve`, by CVE id, package coordinates or a bare package name - https://github.com/streampack-dev/streampack/issues/194
  29. bot[streampack-dev/streampack] New PR #195: operation-specs: cve, by CVE id, package coordinates or a bare name - https://github.com/streampack-dev/streampack/pull/195
  30. bot[Christian Rackerseder | Blog] Responsive vs. adaptive web design - https://www.echooff.dev/blog/responsive-vs-adaptive-web-design
  31. * jreicher quit (Quit: In transit)
  32. * jreicher joined #nevet
  33. jreicherThe community's interest in documentation is one of the reasons I love using Emacs (re the readme blog post)
  34. dreamrealI have an article written on it for monday, I think.
  35. dreamrealbut I'd love to see more about what you're using and why.
  36. jreicherYou mean you want to know more about Emacs and what I do in it?
  37. jreicher(and why?)
  38. dreamrealNo, I want to know what YOU do, I am, uh, experienced in emacs
  39. bot[streampack-dev/streampack] New issue #196: Audio for posts: uploads, a post's audio, and enclosures in the feeds - https://github.com/streampack-dev/streampack/issues/196
  40. jreicherWell when it comes to Emacs I do almost everything in it. Pretty much the only other application I ever run is a web browser.
  41. dreamrealRight, but how does that affect the documentation?
  42. jreicherEmacs has terrible discoverability. And perhaps necessarily so, given the richness of the environment. It would be like expecting the syntax and standard library of a programming language to be discoverable. So there's a strong self-generating force for documentation with anyone who cares about Emacs.
  43. dreamrealAh, I see what you mean. Yeah, agreed.
  44. dreamrealAny thoughts on #196 up there?
  45. jreicherI haven't been looking at any of the issues but I'll look at that one now.
  46. jreicherUmm. You would put blobs in the DB?
  47. dreamrealQuite possibly.
  48. dreamrealThey'd take up about the same amount of room on a filesystem.
  49. dreamrealI'm still not entirely decided there.
  50. dreamrealI'm not even sure the idea has merit *regardless* of the implementation.
  51. jreicherYeah, I understand. Just that point jumped out at me because I've heard very strong opinions on that over the years.
  52. jreicherAnd I have a strong opinion myself.
  53. dreamrealBut feel free to add your own comments to the issue! I mean, seriously: I've done podcasts before for javachannel.org but that was very much a manual process.
  54. dreamrealWell, feel free to share! I'd be working clean-room (and smooth-brain) so I need all the input I can get.
  55. dreamrealMaybe the "right way" is to literally do a companion podcast and provide a way to add pointers to the manual podcast; I do not know.
  56. dreamrealMy expertise here is going to be in the *recording* process and that's pretty much the end of it.
  57. jreicherAt the moment I'm trying to wrap my head around a multimedia post. The simple version is obvious but I'm not sure I really know what it means "in depth". At least not when it's text-led. A video or audio file with closed captions is more clear.
  58. dreamrealWell, the text posts are the main thing: I'm a writer, not a speaker (one of my biggest challenges here would be in DOING the speaking, because I don't want it generated.) So I'd be publishing text and then recording audio using the text as a base transcript, and amending the text posts with something that says "hey, would you rather hear someone mumble their way through this, instead? HERE YOU GO."
  59. dreamrealThere will never be video if I'm involved.
  60. * nevet joined #nevet
  61. * 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/streampack-dev/streampack | This channel is logged: https://bytecode.news/logs/irc/libera/nevet
  62. dreamrealcve log4j
  63. nevetlog4j:log4j: 6 known to OSV, worst CVE-2019-17571 (critical), newest CVE-2023-26464 (high); OSV lists 2.0 as fixing all. https://osv.dev/list?ecosystem=Maven&q=log4j%3Alog4j org.apache.logging.log4j:log4j-core: 11 known to OSV, worst CVE-2021-44228 (critical), newest CVE-2026-34480 (medium); OSV lists 2.25.4 as fixing all. https://osv.dev/list?ecosystem=Maven&q=org.apache.logging.log4j%3Alog4j-core
  64. dreamrealcve guava
  65. nevetcom.google.guava:guava: 3 known to OSV, worst CVE-2018-10237 (medium), newest CVE-2023-2976 (medium); OSV lists 32.0.0-android as fixing all. https://osv.dev/list?ecosystem=Maven&q=com.google.guava%3Aguava
  66. dreamrealokay, off for family stuff
  67. dreamrealWould definitely be interested in further thoughts on the audio thing, it's very much a lark
  68. jreicherIf you were to do an audio-only post, what do you think it would look like? I'm not suggesting you actually do this, but I'm trying to flesh out what audio "means" in this context.
  69. dreamrealOn the site, it'd be a player at the top of posts with audio (so you could listen there) and there'd be a podcast RSS feed
  70. jreicherNo I mean no text for the post at all. Just audio.
  71. jreicherWhat would the "post" look like?
  72. dreamrealOh, would be HIGHLY unlikely
  73. dreamrealI can't see doing audio-only
  74. dreamrealnot personally
  75. dreamrealI mean, I guess it'd be a content-stub: "Here's an audio only post! Go listen, y'all!"
  76. jreicherIt's just a thought experiment; I'm not suggesting you would do it. But I wanted to know what it would look like if you did.
  77. jreicherOK so even with that the audio is kind of "to the side"
  78. jreicherit's not the entry point of the post, if that makes sense
  79. dreamrealyeah
  80. dreamrealaudio would be, for me, almost always ancillary, mostly because *I* am not a strong speaker, especially extemporaneously, and nevet is not a "content delivery site" - if you want a podcast, nevet has podcast FEATURES but you wouldn't use it for "a podcast"
  81. jreicherI don't like it. :) I think it would make sense to have the "post" directly playable from the front page. And it might make sense to do something like that for a text-and-audio post too. So the front page carries a link to the text post, but there's a play button for the audio next to that link on the front pager also.
  82. dreamrealWell, that'd be easy enough to add, honestly
  83. dreamrealthe front page for the UIs is made up from the content feed from nevet, so the information would be available
  84. jreicherDoing it that way might make the feature quite appealing.
  85. bot[streampack-dev/streampack] New issue #197: cve: throttle the command, and go easy on Maven Central - https://github.com/streampack-dev/streampack/issues/197
  86. dreamrealYeah, I mean, the backend and the frontends are separate things.
  87. dreamrealbut new features tend to show up on the backend first, so the frontends are just views on the content.
  88. jreicherAnd if you really wanted to go to town you could have AI-generated speech from the text. Not sure what would be a cheap way of doing that though (if one exists at all)
  89. jreicherWell one of the reasons why I've asked the questions I have is that it might have a bearing on the backend. The post now has multiple objects and the text is no longer a primary one; they are all of equal status.
  90. dreamrealPlenty of ways to do that, but that'd be a really crappy way to represent the text forms. Doable, but not good. Most of the posts would be 5-7 minutes to read aloud, and I have a full pro rig here, so the tech aspects would be easy.
  91. dreamrealPro mics, even good "podcast-pro" mics like a Yeti (it's not a pro mic but it suffices for easy stuff, I'd probably use it because the EQ profile is so normal for podcasts)
  92. dreamrealI don't have NPR-level gear here, but a standard NPR broadcast in the US has about $100K of production gear involved, it sounds FANTASTIC but is a little out of what my audience would need or want or know they wanted, I think
  93. bot[streampack-dev/streampack] New PR #198: cve: throttle the command, and go easy on Maven Central - https://github.com/streampack-dev/streampack/pull/198
  94. bot[streampack-dev/streampack] New PR #199: Post versions, starting with recorded audio: uploads, storage, serving and enclosures - https://github.com/streampack-dev/streampack/pull/199