ByteCode.News
Submit RSS Atom Sign in

Back to the channels

#nevet

  1. bot [jottinger/bytecode.news] New issue #119: Populate lib-blog with blog domain services - https://github.com/jottinger/bytecode.news/issues/119
  2. bot [jottinger/bytecode.news] New issue #117: Harden anonymous post submissions - https://github.com/jottinger/bytecode.news/issues/117
  3. bot [jottinger/bytecode.news] New issue #116: Anonymous post submission rejected despite design intent - https://github.com/jottinger/bytecode.news/issues/116
  4. bot [jottinger/bytecode.news] New issue #115: Add caching to factoid reads - https://github.com/jottinger/bytecode.news/issues/115
  5. bot [jottinger/bytecode.news] New issue #114: Add factoid usage audit data - https://github.com/jottinger/bytecode.news/issues/114
  6. bot [jottinger/bytecode.news] New issue #113: Add ingress guardrails for long-running operations - https://github.com/jottinger/bytecode.news/issues/113
  7. bot [jottinger/bytecode.news] New PR #118: Updating to specifically test and allow anonymous posts - https://github.com/jottinger/bytecode.news/pull/118
  8. * jreicher joined #nevet
  9. blue dreamreal: `git branch -m main master`
  10. jreicher Woke. :p
  11. blue dreamreal has been around too many san fransciso people :P
  12. dreamreal dreamreal doesn't get caught up in such crap. It's a label. github has defaults and I don't care to signal to YOUR group any more than I care for others'. Deal.
  13. blue dreamreal: you implicitly do get caught up in such nonsense, whether you like it or not, if you give in to woke insanity
  14. blue you just choose to frame as I don't care :P
  15. dreamreal It ends up allowing THEM to control you (or me) just as much as anything else
  16. dreamreal "Oh no they declared pink a gay color now I despise pink"
  17. dreamreal I literally do not care
  18. dreamreal I don't care to serve the "unwoke" crowd any more than I care to serve the "woke" group
  19. blue shrug; changing the default branch will take 10s of your life. which you contend is getting 'caught up' in stuff. master has been the default for forever; it doesn't represent the unwoke crowd, it represents the baseline; it's what git itself uses (at least until v3), and it what the official git documentation uses
  20. blue I used it well before woke was a thing and will use it longer after it's completely burnt down
  21. dreamreal Then do so! I find that ten seconds to be nothing but serving a particular master, and I don't LIKE masters
  22. dreamreal so I stick with 'main' as it costs me nothing and has no meaning for me other than a default
  23. dreamreal I know of ONE person who really gets caught up in it now and... he's on this channel
  24. blue I will quote the terrible barack obama, who got ONE thing right in his own life: "not choosing is also a choice"
  25. dreamreal I've worked with people who were rabid that 'master' was offensive; I thought it was silly but spending three days arguing over the semantics was more than I cared about: I needed them to be able to hold their noses and work
  26. * dreamreal nods at Neil Peart
  27. dreamreal I want my choices to matter and this one doesn't
  28. dreamreal I've already spent more energy on it this morning than I have in the last year, except every other time you bring it up
  29. blue it doesn't matter they think master is offensive. if they think it is, they're morons. but this was a non-problem until the woke crowd came along. we used to be able to talk about master as the canonical branch, and there's no good reason to pay any tax on that now
  30. dreamreal It's not a problem NOW
  31. blue it is
  32. dreamreal it does not HURT us to talk about main vs master
  33. blue because when I fork your problem, I need to rename it, because all my scripts and tools use master
  34. blue your project*
  35. blue there is no way to know the default branch in git, because there is no one. in lack of that, tools need to be wired somehow, and main branches break that assumption
  36. blue you're making people's lives unnecessarily harder with this
  37. dreamreal Oh man
  38. dreamreal Okay, it's a good thing to start your morning off with a laugh
  39. blue I literally spent a day debugging one of my tools the other day because someone moved to main
  40. dreamreal you should have led with that
  41. blue maybe it's a non-problem to you, to me it is
  42. dreamreal I get it
  43. dreamreal I see "moving to main" in 2026 CE ridiculous
  44. dreamreal but I see "moving to master" just as ridiculous :D
  45. dreamreal it's virtue signals all the way down.
  46. dreamreal What % frum are you?
  47. dreamreal hurry up, I need to know before I can look at your issue, it might not be kosher enough!
  48. dreamreal oh wait I don't care
  49. dreamreal solved
  50. blue it's funny how people complain all the time you need standards to work more effectively together, and then they are quicker than lightning to rid themselves of the one quasi-standard we had no problems with
  51. dreamreal it's also amusing to me that deploying from a dev branch (and leaving it there, which is what I had done) was less of an issue than the main branch's name :D
  52. dreamreal Well, some people, some very NOISY people, got caught up in it
  53. dreamreal I find main vs master an asshole issue, and were it to come up in an interview I'd disqualify the candidate
  54. blue why? it's a standards issue, your framing is completely wrong
  55. blue git has no default branch, so a convention is in order
  56. blue this is not hard to understand
  57. dreamreal It's the wrong standard to care about
  58. blue is it really?
  59. blue I work with git daily
  60. dreamreal Right, and it has defaults, and I never bothered to change it
  61. blue seems like something I should care about it
  62. dreamreal when master switched to main in github, I didn't care and don't care about it
  63. blue so you don't care when others make choices for you, is that what you're saying? because you seemed to indicate something else above
  64. dreamreal Asshole move: "Romans need to drive on the side of the road I like" non-asshole move: "What side of the road do Romans drive on?"
  65. blue something about not serving any masters and so on
  66. dreamreal I seem to remember someone's anger about libertarianism and how horrible pedantic libertarianism is
  67. blue yes, when libertarianism doesn't deal with real life morals. this isn't applicable here
  68. dreamreal This isn't a real life moral :D
  69. blue I can't convince you, but let me tell you that as a principle, I don't work with main branches, so I'll be sending PRs from my master fork, which you probably have no problem with, since that's the side of the road I drive on?
  70. dreamreal and there's an actual difference: nobody's standing across from those peoples' yards stabbing puppies, so your rage at their imagined reaction in the drawing room is unnecessary. Pony up and stab a REAL puppy and see how they react, then judge. (And then burn, because... puppies.)
  71. * dreamreal won't care, because he is capable of managing more than one worldview as a paradigm for others at a time
  72. blue (I like puppies though, why should I stab them)
  73. dreamreal issue PRs away, I'll be fine
  74. dreamreal to make a point, of course
  75. dreamreal point's there, gotta make it!
  76. dreamreal can't allow others to possibly be willing to say something they don't accept in the real world
  77. blue nah that's not my style. it's just my all dev tools are wired to master and I'm not willing to change that
  78. blue I will also generally call it master, fyi, even if it's called differently, because that's the side of the road I drive on!
  79. blue not willing to spend any mental energy on maintaining two terms for what should be one
  80. dreamreal And I will SOMEHOW be able to integrate that, so when you do, I'll manage... bleeding... on the side of the road... "he said... 'master'... aaaaagh"
  81. blue yes
  82. blue funnily: had you created the branch locally first (the normal git flow) you'd already have a problem :P
  83. blue well, branch/repo, I mean
  84. dreamreal I do so appreciate how you think how you do it is the only normal way
  85. blue it's not. but it's the standard git way
  86. blue I do create repos using gh too
  87. dreamreal It's your standard git way. I haven't used git init in a long time.
  88. blue regrettably though, we have a generation of devs who equoate git with github, which is really dumb
  89. blue dumb & dangerous, I should say, given it's microsoft
  90. dreamreal This is part of why I do tech interviews the way I do, incidentally: I'll be kinda ridiculous on purpose. One interview that I particularly enjoyed, I said "pardon me, I'm gonna use a terrible scottish accent for this interview" and continued... in my normal slightly-southern drawl. The interview actually stopped me to point out that that wasn't a scottish accent - and I said "well, it's a REALLY
  91. dreamreal TERRIBLE scottish accent." His reaction told me a lot about how the interview was going to go, because it signals some of the things he cares about. (He did fine; another person argued with me about it.)
  92. blue dreamreal: that's a fine difference, which is: you paying someone to do something vs FOSS. At work, I'm using mac, I also work with java. Both things I probably wouldn't do it privately. So if my employer used main, I wouldn't care: he's paying me for his nonsense. This is completely different in projects I contribute my free time to, I hope you understand the distinction, or it has merit
  93. blue there's a fine difference*
  94. blue therefore, your rant about prospective employees is irrelevant here, because we're of the same opinion. If a candidate told me he has a problem with main (or master), I'd see it as a negative point. I'm PAYING him to shut up about branch names
  95. dreamreal Dude, I have no intention of forcing you to do anything you don't want to do, regardless of your reason for not wanting to do it
  96. dreamreal I don't want to even ASK you to do what you don't want to do
  97. blue I understand. But understand some things are IMPLIED. You use main, that's fine: if I want to contribute, the implied request is "use main". I can't force you to switch, so the compromise is me using a fork instead of committing directly. Same for docker: I can't use docker, but I'm not going to start sending PRs for nspawn, and at the same time, I still need to get it working locally, which is why I enlisted
  98. blue phaleth's help, because I absolutely SUCK at devops
  99. blue my devops skills are so bad that I'd rather install things on the host than mess around with docker bridges. I'm TRYING to fix this on the new computer, hence why I asked him to help
  100. dreamreal I suck at devops right along with you. ANy time I can find a competent devops guy who's invested, they're golden. i know some people who're absolutely RIDICULOUS IRL whose oddities I endure because 1) they're still people but 2) devops
  101. blue regardless of the master/main discussion, I'm REALLY missing an ordinary workflow where issues=branches, and committing to master isn't possible
  102. blue (not in nevet: as a general thing, I mean)
  103. dreamreal I'm about to switch nevet to requiring PRs to merge to main, it's getting stable enough where that is going to start mattering
  104. blue GH is doing something similar, but only in the backend; issues and PRs are in the same DB table in GH, and issues get branches created for them, they just don't advertise that
  105. blue but my ideal flow is: issue #1 is created; system creates issue/1, as soon as the issue is accepted by maintainers; push access: OP+maintainers+assignees. merging access: maintainers
  106. blue the GH distinction of issue/PR is very, very confusing to me
  107. dreamreal Well, a given issue can have multiple PRs
  108. dreamreal multiple branches
  109. blue that's my point: an issue *needs* to be a PR; one branch, with potentially multiple commits. nothing stops you from creating subbranches for that
  110. blue an issue is a full item of work, IOW
  111. dreamreal What if there are multiple ways to address the issue?
  112. blue concurring implementations?
  113. dreamreal Like, one person does it with a database, another does it with threads, another person says "ooo here's my chance to use rust"
  114. blue the means the issue is too broad. it's really three issues
  115. * dreamreal sighs, watching the humor fly past blue
  116. dreamreal Okay, fine, let's be a little more limited: one person does it with a subselect, the other with a view, and the third does a brute force that actually handles timeseries better: all actually address the issue in scope, but have different strengths and weaknesses: issue is the same, three branches, three PRs, maybe more because aliens.
  117. blue is this a real thing: if you're working in a team, you'd discuss this aforehand. why would you have three people doing three different things?
  118. blue and then all PRing it into master???
  119. dreamreal Actually, I'm working on an issue with nevet like that: #113. I think the scale of the original issue is right but too broad for now, so I'm fixing it based on a comment. But I can totally see someone else going "wait the integration layer is fine for this, what if we compare"
  120. dreamreal Just because it's a PR doesn't mean it's ACCEPTED
  121. blue yes; but an issue isn't accepted either; only when it's closed and merged onto master
  122. dreamreal So why would you presume otherwise for everything else? Lots of different workflows out there; it's nice to be prescriptive but not so great to be proscriptive. Remember RCS? SVN?
  123. dreamreal Hell, clearcase, which I'd forgotten about: IBM had a few of them, before git took over, some were great, others... not so great :D
  124. blue How is this proscriptive: the only thing the system would do is allow you to define rules for the repository. And the rules *I* would set is: no direct committing to master, only FF merges from issue branches. What's the problem?
  125. dreamreal That's a fine rule, and you should enforce it, especially for yourself, and nevet's about three steps away from it itself. nevet's been fast and loose so far mostly because this iteration was created on a lark, because I got annoyed at the streampack design enough to try something different one morning.
  126. dreamreal And being proscriptive IN A TEAM is different than being proscriptive in a tool. Team proscriptions good, tool proscriptions baaaaaad.
  127. blue yes, and I wasn't complainign about nevet, was I?
  128. blue 13:38 < blue> (not in nevet: as a general thing, I mean)
  129. dreamreal No, I was just making the comment. It's something people do when they converse.
  130. dreamreal karma changed, btw: subject lengths are ~= 45 chars (over that is considered to be conversation, not karma) and it has some other rules about specific names that help
  131. dreamreal So you can now talk about C++
  132. dreamreal C++++
  133. nevet C++ has neutral karma.
  134. dreamreal :D
  135. blue that's great -- so we can finally talk like normal mortals?
  136. blue NICE!
  137. blue I'm glad you came around about that
  138. dreamreal Yes, it has an emdash cutout for morons who use typesetting rules WHEN THEY TYPE MANUALLY
  139. dreamreal Well, you were so stupid and annoying about it that I wondered if there was a way to write karma to compensate for low IQ
  140. blue of course, would have been better if you did that before I complained, but sometimes a man needs to see the results of his actions for himself
  141. dreamreal and it handles C++ and J++ very specifically, and THIS is probably a karma action :D
  142. dreamreal Ooo
  143. dreamreal I shoudl crank up logging in the karma to walk through how that didn't trip as karma - actually, it's probably the last J++
  144. dreamreal (if a language is the last token in a subject, it assumes it's not a karma action)
  145. blue nevet is gearing up to be almost perfect now
  146. dreamreal You have some very very very inconsistent measures of "perfect"
  147. blue parse it as "ai perfect". fulfilling all my needs
  148. blue dreamreal: what's the business case for nevet, anyway?
  149. blue dreamreal: does nevet have an rss watcher service?
  150. dreamreal rss list
  151. dreamreal grr and yes
  152. blue how do I add https://primate.run/blog.rss in the #primate channel?
  153. dreamreal feed list
  154. nevet Enigmastation.com - https://enigmastation.com/feed.xml
  155. blue is it possible?
  156. dreamreal hold on
  157. dreamreal yes
  158. dreamreal okay, interesting: that's definitely an RSS feed, need to figure out why the discovery is failing
  159. dreamreal working on a different issue right now, but that's next
  160. blue k
  161. dreamreal I'm working on adding timeouts for operations, which has some fascinating implications for virtual threads
  162. blue for what operations?
  163. dreamreal but that RSS failure's pretty important
  164. dreamreal all of them!
  165. dreamreal like the dispatch needs to have some way to measure/address poorly-behaved operations
  166. dreamreal blue: .. errr.. early diagnosis is that that url returns a 404 with a valid RSS body
  167. dreamreal curl -sI https://primate.run/blog.rss # shows HTTP/2 404
  168. blue I get 200
  169. blue curl also shows 404, no idea why, let me look into it
  170. blue dreamreal: if you open it in the browser, does devtools show 200?
  171. dreamreal it does
  172. dreamreal okay, HEAD is returning 404 but GET is returning 200
  173. blue yes
  174. blue HEAD isn't defined on this route
  175. blue ➜ ~ curl -v https://primate.run/blog.rss
  176. blue < HTTP/2 200
  177. blue -I forces HEAD
  178. blue HEAD isn't defined for the /blog.rss route
  179. blue do you NEED HEAD for some reason?
  180. blue I mean, I can add it, I just don't see the point
  181. dreamreal no, was just reporting what I found as I tested
  182. blue is it for periodic caching?
  183. dreamreal HEAD is expected to be lighter than GET so it's usually a good first test
  184. blue hm
  185. blue `According to the HTTP spec, a server should support HEAD anywhere it supports GET.`
  186. dreamreal basically "show me the headers, only the headers, that a GET would see so I can see if I want to download all 1.4MB of your CSS"
  187. blue can you file a primate issue?
  188. dreamreal yes
  189. blue something like: add an app option to mirror GET routes as HEAD unless a HEAD route was created manually
  190. blue default: false
  191. * Chronos likes "main" better than "master" because it's shorter
  192. Chronos Am I allowed to have that preference for that reason?
  193. dreamreal I find I struggle to care either way: master vs main is WAY under the TCP packet barrier, those two chars aren't going to make much of a difference
  194. Chronos (Mostly just poking fun at the debate above, heh.)
  195. dreamreal it deserves it
  196. dreamreal Chronos: so what did you think of teh safecracker thing?
  197. Chronos dreamreal: safecracker thing?
  198. dreamreal https://github.com/jottinger/bytecode.news/issues/98
  199. dreamreal it's sort of like mastermind but way easier for IRC, since it uses digits and not a more limited set of constraints
  200. bot [jottinger/bytecode.news] New issue #120: Bug: https://primate.run/blog.rss is NOT being discovered when being added - https://github.com/jottinger/bytecode.news/issues/120
  201. bot [jottinger/bytecode.news] New PR #121: Adding operation timeout - https://github.com/jottinger/bytecode.news/pull/121
  202. dreamreal blue: found it. Bug was in client; was not sending an Accept header.
  203. blue oh? is that needed?
  204. dreamreal Well, adding one fixes it
  205. dreamreal curl adds */* by default, I wasn't sending one at all
  206. dreamreal Now I'm adding `application/rss+xml, application/atom+xml, application/xml, text/xml, text/html, */*;q=0.8`
  207. blue thanks for the issue, dreamreal
  208. blue I'm a bit conflicted how to namespace this feature.. putting it under http feels a bit too lowlevel
  209. dreamreal Well it IS HTTP
  210. * nevet joined #nevet
  211. * 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/streampack
  212. blue that's why it'd be an opt-in with default false, since it's magic
  213. dreamreal huh, that quit message...
  214. bot [jottinger/bytecode.news] New PR #122: Fixing RSS discovery - https://github.com/jottinger/bytecode.news/pull/122
  215. Chronos dreamreal: safecracker looks neat!
  216. Chronos safecracker
  217. Chronos Awww.
  218. Chronos nevet doesn't love me. :(
  219. dreamreal Chronos: I haven't written it!
  220. Chronos Oh, heh!
  221. dreamreal The operation is still an open issue!
  222. * Chronos should probably upload his ancient IRC bot to GitHub for posterity.
  223. dreamreal "Chronos: hey, the *proposal* at issue XYZ, does that look interesting? Shoudl we write it?" chronos: "Wow, that looks so cool now that I've stepped into the future and you already wrote it by the time I pretended to look at it!"
  224. dreamreal but the neat thing about the safecracker operation is that it literally changed timed events in nevet just by being proposed :D
  225. Chronos Get'r'done!
  226. dreamreal I mean, considering I was waiting for you to give it a thumbs up or thumbs down... now I can :D
  227. dreamreal Chronos: the safecracker thing made me revise timed events: now nevet has a tick operation that things can listen for. github and rss now use THAT with an offset timer ("last poll was X... next poll is Y... is it after Y yet?") which separates it from the cron scheduling they WERE using
  228. Chronos Very nice
  229. dreamreal RSS and github were fine with really coarse granularity, like hours and minutes... safecracker needs seconds
  230. blue dreamreal: http.autoHead: p.boolean.default(false), good?
  231. dreamreal blue: +1
  232. dreamreal blue: ++ too
  233. nevet blue now has karma of 2.
  234. blue k. I'm actually gonna see how I can implement it in a way that's nondumb. because I don't want to create senseless HEAD routes for every GET route for which a HEAD route does not exist. it's gonna go in the request processing logic
  235. blue this is a classic case of "better data structures aren't good"
  236. blue the problem is primate doesn't even do this kind of matching... gonna have to wire it down
  237. blue possibly the HTTP router will need the same option
  238. blue which is probably not a bad idea, anyway
  239. Chronos Just testing something -- because I'm curious.
  240. Chronos Just testing something--because I'm curious.
  241. blue Chronos: he fixed that
  242. dreamreal Wellyeah, it's thorny. Maybe on a HEAD, try to resolve the head specifically, and if the flag is set true AND the head fails, search for GET?
  243. Chronos Interesting.
  244. Chronos Just testing something-- because I'm curious.
  245. nevet Just testing something now has karma of -1.
  246. Chronos Ah ha!
  247. Chronos Just testing something --because I'm curious.
  248. dreamreal Actually, that might be a bug too: that second one shoudl have triggered. OH, NO IT SHOULDN'T!
  249. Chronos Nice enhancement.
  250. dreamreal Chronos: that helps cut out karma operations where *program arguments* are being mentioned
  251. blue the positive case there is arguable ok for a karma feature. I'm on the fence on that
  252. blue arguably*
  253. dreamreal like, if I say do javac --version - that's NOT a karma operation
  254. dreamreal so it's looking for things that LOOK LIKE arguments, since nevet tends to hang out in programming channels
  255. Chronos for (int i = 0; i < 10; i++)
  256. nevet for (int i = 0; i < 10; i now has karma of 1.
  257. Chronos tsk tsk.
  258. dreamreal no offense but damn you to hell
  259. Chronos Lol!
  260. dreamreal nevet is RIGHT here: I hereby declare that this is why you use a ranged stream, so karma isn't triggered
  261. blue dreamreal: https://github.com/primate-run/primate/blob/master/packages/core/src/private/serve/App.ts#L475
  262. Chronos dreamreal: Sure, whatever helps you sleep at night ;)
  263. dreamreal "I would have used a for loop here, as it's very clear and straightforward and complete idiots would understand but noooooo range(0,10).forEach( i->{}) it is, so karma isn't triggered
  264. blue this will probably need to become: OR `verb === "head" && verbs.get !== undefined`
  265. dreamreal idiots untie!
  266. blue but that's only half of the story. would still need to serve only the heads, and a null body
  267. blue headers*
  268. dreamreal well
  269. Chronos dreamreal: that's a deep subject to get into
  270. dreamreal that looks right BUT don't forget: HEAD is HTTP, so there's a lack of formal requirement
  271. Chronos </dadjoke>
  272. dreamreal HEAD *can* return the body
  273. blue we're talking about the autocase here
  274. blue if you define a head route yourself, you're gonna get what you asked for
  275. dreamreal I get it, BUT if you're going to rely on decay, I'd say "do the simple thing" and return the GET
  276. dreamreal if someone wants only the HEAD content they need to say so, because it literally means different things, and the fallback is stating "no, they're the same for idiot clients"
  277. blue dreamreal: I think you're actually mistaken here. the HTTP spec dictates HEAD must not return a body
  278. dreamreal Does it say it MUST not? Ooo, the W3C is getting good at last. Then there you are.
  279. blue https://www.rfc-editor.org/rfc/rfc9110#section-9.3.2
  280. nevet RFC 9110: HTTP Semantics
  281. blue `The HEAD method is identical to GET except that the server MUST NOT send content in the response.`
  282. dreamreal There you are, then
  283. dreamreal ~rfc 9110
  284. dreamreal rfc 9110
  285. nevet rfc 9110: 9110: HTTP Semantics (https://www.rfc-editor.org/rfc/rfc9110.html)
  286. blue hence
  287. blue 15:27 < blue> but that's only half of the story. would still need to serve only the heads, and a null body
  288. dreamreal Prefer the specs operation with nevet!
  289. dreamreal It helps populate the factoids
  290. dreamreal rfc 9110
  291. nevet rfc 9110 is 9110: HTTP Semantics. URL: https://www.rfc-editor.org/rfc/rfc9110.html
  292. blue is it searchable?
  293. blue ?rfc http
  294. blue hmpf
  295. blue feelsbadman
  296. dreamreal What do you mean? The *factoids* are
  297. dreamreal the specs plugin does not aggressively search, no
  298. blue no, can I search the rfc body with nevet?
  299. dreamreal No, it doesn't cache the rfc body
  300. blue body of work, I mean
  301. dreamreal Eventually I'd like it to summarize the spec via AI but not yet
  302. blue ?rf http would return all rfcs containing 'http' in their titles
  303. blue ?rfc*
  304. dreamreal yes, that'd be awesome but incredibly verbose
  305. dreamreal but like I said, it doesn't do that
  306. blue maybe do a 5 cutoff or so
  307. blue the thing is this: I needed to look the rfc first in my browser, and then I already had the link: so going back here and doing !rfc <n> was.. an indirection
  308. blue look up*
  309. dreamreal "it has the wrong priority, dreamreal! You chose date order, it's OBVIOUSLY the relevant RFC I wanted first!"
  310. dreamreal blue: Oh, I know.
  311. blue an rfc title search would be useful, I think
  312. blue preferably case insensitive
  313. dreamreal It would, but I need to figure out the semantics for it
  314. dreamreal someone should file an issue for that, actually
  315. dreamreal while I'm working on other things :D
  316. dreamreal this also has the side effect of being spanned to the other specs: all the spec operations right now are peers, and search means specifics per spec class
  317. blue ask what's the http rfc defining how HEAD works?
  318. nevet RFC 7231 defines HTTP/1.1 semantics, including the HEAD method. HEAD is identical to GET except the server must not send a message body in the response - only headers are returned.
  319. blue feelsbadman :(
  320. blue it's 9110 NEVET
  321. dreamreal tell anthropic, not nevet
  322. dreamreal nevet doesn't care
  323. dreamreal ask what's the difference between rfc 7231 and rfc 9110
  324. nevet RFC 9110 (2022) obsoletes RFC 7231 (2014) as the core HTTP semantics specification. RFC 9110 consolidates and updates the HTTP/1.1 specification with clarifications, corrections, and lessons learned from nearly a decade of implementation experience, while maintaining backward compatibility with the fundamental protocol defined in 7231.
  325. blue ask what's the http rfc defining how HEAD works; ignore obsoleted ones?
  326. nevet RFC 9110 defines how HEAD works. It's the current HTTP semantics specification that replaced the obsoleted RFC 2616.
  327. blue GOOD.
  328. dreamreal hm, interesting potential revision for the ask - "ignore outdated references if more current references exist."
  329. blue yes!
  330. blue in which case, it IS nevet and not anthropic :P though the anthropic default is dumb here
  331. blue anyway, I had it filed under HEAD must not have body, which I guess was standardised in 2014
  332. blue so before, you'd have been right indeed
  333. blue this makes sense too for the caching use cache
  334. blue use case*
  335. dreamreal No, I'd have been WRONG, because I was suggesting that the behavior was SUPPOSED to be not to supply a body but that it didn't really matter, when the spec says compliance actually means something
  336. dreamreal it still gets ignored a lot but that's not the point
  337. blue btw, interestingly, GET is the other way around: it must not have a body
  338. dreamreal wait what
  339. dreamreal GET ... the whole purpose is to get the body, o?
  340. dreamreal no?
  341. blue the request
  342. blue the body must be null
  343. dreamreal HEAD - headers, no body.. OH
  344. dreamreal right, sorry, you're talking ingress
  345. blue you're talking about response
  346. dreamreal right
  347. blue so GET requests must not have a body, whilst HEAD responses must also not have a body
  348. blue and I assume, HEAD requests must also not have a body
  349. blue since "otherwise identical"
  350. dreamreal yeah
  351. blue the nevet algorithm can still be lazy, dreamreal
  352. blue it can try for a HEAD request first
  353. blue the golden path is the server supporting it
  354. dreamreal HEAD was *me*, not nevet
  355. dreamreal nevet uses GET
  356. blue good
  357. dreamreal HEAD was me going "what does this even respond with"
  358. * nevet joined #nevet
  359. * 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/streampack
  360. dreamreal version
  361. nevet nevet 1.0 | b3a39e4 (main) | Built 2026-02-27 09:05:20 EST
  362. dreamreal safecracker
  363. bot [jottinger/bytecode.news] New PR #123: Adding safecracker game - https://github.com/jottinger/bytecode.news/pull/123
  364. dreamreal hmm
  365. dreamreal hangman
  366. nevet Hangman: _ _ _ _ _ _ _ _ _ (6/6 lives) -- Use 'hangman <letter>' to guess, 'hangman solve <word>' to solve.
  367. dreamreal hangman a
  368. nevet Hangman: _ _ _ _ _ _ _ _ _ (5/6 lives, guessed: a) -- No 'a'. 5 lives left.
  369. dreamreal hangman r
  370. nevet Hangman: _ _ _ _ _ _ _ _ _ (4/6 lives, guessed: a, r) -- No 'r'. 4 lives left.
  371. dreamreal hangman s
  372. nevet Hangman: _ _ _ _ _ s _ _ _ (4/6 lives, guessed: a, r, s) -- 's' is in the word!
  373. dreamreal hangman t
  374. nevet Hangman: _ _ _ _ _ s _ _ _ (3/6 lives, guessed: a, r, s, t) -- No 't'. 3 lives left.
  375. dreamreal hangman l
  376. nevet Hangman: l _ _ _ _ s _ _ _ (3/6 lives, guessed: a, l, r, s, t) -- 'l' is in the word!
  377. dreamreal hangman n
  378. nevet Hangman: l _ _ _ _ s _ n _ (3/6 lives, guessed: a, l, n, r, s, t) -- 'n' is in the word!
  379. dreamreal hangman g
  380. nevet Hangman: l _ _ _ _ s _ n _ (2/6 lives, guessed: a, g, l, n, r, s, t) -- No 'g'. 2 lives left.
  381. dreamreal hangman o
  382. nevet Hangman: l _ _ o _ s _ n _ (2/6 lives, guessed: a, g, l, n, o, r, s, t) -- 'o' is in the word!
  383. dreamreal hangman i
  384. nevet Hangman: l i _ o _ s i n _ (2/6 lives, guessed: a, g, i, l, n, o, r, s, t) -- 'i' is in the word!
  385. dreamreal hangman p
  386. nevet Hangman: l i _ o _ s i n _ (1/6 lives, guessed: a, g, i, l, n, o, p, r, s, t) -- No 'p'. 1 life left.
  387. dreamreal hangman m
  388. nevet Hangman: l i m o _ s i n _ (1/6 lives, guessed: a, g, i, l, m, n, o, p, r, s, t) -- 'm' is in the word!
  389. dreamreal hangman u
  390. nevet Hangman: l i m o u s i n _ (1/6 lives, guessed: a, g, i, l, m, n, o, p, r, s, t, u) -- 'u' is in the word!
  391. dreamreal hangman e
  392. nevet You got it! The word was 'limousine'. Use 'hangman' to play again.
  393. dreamreal safecracker
  394. dreamreal hrm
  395. * nevet joined #nevet
  396. * 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/streampack
  397. dreamreal grrr, gotta figure out what's going on there
  398. dreamreal but have other things I need to do
  399. * nevet joined #nevet
  400. * 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/streampack
  401. dreamreal safecracker
  402. nevet safecracker pattern: . . . . Good luck, players! (5:00 to go!)
  403. dreamreal pffft there it goes!
  404. dreamreal safecracker 1 2 3 4
  405. nevet safecracker result for dreamreal: < < < < (4:46 to go!)
  406. dreamreal safecracker 5 5 5 5
  407. nevet safecracker result for dreamreal: < < = < (4:37 to go!)
  408. bot Safecracker: 4:29 remaining!
  409. dreamreal safecracker 7 7 5 7
  410. nevet safecracker result for dreamreal: > < = = (4:14 to go!)
  411. dreamreal safecracker 8 6 5 7
  412. nevet safecracker result for dreamreal: > < = = (4:05 to go!)
  413. bot Safecracker: 3:58 remaining!
  414. dreamreal safecracker 9 8 5 7
  415. nevet safecracker result for dreamreal: > = = = (3:57 to go!)
  416. dreamreal safecracker 0 8 5 7
  417. nevet safecracker result for dreamreal: < = = = (3:52 to go!)
  418. dreamreal safecracker 2 8 5 7
  419. nevet safecracker result for dreamreal: < = = = (3:36 to go!)
  420. dreamreal safecracker 3 8 5 7
  421. nevet safecracker result for dreamreal: < = = = (3:30 to go!)
  422. bot Safecracker: 3:27 remaining!
  423. dreamreal safecracker 10 8 5 7
  424. nevet Error: Guess must be 4 digits (0-9) separated by spaces. Example: safecracker 3 0 3 0
  425. dreamreal safecracker 9 8 5 7
  426. nevet safecracker result for dreamreal: > = = = (3:20 to go!)
  427. dreamreal safecracker 8 8 5 7
  428. nevet safecracker result for dreamreal: > = = = (3:15 to go!)
  429. dreamreal safecracker 6 8 5 7
  430. nevet dreamreal has broken the code! Way to go, dreamreal!
  431. dreamreal woo I'm the best!
  432. dreamreal safecracker
  433. nevet safecracker pattern: . . . . Good luck, players! (5:00 to go!)
  434. dreamreal (don't play)
  435. bot Safecracker: 4:29 remaining!
  436. bot Safecracker: 3:58 remaining!
  437. bot Safecracker: 3:27 remaining!
  438. bot Safecracker: 2:57 remaining!
  439. bot Safecracker: 2:26 remaining!
  440. bot Safecracker: 1:56 remaining!
  441. bot Safecracker: 1:26 remaining!
  442. bot Safecracker: 0:55 remaining!
  443. bot Safecracker: 0:24 remaining!
  444. bot Time's up! The combination was: 9 6 3 3
  445. dreamreal interesting drift
  446. dreamreal I know why it does it: it calculates the next offset from the timestamp and not the previous offset. Easy to fix.
  447. * nevet joined #nevet
  448. * 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/streampack
  449. bot [jottinger/bytecode.news] New PR #124: feature/98 safecracker game - https://github.com/jottinger/bytecode.news/pull/124
  450. dreamreal safecracker
  451. nevet safecracker pattern: . . . . Good luck, players! (5:00 to go!)
  452. dreamreal again, please don't play
  453. dreamreal karma chronos
  454. nevet chronos has karma of 3.
  455. bot Safecracker: 4:29 remaining!
  456. dreamreal okay, cool. Evertything still runs, the game is just "an additional mechanism waiting for events."
  457. bot Safecracker: 3:59 remaining!
  458. dreamreal drift seems better already.
  459. bot Safecracker: 3:29 remaining!
  460. dreamreal tag ide
  461. nevet Factoids tagged 'ide': eclipse, ide, idea, and netbeans
  462. bot Safecracker: 2:59 remaining!
  463. bot Safecracker: 2:29 remaining!
  464. bot Safecracker: 1:59 remaining!
  465. dreamreal the safecracker isn't even an additional thread: it's actually a filter that watches for events that match a criterion.
  466. bot Safecracker: 1:29 remaining!
  467. dreamreal "i'm going to ignore timer events until a tripwire is hit. Oh, look! There it is! Time notification."
  468. bot Safecracker: 0:59 remaining!
  469. bot Safecracker: 0:29 remaining!
  470. bot Time's up! The combination was: 1 3 4 0
  471. dreamreal Woohoo! Drift fixed.
  472. Chronos dreamreal: Can nevet handle hangman and safecracker being run at the same time?
  473. dreamreal safecracker
  474. nevet safecracker pattern: . . . . Good luck, players! (5:00 to go!)
  475. dreamreal hangman
  476. nevet Hangman: _ _ _ _ _ _ _ _ (6/6 lives) -- Use 'hangman <letter>' to guess, 'hangman solve <word>' to solve.
  477. dreamreal safecracker 2 1 1 2
  478. nevet safecracker result for dreamreal: = < < < (4:49 to go!)
  479. dreamreal hangman a
  480. nevet Hangman: _ _ _ _ _ _ _ _ (5/6 lives, guessed: a) -- No 'a'. 5 lives left.
  481. dreamreal safecracker 2 5 5 5
  482. nevet safecracker result for dreamreal: = > = > (4:36 to go!)
  483. dreamreal ~hangman r
  484. bot Safecracker: 4:28 remaining!
  485. dreamreal ~hangman r
  486. dreamreal hangman r
  487. nevet Hangman: _ _ _ _ _ _ _ _ (4/6 lives, guessed: a, r) -- No 'r'. 4 lives left.
  488. dreamreal You can play too, it's not tied to a single player!
  489. dreamreal But as you can see, yes
  490. Chronos safecracker 2 7 5 8
  491. nevet safecracker result for someone: = > = > (4:00 to go!)
  492. bot Safecracker: 3:58 remaining!
  493. Chronos safecracker 2 8 5 9
  494. nevet safecracker result for someone: = > = > (3:48 to go!)
  495. dreamreal It's ALL an event stream all the way down
  496. Chronos Wait, > means the actual # should be bigger, right?
  497. bot Safecracker: 3:28 remaining!
  498. Chronos safecracker 2 9 5 10
  499. nevet Error: Guess must be 4 digits (0-9) separated by spaces. Example: safecracker 3 0 3 0
  500. bot Safecracker: 2:58 remaining!
  501. dreamreal Wait, where'd the safecracker notifications go
  502. dreamreal safecracker 2 4 5 2
  503. nevet safecracker result for dreamreal: = > = < (2:47 to go!)
  504. dreamreal safecracker 2 8 5 9
  505. nevet safecracker result for dreamreal: = > = > (2:39 to go!)
  506. dreamreal safecracker 2 7 5 8
  507. nevet safecracker result for dreamreal: = > = > (2:33 to go!)
  508. bot Safecracker: 2:28 remaining!
  509. Chronos "safecracker result for someone: = > = > (3:48 to go!)" — for "someone"?
  510. dreamreal safecracker 2 6 5 7
  511. nevet safecracker result for dreamreal: = > = > (2:26 to go!)
  512. dreamreal safecracker 2 4 5 4
  513. nevet safecracker result for dreamreal: = > = = (2:19 to go!)
  514. dreamreal safecracker 2 3 5 4
  515. nevet safecracker result for dreamreal: = > = = (2:15 to go!)
  516. dreamreal safecracker 2 2 5 4
  517. nevet dreamreal has broken the code! Way to go, dreamreal!
  518. dreamreal Hrm
  519. dreamreal hangman s
  520. nevet Hangman: _ _ _ s _ _ _ _ (4/6 lives, guessed: a, r, s) -- 's' is in the word!
  521. dreamreal hangman n
  522. nevet Hangman: _ _ _ s _ _ _ n (4/6 lives, guessed: a, n, r, s) -- 'n' is in the word!
  523. dreamreal hangman e
  524. nevet Hangman: _ _ e s _ _ _ n (4/6 lives, guessed: a, e, n, r, s) -- 'e' is in the word!
  525. Chronos hangman i
  526. nevet Hangman: _ _ e s _ i _ n (4/6 lives, guessed: a, e, i, n, r, s) -- 'i' is in the word!
  527. dreamreal hangman o
  528. nevet Hangman: _ _ e s _ i o n (4/6 lives, guessed: a, e, i, n, o, r, s) -- 'o' is in the word!
  529. dreamreal hangman u
  530. nevet Hangman: _ u e s _ i o n (4/6 lives, guessed: a, e, i, n, o, r, s, u) -- 'u' is in the word!
  531. Chronos hangman question
  532. nevet Error: Unknown hangman command. Use 'hangman' to start, 'hangman <letter>' to guess, or 'hangman solve <word>' to solve.
  533. dreamreal hangman solve question
  534. nevet You got it! The word was 'question'. Use 'hangman' to play again.
  535. Chronos Aww!
  536. dreamreal SUCK it, chronos!
  537. Chronos Robbed!
  538. dreamreal But to answer your question, yes, you can run as many things as a provenance will allow
  539. dreamreal so you can't run two hangman games IN A SINGLE CHANNEL
  540. dreamreal but you could run hangman IN A CHANNEL and in PM
  541. Chronos I had the reverse understanding of < and > in safecracker, but now my brain is fixed.
  542. Chronos dreamreal: Why did nevet refer to me as "someone" instead of "Chronos"?
  543. dreamreal because you don't have an identity in the bot
  544. dreamreal hmm, that's a really good point
  545. dreamreal file an issue, please? Include that exchange (where I'm 'dreamreal' and you're 'someone', if you would)
  546. dreamreal nick derivation is weird because it's actually related to the provenance identity: if you don't have a provenance, you're effectively anonymous to the event system
  547. dreamreal (the job of an ingress provider is literally to format the ingress content for the message system... and assign provenance if possible.)
  548. dreamreal "on IRC, I can match an IRC user to an identity like so... oh, wait, no match? anonymous it is!" ... but it SHOULD be propagating the nick as well
  549. Chronos Thank you; issue created — https://github.com/jottinger/streampack/issues/61
  550. nevet hangman: referred to me as "someone" rather than "Chronos" · Issue #61 · jottinger/streampack
  551. Chronos oops wait, let me expand the example
  552. dreamreal safecracker did too
  553. dreamreal thank you
  554. Chronos updated; that's better
  555. dreamreal you put it on streampack and not bytecode.news, though, didn't you :D
  556. Chronos wait, now it lost our nickxs
  557. Chronos stupid irccloud copy and paste. fixing
  558. Chronos oops wait no
  559. Chronos Sorry. Wife was distracting me on and off. Brain short circuited.
  560. Chronos dreamreal: Wrong place? I can delete and recreate in the right place
  561. dreamreal wives are the WORST!
  562. Chronos Heh!
  563. dreamreal I am working on it, and issues for current nevet go on bytecode.news
  564. dreamreal Okay. let's test something out
  565. dreamreal 21
  566. dreamreal !21 matches
  567. dreamreal 21 matches
  568. nevet A new game of 21 Matches begins! There are 21 matches on the table. Take 1, 2, or 3 matches each turn. Whoever is forced to take the last match loses. Use '21 take <1-3>' to play.
  569. dreamreal Chronos: make a move there please
  570. dreamreal Chronos: ! where are you!
  571. dreamreal Someone make a move here, I need to check something
  572. Chronos https://github.com/jottinger/bytecode.news/issues/125
  573. dreamreal chronos, make a move in 21 please
  574. Chronos 21 take 3
  575. nevet How very predictable. With great confidence, I take 1. There are 17 matches remaining.
  576. Chronos (I am not familiar with this game... leave your opponent with the last match or something?)
  577. dreamreal yeah
  578. Chronos 21 take 3
  579. nevet Fascinating. Without a hint of doubt, I take 1. There are 13 matches remaining.
  580. Chronos 21 take 3
  581. nevet How very predictable. After pretending to think about it, I take 1. There are 9 matches remaining.
  582. Chronos 21 take 3
  583. nevet We might as well be playing rock, paper, scissors! After weighing my many options, I take 1. There are 5 matches remaining.
  584. Chronos 21 take 2
  585. nevet A bold strategy, Cotton! After careful consideration, I take 2. You are left with one match. I claim victory!
  586. Chronos My instinct is this game is over after the first move :)
  587. dreamreal dang you can't even beat a bot
  588. dreamreal oh, it's over before then :D
  589. Chronos Heh!
  590. dreamreal there's no way to win; the code doesn't even have player victory text :D
  591. Chronos Oh, because the player doesn't get to choose who goes first, got it, heh
  592. dreamreal so 21 matches is pretty much the first thing I write after hello world in ANY language
  593. dreamreal the strategy is ALWAYS the same: collect player move, validate, play 4-playermove until there's 1 match left
  594. dreamreal but gives me input mechanics, output mechanics, loops, terminal conditions, etc
  595. * nevet joined #nevet
  596. * 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/streampack
  597. dreamreal hangman
  598. nevet Hangman: _ _ _ _ _ _ _ _ _ (6/6 lives) -- Use 'hangman <letter>' to guess, 'hangman solve <word>' to solve.
  599. dreamreal Chronos: take a guess, please
  600. bot [jottinger/bytecode.news] New issue #125: On IRC, the Hangman game referred to me as "someone" rather than my IRC nick "Chronos" - https://github.com/jottinger/bytecode.news/issues/125
  601. bot [jottinger/bytecode.news] New PR #126: Fixing anonymous user name references for IRC - https://github.com/jottinger/bytecode.news/pull/126
  602. dreamreal grrrr
  603. dreamreal chronos, I HAVE an id in the bot!
  604. dreamreal jreicher: yo!
  605. Chronos hangman e
  606. nevet Hangman: _ _ _ _ e _ _ _ _ (6/6 lives, guessed: e) -- 'e' is in the word!
  607. Chronos hangman a
  608. nevet Hangman: a _ _ _ e _ _ _ _ (6/6 lives, guessed: a, e) -- 'a' is in the word!
  609. Chronos hangman s
  610. nevet Hangman: a _ _ _ e _ _ s _ (6/6 lives, guessed: a, e, s) -- 's' is in the word!
  611. Chronos hangman d
  612. nevet Hangman: a _ _ _ e _ _ s _ (5/6 lives, guessed: a, d, e, s) -- No 'd'. 5 lives left.
  613. Chronos hangman c
  614. nevet Hangman: a _ c _ e _ _ s _ (5/6 lives, guessed: a, c, d, e, s) -- 'c' is in the word!
  615. Chronos hangman l
  616. nevet Hangman: a l c _ e _ _ s _ (5/6 lives, guessed: a, c, d, e, l, s) -- 'l' is in the word!
  617. Chronos hangman h
  618. nevet Hangman: a l c h e _ _ s _ (5/6 lives, guessed: a, c, d, e, h, l, s) -- 'h' is in the word!
  619. Chronos hangman m
  620. nevet Hangman: a l c h e m _ s _ (5/6 lives, guessed: a, c, d, e, h, l, m, s) -- 'm' is in the word!
  621. Chronos hangman i
  622. nevet Hangman: a l c h e m i s _ (5/6 lives, guessed: a, c, d, e, h, i, l, m, s) -- 'i' is in the word!
  623. Chronos hangman t
  624. nevet Chronos got it! The word was 'alchemist'. Use 'hangman' to play again.
  625. dreamreal excellent!
  626. dreamreal safecracker
  627. nevet safecracker pattern: . . . . Good luck, players! (5:00 to go!)
  628. Chronos Only ONE wrong guess. I'm THE MAN.
  629. dreamreal yes, you're the man
  630. Chronos haha
  631. dreamreal now try safecracker
  632. Chronos safecracker 5555
  633. nevet Error: Guess must be 4 digits (0-9) separated by spaces. Example: safecracker 3 0 3 0
  634. Chronos safecracker 5 5 5 5
  635. nevet safecracker result for Chronos: > < > > (4:32 to go!)
  636. bot Safecracker: 4:29 remaining!
  637. dreamreal there we go!
  638. dreamreal hangman
  639. nevet Hangman: _ _ _ _ _ _ _ _ (6/6 lives) -- Use 'hangman <letter>' to guess, 'hangman solve <word>' to solve.
  640. Chronos safecracker 3 7 3 3
  641. nevet safecracker result for Chronos: < = < > (4:10 to go!)
  642. dreamreal hangman solve gauntlet
  643. nevet Zero letters guessed and you nailed it? That's either genius or espionage. The word was 'gauntlet'. Use 'hangman' to play again.
  644. bot Safecracker: 3:59 remaining!
  645. Chronos safecracker 4 7 4 2
  646. nevet safecracker result for Chronos: = = = > (3:45 to go!)
  647. * dreamreal preens a little
  648. Chronos safecracker 4 7 4 1
  649. nevet Chronos has broken the code! Way to go, Chronos!
  650. Chronos dreamreal: haha :)
  651. * blue joined #nevet
  652. dreamreal you got one wrong letter... I got no wrong letters at all. And didn't even need one GUESS.
  653. Chronos Mmmhmmm. ;)
  654. Chronos Elf needs food, badly.
  655. * dreamreal whistles innocently.
  656. dreamreal thanks, bug fixed I think
  657. Chronos (Speaking of Gauntlet)
  658. Chronos Nick stuff looks good. Thanks!
  659. blue dreamreal: I took the freedom to use nevet's config in that primate issue
  660. blue mostly because... that's where I came across the need for the feature
  661. blue I will probably only need BACKEND_NEVET in the primate code; but I might need other stuff like jwt, too
  662. dreamreal yeah?
  663. blue yes, so your comments are highly welcome
  664. dreamreal hah, that's awesome
  665. dreamreal and commented
  666. blue thank you!
  667. dreamreal hopefully it's useful
  668. dreamreal today
  669. nevet Today is Friday, February 27, 2026
  670. dreamreal today hebrew
  671. nevet Today is Friday, 10 Adar, 5786 (Hebrew)
  672. blue dreamreal: yeah, the last open question is mostly for people who might not be comfortable with automatic env loading
  673. blue you MIGHT have an .env file which you can use for.. I dunno, a PRESTEP or something.
  674. blue I can't think of a good reason for it, but also magic is often something people would at least like an escape hatch from
  675. jreicher Oh gosh I should have said anything about the trunk name. I'm sorry. Just call it "trunk". Or "dumbo".
  676. jreicher ^should^shouldn't
  677. jreicher I was just teasing because I didn't think anyone really cared.
  678. jreicher blue: at the risk of restarting an unproductive conversation, I do have a bit of an issue with this: "so you don't care when others make choices for you". That's vague bait. Both "yes" and "no" invalid answers. Other people make choices for us all the time. Sometimes long-dead people. The design of power sockets in every country is an example that comes to mind. It's not reasonable to care about that choice. Or at least not every
  679. jreicher element of it. But some choices, of course we should care about.
  680. blue You don't need to be sorry jreicher, I don't think anyone's hurt
  681. jreicher Well, it's more about the time spent... :)
  682. blue and also, to your point, yes, that's true. my parents made a lot of choices for me. the point was more like, things you can influence. I get dreamreal's position; he just doesn't care either way, so whatever's the current default works for him. He also didn't care when it was 'master'. For me though, it's different: because in the very least, this is unneeded friction that anyone with half a spine should have
  683. blue objected to
  684. blue You can of course don the Zarathustra position that you live on your mountain and nothing really touches you, but in the end everything touches you, that's why I quoted Obama on that. indecision is also a decision, just masked as none
  685. blue if you don't go vote in elections... you're voting for the winner. not caring is not not taking a stance; it's just taking a stance that aligns with the winning stance
  686. jreicher When working in a team I would be sensitive to the possibility that somebody else might be offended about the user of "master", and for that particular project such a person's feelings would give me a reason to change the trunk name even if I continued to be ambivalent about the default. I suspect dreamreal might be the same.
  687. dreamreal yet you can draw up a fight on every last fucking thing in the world that you encounter and MIGHT disagree on, and you have that right, but it's EXHAUSTING and pointless. Fight on the things that matter. This one matters to you? Great! have at it! Every windmill deserves a tilt! ... but not everyone else sees the same dragon or cares, and sometimes that's how it be.
  688. Chronos blue: What extra friction does main cause? (honestly curious)
  689. blue why should you be sensitive though? the word master is ubiquitous in the English language; and at any rate, it does not refer to people here. So whoever is being offended is not doing it in good faith, and should just completely ignored
  690. blue and any rate, offence is given, not taken
  691. dreamreal yet that's a battle that's already been fought in shadowy halls where we do not care who treads
  692. jreicher And take this in an even more cynical direction, I sometimes wonder whether arguing about this in the absence of a real person having real feelings is just performative. I would want to make sure people who argue so vehemently in the absence of hurt feelings are just as principled when there are real feelings at stake.
  693. blue dreamreal: I get it that to YOU it's pointless. I conceded as much. To me it's not pointless though
  694. dreamreal master vs main: I am not offended by either, even though I find slavery as a concept a horror tantamount to rape
  695. dreamreal yes, and I accept that it's not pointless to you
  696. blue dreamreal: that's not the point though, is it? the word 'master' has many uses; master key is hardly related to slavery. monkeypatching the slavery meaning onto a technical tool is dishonest at best, and downright evil otherwise
  697. dreamreal jreicher: honestly, I think the whole master/slave thing was people desperate for a win in any forum in which they could get it, and in any ral forum they're utterly ignored
  698. dreamreal any real forum, though
  699. dreamreal these people are not and were not winners
  700. blue jreicher: this is not cynical at all. Not one living being is actually offended by the use of the term 'master' to name a technical aspect of a tool. Anyone who contends otherwise should be classified as certifiable
  701. dreamreal "Let me show you how much I care by caring BALLS TO THE WALL about stuff that was actually irrelevant"
  702. Chronos My wife and I bought a new house last year; while searching, we noticed that "master bedroom" had a new name, "owner suite." Our realtor told us the change was because "master" was offensive... but that it turned out "owner" is also offensive, so now it's changing to "primary bedroom."
  703. dreamreal hahahahahahaha
  704. dreamreal of course, realtors are also the idiots of the white collar world
  705. dreamreal if there are any realtors here, I'm sorry, I insulted you directly and you were to D U M B to notice
  706. blue the reason I don't flow with the "why do you care" argument is that it's a known woke tactic; under the guise of it, substantive changes are made to the language and thus to reality
  707. Chronos blue: The crazy woke people ended up getting spanked very hard for their crazy wokeness, in the 2024 U.S. elections.
  708. blue the more interesting question to me is "why don't you care?"
  709. dreamreal well.. in reality, reality don't change
  710. Chronos I keep telling people that Republicans didn't win in 2024; rather, Democrats lost, for getting so deep into Crazyville.
  711. blue dreamreal: I have long believed that. but actually one thing leftists get right is that language does affect our thinking. it doesn't change reality per se, but it does strongly affect our perception of it, which matters greatly
  712. dreamreal and the democrats are getting worse. I hate that, really: I despise the Democrats but we need a viable opposition party
  713. dreamreal I just don't know what you'd call it such that it attracted the sane democrats
  714. dreamreal they just threw away this election cycle and the next, assuming the republicans have the brains god gave retarded gnats
  715. Chronos I think it's okay — *good*, even — to be woke. But not crazy woke.
  716. dreamreal man, that term is so overloaded
  717. Chronos dreamreal: Are the Democrats getting worse? Or have they improved some, since Trump was elected?
  718. dreamreal in most senses preceding the last ten years, I'm very woke
  719. dreamreal Chronos: did you see the SOTU?
  720. dreamreal they basically pissed away every american patriot
  721. Chronos dreamreal: I did not. My assumption is that it would be mostly Trump boasting, and I've already heard a few lifetimes worth of his boasting.
  722. dreamreal every democrat who went "man, I don't like the GOP, but at least I love my country" got spat on
  723. jreicher blue: what's the "missing workflow" you were talking about? issues=branches, you said
  724. Chronos dreamreal: What did they (the democrats) do (or not do)?
  725. dreamreal he trolled them and they fell for it hook, line, sinker, rudder, propeller, keel, ballast, anchor, mast, sail, and dock
  726. blue jreicher: I was mostly referring to the fact I'd like to see an issue-based workflow, and not artifically separate PRs and issues
  727. dreamreal "stand up if you represent american citizens first" -- nope. "stand up and honor the mother of this murdered ukrainian girl" -- nope. "Let's clap for the hockey team!" -- nope.
  728. dreamreal just oevr and over and over again.
  729. dreamreal Simple shibboleths... and they blew every one of them they could.
  730. dreamreal were they shibboleths? Of course they were. But shibboleths are easy: all you have to do is perform them!
  731. blue it's funny how they can't just come out in favour of no men in women's sports. this is 101 sanity
  732. Chronos dreamreal: Trump literally said "stand up if you represent american citizens first" and republicans stood up while no democrats did..?
  733. dreamreal "Use a sibilant S, or you're an alien!" "sssss." "Okay, you're one of us."
  734. blue they're too afraid of their own woke minibase, dreamreal :P
  735. dreamreal Chronos: yes
  736. dreamreal I don't know about NO democrats - I think a few did
  737. dreamreal fetterman, at least one other
  738. blue fetterman's not here
  739. blue he's in andromeda
  740. blue that doesn't count, regrettably
  741. Chronos dreamreal: I assume it's because Democrats don't believe Americans should come before immigrants, or something to that effect?
  742. blue the joke still holds though that the only democrat with a brains is... brain-damaged
  743. dreamreal Chronos: *illegal* immigrants. "Do you represent illegals first, or american citizens?"
  744. dreamreal That's the formation.
  745. blue wait, they didn't stand up for that?
  746. blue WHY?
  747. blue that's like the total baseline
  748. jreicher Sorry, I'm a bit distracted. My partner is a little devastated her hamentaschen experienced side fall in the oven.
  749. dreamreal To congress. People whose oath of office is TO THE CONSTITUTION.
  750. dreamreal I need to get some of those
  751. blue jreicher: oh wow, damn it!
  752. dreamreal the local stores have crap like prunes
  753. Chronos dreamreal: I guess I respect them for sticking by their morals (misguided as they may be).
  754. dreamreal I guess I'm lucky that they HAVE hamantaschen
  755. dreamreal Chronos: their morals shoudl be to defend the constitution
  756. Chronos Regarding clapping for the hockey team; bringing that up just seems... juvenile? I care about the hockey team at least as much as they care about *me*.
  757. blue dreamreal: you know how they're call in eretz hakodesh?
  758. dreamreal if their morals say "every human is equal before the constitution" then their morals are wrong
  759. blue called*
  760. dreamreal blue: oh no
  761. dreamreal what
  762. blue haman's ears
  763. dreamreal Chronos: it's just tribal signalling but the tribe here is AMERICA
  764. blue dreamreal: welp, the constitution is for americans, not for illegals
  765. dreamreal and as jingoistic as that sounds, jingoism in SPORTS is a different thing than jingoism in politics
  766. dreamreal blue: our constitution addresses all humans
  767. Chronos dreamreal: Even if they believe what they're peddling — and I think they do — it seems painfully obvious to me their tactics are piss poor.
  768. dreamreal but citizens have representation aliens do not
  769. blue dreamreal: is it though? I sincerely doubt that -- even if that's the interpretation of SCOTUS
  770. Chronos dreamreal: Yeah, I just don't give a shit about the U.S. men's hockey team. Sorry. <shrug>
  771. Chronos Not one little tiny shit.
  772. Chronos But then, I never got the whole sports thing.
  773. dreamreal blue: no, there's a difference in how the constitution refers to people vs citizens
  774. dreamreal Chronos: well, it comes down to "our side" vs "their side"
  775. Chronos People going absolutely bananas over "their team," when it's not even really "their team," just a bunch of strangers from far away who literally don't give a damn about them.
  776. blue dreamreal: yes I get that, but it's not a meaningful difference. the constitution applies on american soil or to american citizens, which is it then?
  777. dreamreal in sports, it's fully okay to go "hey, we won, they did not" even if the sport is irrelevant
  778. dreamreal blue: yes
  779. dreamreal it applies to both
  780. Chronos dreamreal: Except "we" did not, in fact, win...
  781. dreamreal an american citizen is defended by the constitution, no matter where they are
  782. dreamreal Chronos: hey, we certainly did if we're 'merican!
  783. dreamreal Our team winned! Theirs didn't!
  784. blue dreamreal: q, an american abroad is protected by the 1st amendment, yes no?
  785. dreamreal We, as citizens, contribute and participate in our olympic representation
  786. dreamreal blue: for american purposes
  787. Chronos Even "my" *local* professional sports teams are, well, not made up of primarily *local* people. The whole sports obsession thing seems utterly bizarre to me.
  788. blue dreamreal: where does it say that in the constitution?
  789. dreamreal if I go to thailand and run down the king, i do not have that protection there
  790. Chronos I'm proud of the U.S. women's hockey team, though, for not accepting Trump's invitation, after he treated them badly.
  791. dreamreal blue: That's a good question
  792. dreamreal Chronos: how did he treat them badly?
  793. dreamreal What did he do?
  794. blue the constitution can't possibly apply outside of american soil. that would imply it has global jurisdiction
  795. dreamreal Chronos: he... invited them to the white house, just like the men's team
  796. blue so the q becomes, if an american citizens is in canada and criticises the govt, can he prosecuted upon returning to us soil?
  797. Chronos dreamreal: He said something less than kind while on the phone with the U.S. men's hockey team. Something about "he'll HAVE to invite the women too." It was just the kind of immature and juvenile "joke" I'd expect from him.
  798. dreamreal Chronos: oh my god
  799. dreamreal I listened to that phone call
  800. dreamreal I understand the sentiment but that was NOT what that call was saying
  801. dreamreal AT ALL
  802. Chronos Hey, stop hacking the POTUS's phone!
  803. dreamreal IT WAS ON TV
  804. Chronos (JOKE)
  805. blue iow, the constitution applies only to americans, so americans are protected from 1st amendment violations anywhere they are, as pertains to the american govt
  806. dreamreal "Imagine the outrage if I don't invite the women's team too" -- cue outrage that he said there'd be outrage if he didn't invite the women's team
  807. blue by extension, foreigners are not protected by that
  808. dreamreal Chronos: people are DESPERATE to hate Trump for everything, which is amusing because there's plenty to despise him for
  809. Chronos dreamreal: Why would he say that?
  810. dreamreal Chronos: it's true!
  811. dreamreal That's why!
  812. dreamreal I mean, is it Trump? Sure. But the interpretation being applied is ENTIRELY partisan
  813. Chronos dreamreal: An adult avoids saying lots of things that are true, because saying them is foolish!
  814. dreamreal I listened to it. It was not putting down the women's team at all. And the men? They were laughing at it, going "two for two!" -- CELEBRATING the womens' win as well
  815. Chronos Why bring it up *at all*?
  816. Chronos What's wrong with him that he mentioned it *at all*?
  817. dreamreal Because it's trump, of course. I thought it was unnecessary - but it's not like some horrible offense like it's being made out to be
  818. blue does anyone even watch women's hockey. I didn't even know it existed until now
  819. Chronos Could *anything* good come from saying it?!
  820. Chronos The man needs to STFU *way* more.
  821. dreamreal Chronos: sure
  822. dreamreal Chronos: he was doing trump things. Mein Gott, think game theory
  823. dreamreal He's a MASTER of simple trolling
  824. blue as long as he ends up bombing iran back to the middle ages...
  825. blue he can say whatever he wants
  826. dreamreal he's a dullard and a fool and an awful person, okay? But he leverages that and gets people to respond EXACTLY how he wants them
  827. Chronos dreamreal: Well, it appears to have had some effect — the women's team turned down his invitation — do you consider this a positive outcome for Trump, or the Republicans, or men, or women?
  828. dreamreal he was laying track for the SOTU for EVERYONE to see. There's no way a moderately stupid Dem wasn't going "oh no, he's going to make this a patriotic thing, because it IS patriotic, and we're gonna have to agree that America won and celebrate it or else we're going to look like TRAITORS. Oh, well. let's look like traitors!"
  829. Chronos I can understanding trolling when it benefits you or your team. I'm just not seeing the benefit to him or his team.
  830. Chronos s/understanding/understand/
  831. dreamreal Are you kididng me?
  832. dreamreal DUDE
  833. dreamreal he just nuked the democrats MULTIPLE TIMES in the SOTU
  834. Chronos dreamreal: Somehow, I don't think he was being that clever, and thinking that far ahead. I think you're giving credit where it's not due — but I suppose it's possible.
  835. dreamreal I mean, I felt HORRIBLE for them
  836. dreamreal for THEM
  837. dreamreal can you imagine getting lapped by THAT moron over and over and over again?
  838. dreamreal Chronos: he does this same thing ALL THE TIME
  839. dreamreal "He's only done this one trick 40X in a row, accidentally every time I'm sure"
  840. Chronos Oh, I don't think modern Democrats have a clever bone in their bodies. They have NO idea how to win a war.
  841. dreamreal he wrote abotu it IN HIS FREAKING BOOK
  842. dreamreal which was ghostwritten, mind, but even so
  843. Chronos Democrats will try to win [unwinnable] battles because it's the moral thing to do, knowing fully well the whole time it'll lose them the entire war.
  844. Chronos Or maybe they don't know.
  845. Chronos (Moral thing to do — according to them.)
  846. dreamreal How is that a moral thing, to say "screw you" to a mother who lost her child?
  847. dreamreal How is it moral to go "oh look, a kid disabled thanks to a truck, screw that kid"
  848. dreamreal how is it MORAL to say "our constituents can pound sand, we want illegal aliens here"
  849. Chronos dreamreal: Morals being subjective; it was the moral thing to do in their minds (I guess?).
  850. dreamreal I mean, that may be their actual mores
  851. dreamreal in which case I say they need to GTFO
  852. dreamreal and trump gave them a chance to display those mores in full view of everyone
  853. dreamreal and they took that chance
  854. dreamreal They'd rather despise trump and make sure everyone KNEW they despise trump, Trump hatred is more important than anything else
  855. dreamreal and if that's your guiding principle, well, okay, cool. You suck. GTFO.
  856. Chronos Don't look at me; I dislike both parties
  857. * Chronos <- moderate
  858. dreamreal I *do not like Trump*. I would not leave him alone in a room with my wife. i respect the office he inhabits, I suppose... and that's as far as it goes.
  859. dreamreal I'm not moderate, I'm a liberal, screw you
  860. blue what makes you a liberal
  861. dreamreal I'm just a liberal in the old sense, not the new "omg puppies and rainbows and mushrooms and WE HATE EVERYTHING"
  862. dreamreal I'm a liberal in the rationalist, flat-sense-of-worth humanism pattern
  863. blue I don't know what it means
  864. dreamreal I'm a classic liberal because I suspect power, focus on dignity, refuse to coerce, and demand fairness. I'm not a liberal in the modern tribal sense.
  865. blue but like, you still have a position on say, abortion, no?
  866. blue is it closer to the D or R party
  867. dreamreal I have a position on most things! And I'm very axiom-driven.
  868. blue I didn't know classic liberal suspected power, I thought classic liberal would be like an assertion of god-given rights or whatever the christians call it
  869. blue life, liberty and the pursuit of happiness, etc.
  870. blue I guess that's the same as what you said?
  871. dreamreal sure.
  872. dreamreal i neither demand nor expect satisfaction along those lines from others. Those things are not theirs to dispense or control. Classic liberal.
  873. Chronos What I like about Republicans is that they're super transparently evil. Benefit rich people? Fuck everyone else? Yep, yep, I like that I understand them to some degree, it means I can better predict their behavior and act accordingly.
  874. blue yeah that's me too. though I don't like the label liberal. there's nothing liberal about it, I'm not 'open to new ideas'
  875. blue I'm still mostly conservative in the sense of conserving things that have proved useful for uh, nearly forever
  876. Chronos What I *dis*like about Democrats is they *really believe* their twisted morality is good and right; they've become deeply religious, which always make me super nervous.
  877. dreamreal See, I'd see both parties as transparently evil at the edges, but the democrats are transparently corrosive as well. Republicans win that one.
  878. blue at least you *have* two parties, dreamreal!
  879. blue here we have a uniparty, and that's it
  880. Chronos At least with Republicans, if I need to, I can pretend to be a Christian, and even start going to some Church, and make all the right noises, and appear to fit in, and not get labeled "domestic terrorist."
  881. dreamreal It's funny, I see a lot more outsiders in the republican party than I do the democratic party
  882. dreamreal the democrats emphasize the ol' rainbow but when you look under the curtains, everyone has to think the same or else
  883. Chronos With Democrats, I have to support some of their insane agendas that hurt me, my family, and me neighbors, like, "Borders are racist."
  884. blue also, elon was not wrong with the idea of the American party. only it's probably never going to happen
  885. Chronos blue: Are you a German citizen?
  886. blue ya, Chronos
  887. blue since... lemma look, 2019
  888. Chronos blue: Where are you originally from? If you don't mind saying.
  889. blue Chronos: Israel
  890. Chronos blue: Why did you decide to move to Germany and become a German citizen?
  891. blue Chronos: because Israel is the next best thing to hell on earth
  892. Chronos Oh! Wow. I had no idea. I thought Israel was very nice, modern, etc.
  893. blue it's probably the only palce in the world that it's 100% good that it exists, and yet it manages to get out the worst in mankind, mostly not through any fault of its own
  894. dreamreal it can be
  895. Chronos Huh. Interesting.
  896. blue Israel was envisioned almost entirely differently than how it was supposed to be. The Holocaust and WWII made it an impossible place, because the human capital that was supposed to drive it got almost completely lost
  897. blue than how it came to be*
  898. dreamreal it's actually a marvel that it exists at all
  899. dreamreal we Jews RAWWWWWWK
  900. blue ya
  901. Chronos Well, it kind of looks like China will become the next superpower, as the U.S. continues its downhill slide.
  902. Chronos Time to cozy up to them!
  903. dreamreal Depends on the democrats, if they can regain power
  904. dreamreal if they can't, the US may be okay
  905. blue so imagine you wanna start a company, you have a bunch of REALLY talented engineers, like I mean supertalent, that for some odd unfathomable reason, no one wants to employ. and then almost just before you get to start working, like 90% of them vanish. and instead, you need to hire 90% completely unqualified idiots who have never done any proper work, in anything
  906. blue so now those idiots start working for you, but they resent you like hell, hate you, and are sure you're the bane of their existence, even though you saved their sorry butts from riding camels all day long to fetch water
  907. Chronos You guys must hate Greta ;)
  908. dreamreal I don't hate anyone that I know of
  909. dreamreal I think she's going to have a hard time in any real world
  910. dreamreal she's been kind of abused by her caretakers
  911. blue anyway, basically that's the story of Israel, as said, impossible
  912. dreamreal her role in society is basically a yapping dog, too small to actually do anything beyond the yapping, until you get close enough that its needle teeth can bite you
  913. blue and also the occassional "jews bad", because why not, why not just focus on climate issues
  914. dreamreal she's going to die unhappy and unloved unless she somehow figures it out for herself, which I doubt she'll do as long as she's enabled as a figurehead
  915. dreamreal but I don't HATE her
  916. blue ya, I don't hate anyone
  917. blue there are exceptions, but they're personal, not political
  918. blue and they definitely don't apply to anyone I've never met
  919. blue greta is mostly in the pity box for me. she was obviously groomed by her parents to be this political puppet with no brains
  920. dreamreal Yeah, there're a few I suppose
  921. dreamreal but I don't know if I've met anyone I'd hate either, buber makes that hard
  922. blue if she were born just 40 years earlier, she'd probably be with a child in a kibbutz :P
  923. dreamreal it's part of why we should reach out to as many people as we can: we should collect personal impressions of everyone around us as much as we're able to tolerate
  924. blue dreamreal: one of the best mapping of a reality is 'a man is a product of his time'. that of course doesn't excuse evil, but it serves to illustrate a lot of behaviour
  925. blue I am, too, a product of my time, and so are you
  926. Chronos dreamreal: What do you think the most concerning things is about Democrats? In terms of which of their polices would be the most harmful to the U.S.
  927. Chronos If you don't mind saying.
  928. dreamreal Chronos: the endless refusal to accept redemption.
  929. jreicher blue: (I'm slowly catching up.) You mean that there should be a correspondence between branches and issues, rather than between branches and "code changes" (whatever that might mean, the ambiguity of which is perhaps what youa re reacting to)
  930. jreicher ?
  931. Chronos dreamreal: Can you elaborate on that?
  932. blue jreicher: ya. for me issues should represent a complete item of work that, when done, can be fast-forwarded as is to master
  933. jreicher Err. FF? (Not the main topic here, but why would FF apply?)
  934. blue because then maintainers can merge to master directly
  935. dreamreal Chronos: the democrats damn - and damnation is permanent. There is no recovery. You said a thing that we interpret TODAY as racist, therefore you are a racist, you are contemptible, you owe endless restitution and can never be redeemed, only a symbol of endless remuneration.
  936. blue iow, it's the issue owner's job to make sure maintainers don't need to rebase. this is more or less how the linux kernel dev works, btw
  937. jreicher blue: you mean without having to resolve conflicts? So you're saying PR submitter should stay ahead of master?
  938. blue jreicher: yes. once you indicate to the maintainer that work is done, it should in at the tip of master, i.e. rebased, by you
  939. jreicher I wouldn't use rebase. There are other ways of staying ahead of master. But I understand what you mean.
  940. blue if there are conflicts, it's your code to resolve them, as the code owner / issue owner
  941. blue it's your job*
  942. jreicher Yep, that's what I thought you meant. You want to save maintainers resolving conflicts with code they are less familiar with than the author.
  943. blue maintainer can focus on pure review
  944. blue yes
  945. dreamreal Chronos: it doesn't matter than you said it 40 years ago, or that everyone around you said the same thing, YOU are racist because it is useful for them for you to be racist and you cannot EVER recover from that. Ever. But you better start paying into the coffers for it. Or else.
  946. blue ^
  947. jreicher OK, so back to the "issue per branch" idea. Are you familiar with the notion of an agile "epic" or "feature"?
  948. dreamreal Chronos: and it's not me saying that because it's happened TO ME - this is the pattern you see in the dominant aspects of the Democratic party. There's your corrosive element... and add to it postmodernism, and what you get is active, corrosive EVIL, and I can't.
  949. blue jreicher: yes, I am. those can be modelled as issues that never use their branches, or as something else
  950. blue in the linux kernel's dev model though, you'd have hierachies
  951. blue an epic 'maintainer' would pull from his issues, and signal to the master maintainer to pull
  952. jreicher blue: OK, so if something is "too big" for one branch, you don't have a problem with it being done across multiple branches that contribute smaller changes to build to the final solution?
  953. blue jreicher: yes, that's no problem. hierarchical issues are fully. not all issue branches must flow directly back onto master
  954. blue fully ok*
  955. jreicher Oh but you would still have a branch for each issue.
  956. blue it's fully ok to create subissues, and have all the subissues flow back to the 'epic'/'feature' issue
  957. blue it's really almost entirely the same as the linux kernel dev system, I'd say
  958. jreicher OK, so looks like there are two different things here. One is the maintainer's view, and the other is the contributor's view. You would want the maintainer to see only one branch, corresponding to the "epic", no matter how large it is, and ahead of master so that there are no conflicts. Right? So nothing partial, and nothing conflicting.
  959. blue yes, pretty much
  960. Chronos dreamreal: Thanks for that explanation. I can't disagree.
  961. blue jreicher: but there could be several epic/feature branches
  962. blue all ready at different times
  963. blue and their maintainers could be different people
  964. dreamreal Well, you should, because my verbiage here is pretty acidic - a register I don't prefer - but I'm annoyed, so that comes through. Sorry about that.The Buber reference was intentional and sincere and entirely relevant.
  965. jreicher It's an interesting idea. I have some sympathy for taking the maintainer's POV like that. But I think contributors should be able to do whatever they like. Branch without issues. Issues without branches. etc.
  966. dreamreal if I could meet greta I would.
  967. jreicher But maybe the keep all that in their own fork
  968. blue jreicher: yes, I understand it. but I also find it highly chaotic. in your typical github repo, you have many issues; and many people randomly sending in PRs. a lot of this work might not be relevant at the time of creation, or end up being wasted, or repeated. issues focus work: especially if they can be first 'accepted' by maintainers, before work is started on them
  969. blue you can still do your own work in your own repo, if you so wish. but you just can't randomly PR it without having it on an issue branch first
  970. jreicher Which again is the maintainer's POV. And that's fine.
  971. jreicher (IMO)
  972. jreicher It's a bit like saying you can write an email in whatever language you choose. It has to be one the recipient can read.
  973. jreicher ^can^can't
  974. jreicher dammit
  975. blue yes
  976. blue in the end, it's about expectation management
  977. blue I personally onyl want to start working on an issue that has been accepted, and where no one else is working on it
  978. blue if the issue's not been accepted, or someone else is working on it.. well, I might be wasting my time
  979. blue using issues as an expectation system mean the maintainer can't really 'complain' later about the method, only about the code
  980. jreicher Mind you, if people want to work in chaotic ways, and you are witness to it but are otherwise unaffected, I often think the best reaction a deep breath, perhaps a little cry, and then leave them to it. You probably have better things to do.
  981. blue means*
  982. blue yes, but also, this creates unnecessary friction. I have a long-standing open PR in my project where someone used AI to generate docs. I don't really want to reject it outright at the moment, because it's a user, but I also am probably not going to merge it. and it is my fault for not having set up the expectation framework properly
  983. blue this situation would be impossible in the issue-based system I just theorised
  984. blue I want to encourage contribution: but at least on my own terms, in some basic acceptance-framework-based way
  985. jreicher Oh I see your concern now. You (also) want to smooth over the relationship between maintainers and contributors.
  986. blue I have no real problem btw even with the fact it was AI-generated. but the PR is so random that it satisfies almost none of what *I* envisioned for this docs section
  987. blue it's *less* work for me to fully reject than work through the problems with the contributor
  988. jreicher This is reminding me of the experience people have submitting to Emacs. They don't always like what the maintainers say.
  989. blue and again, this is my fault for not having communicated intent properly
  990. blue *I* should have defined acceptance criteria for this, and I haven't, and since the since is open, the guy jsut went ahead and sent a PR
  991. blue since the system*
  992. blue I just want to make it clear I don't blame him, it's my fault here, and the fact I can't really set it up technically the way I want to, on github
  993. jreicher Have you asked him what he wants to do in this situation?
  994. jreicher He might be prepared to modify the PR with your feedback
  995. blue I haven't, mostly because this needs a full rewrite, and the code the docs are based is moving too fast right now
  996. blue it's just not ready yet for docs
  997. blue which is one of the reasons I haven't documented it myself, yet
  998. blue if this was strictly issue-based, the guy could have opened an issue: but not done any work on it until it was accepted
  999. blue based on*
  1000. blue since it's my project, there are many 'implicit' things I haven't done: I know I need to do it, but I'm also not opening an issue for every little thing, because I don't want to use the issue tracker as a reminder system
  1001. blue things that are still in that cosy place of, needs to be done, but too far away that I don't even want to open an issue about it, just stay in brain or local text file. they're so far away I can't even commit to a shape
  1002. blue heck, I don't even know if it's one or many shapes, that's how far it is
  1003. blue I can barely discern it in the distance myself
  1004. blue I don't want the issue tracker to become a graveyard of "this is something I wanna do at some point in the next decade"
  1005. blue because I could fill it to the brim with THAT kind of quality
  1006. jreicher It might be worth talking to them anyway. It's not about what might happen next, but about your concerns for their expectations and understanding of what they can do.
  1007. jreicher And gives you "practice" at the relationship (since you seem to be interested in this)
  1008. blue yeah, I might do that
  1009. blue another thing, jreicher, that I'm missing in gh are proper broads. they have like a 'projects' feature that yet a third look into what the project is doing. I'd very much prefer a broad kanban view of the issues that tells me, ok, those are the long-term things dreamreal is working on for nevet, and this is where the project is heading. instead there's this weird 'projects' feature that is totally parve
  1010. blue proper boards*
  1011. jreicher That's an interesting idea. I wonder if any forges have that.
  1012. blue there used to be a website that did it super nicely, it was called pivotaltracker. not far from today's trello, but much better organised. let me see if I can find a screenshot of how it looked like
  1013. * jreicher prepares himself for the first sight of Netscape he's seen in years
  1014. blue it's not that old, just like 5 years in the past or so
  1015. jreicher I was joking. :p
  1016. blue https://startupstash.com/wp-content/uploads/2020/04/pivotaltracker_platform_1.png
  1017. jreicher Nice
  1018. blue I *really* liked how condensed it was, and you have a nice overview of where a project was at
  1019. jreicher Serentiy EHS? That the one?
  1020. blue I think that's the name of the project shown. the thing itself was called pivotaltracker
  1021. blue I think it got sold off or something
  1022. jreicher Trying to find what it is now. Not easy.
  1023. blue I get this: https://www.planview.com/products-solutions/products/hub/integrations/pivotaltracker/
  1024. nevet PivotalTracker - Planview
  1025. blue I think they bought it, and it's something else now
  1026. blue or maybe that's just an intergration for it
  1027. blue I have no idea; I don't think the tool is available anymore, unfortunately
  1028. blue https://news.ycombinator.com/item?id=41591622
  1029. nevet Pivotal Tracker will shut down | Hacker News
  1030. blue apparently EOL'd in Sept 2024
  1031. * blue says kaddish
  1032. jreicher Chronos: I don't think it's a given that China will become the next superpower. I suspect the governance structure they have is not sustainable. Too much depends on the personal competence of Xi Jinping, and nobody lives forever. One of democracy's biggest strengths is that the system is "designed" to survive changes in people, constantly trying to cultivate competent replacements.
  1033. jreicher dreamreal: what you call "damnation" would be called "cancel culture" over here.