I, too, find myself wondering why this seems to be such an intractable problem. Maybe it's just misaligned incentives? That is, the phone companies really only care as much as they need to in order to prevent you leaving for another phone company.
From a technical perspective, it doesn't seem to be _that_ difficult: it seems like KYC but for anyone who wants automated access to telephone networks. I know there are some existing efforts there that are more technically comprehensive than that (SHAKEN/STIR), but I don't know where they're at in terms of adoption/rollout.
In other ecosystems, I could see how this could be a problem, but I don’t think I’ve ever had a problem with a Go upgrade.
What’re the actual, practical results of a package pushing you towards a higher go version that you wouldn’t otherwise have adopted right away? Why is this actually important to avoid beyond “don’t tell me what to do”?
Sure, but that doesn't address GP's argument, which I _think_ is "there's a time and a place for those criticisms, and _literally every time emacs is brought up in a public forum_ ain't it"
I hope it's not my comment(s) that triggered your anger, still, please accept my apology.
> Stallman deserves to be criticized for his own positions.
I fully agree. I'm just asking to try to decouple that from Emacs.
> because i like his software
Can we agree that Emacs is no longer "his software" and it stopped being that long ago? Governance and ownership have separated from authorship, right? The point is - when the scandals got out, we didn't circle the wagons. If the tool and the person were tightly coupled, you'd expect the community to defend him. We didn't. The separation was/is real, not just rhetorical.
Sure, yes, GNU/Emacs is still officially an FSF project, and the FSF is still Stallman's institutional creation, even if he's been sidelined. His philosophical fingerprints - GPL, copyleft, free software ideology as distinct from open source - are baked into the project's DNA in ways that aren't cosmetic. So there's a version of "his software" that's genuinely hard to dislodge. I'm not trying to argue that or erase his authorship, no.
But can we still find a way to deal with it differently? Say:
- Wagner was viciously antisemitic; the music is still the music
- Caravaggio was violent, possibly a murderer, yet painted some of the most incredible art pieces
- Heidegger was a Nazi sympathizer yet produced genuinely influential philosophy
People are complex creatures, sometimes we need to decouple the evaluation of the contribution from the evaluation of the person. I just want to avoid circles like: "using/praising Emacs is bad because Stallman is bad, therefore his creations are tainted".
I'm not defending Stallman or any of his behavior (good or bad), I'm defending something the community itself largely built, maintained, and steered. When people outside of the loop hear these things together, it hurts me personally - the conflation feels like a category error aimed at something I personally have a long relationship with.
The annoying thing about these whole thing is that you threw the Stallman material probably without even thinking about any of that. It's rhetorical ammunition, not a serious argument. You're not really engaging with what Emacs is to its users - just reaching for the most socially radioactive association available to win a point. And I'm now having to "defend" against an argument that was never made in good faith to begin with.
Which is exhausting in a particular way - not because the argument is hard, but because you have to take it seriously even when it wasn't offered seriously.
> it makes history a lie that eventually collapses under its own weight in large teams
Can you please elaborate on this? I've seen this argument from others as well, but nobody has ever been able to articulate what that actually looks like and why rebasing branches specifically is to blame.
My perspective: whatever happens to the commit history on your non-`main` branch is your business. I don't care about the specifics until your work is merged into a shared branch that we all understand to be the canonical representation of the software we're working on.
I'm not the GP, but I've seen "rebase lies" in the wild.
Suppose a file contains a list of unique strings, one by line. A commit on a feature branch adds an element to the list. Later on, the branch is rebased on the main branch and pushed.
But the main branch had added the same element at another position in the list. Since there was a wide gap between the two positions, there was no conflict in Git's rebase. So the commit in the feature branch breaks the unicity constraint of the list.
For someone that pulled the feature branch, the commit seems stupid. But initial commit was fine, and the final (rebased) commit is a lie: nobody created a duplicate item.
Thanks for that. I'm definitely familiar with that kind of situation, but what I'm not seeing is how that leads to history "collapsing under its own weight" in larger teams. That seems like a relatively straightforward rebase error that is easily corrected. (Also, if it is important for that list to only include unique items and you were able to merge it anyway, maybe that also reveals a gap in the test suite?)
“I want this feature” and “I want this feature to not exist” are fundamentally incompatible viewpoints when applied to any given feature. It seems like adding that feature and making it opt-in is a good middle ground. The people that want it can have it and the people who don’t want it can pretend it doesn’t exist. This outcome seems like the result of listening to all viewpoints, so I’m not sure what problem you’re trying to point out.
This is the second time I've seen somebody use the word "clankers" in the last couple days to refer to AI. Is that a thing now? Where'd that come from?
Gonna be honest, it has taken away from the message both times I've seen it. It feels a bit like you're LARPing your favorite humans vs robots tv show.
We have been rewatching Clone Wars as a family, and I, for one, find this terminology hilarious given the use of it in the series towards the separatist droids.
> In practice, pornography showing genitalia and sexual acts is not ipso facto obscene according to the Miller test.
I'm not sure you can make the statement that pornographic materials aren't protected speech. I don't think you can make the statement that they are though.
In practice it is protected, but as the law is written it's hard to say how or why. Pure pornography with penetrative sex, by any reasonable definition, "depicts or describes, in a patently offensive way, sexual conduct" and "lacks serious literary, artistic, political, or scientific value". And it's pretty clear that most pornography is intended to "appeal to the prurient interest". So it's really only protected because juries refuse to convict, meaning it's only protected if the defendant is seen as likable.
Why Does “literary, artistic, political, or scientific value” matter. And who gets to judge that? I can arbitrary decide it does hold artistic value to me. If at least one person finds it is valuable why should it be banned?
I understand you’re simply quoting the Miller Test but the entire concept of obscenity is ridiculous. Speech is speech. The Constitution says nothing about obscenity.
You're missing that the Yubikey Nano exists. You just leave it in the port. You don't need to remove it - you have to physically touch it to activate it in the same way that you'd have to touch the Touch ID sensor.
Same way? That thing isn't biometric, how is this protecting me in the same way? That's just ridiculous. Yubikey Nano is a "thing you have", TouchID is a "thing you are".
Well, okay, you can select two specific words to fuel your apparent outrage if you'd like, but if you actually read the entire sentence, you'll see that there is some critical context that you're missing: "you have to physically touch it to activate it in the same way that you'd have to touch the Touch ID sensor."
I did not claim that it was the same security scheme or that it's biometric or anything like that. I did claim that you have to physically touch it to activate it.
Edit to add:
re 'Yubikey Nano is a "thing you have", TouchID is a "thing you are".', I would argue that your finger is in fact a thing you have. The loss of a finger might change a little of who you are depending on the circumstances that led to you losing said finger, but these both fall into "thing you have" territory for me. I don't think it's wise to consider Touch ID much more than that, personally.
What the other person is trying to explain to you is that your Yubikey solution fails the following scenario: you leave your laptop at school.
With TouchID, nobody can unlock it. With a Yubikey in the USB-C port, anyone could unlock it.
That's why macOS Yubikey login integration requires you to type in a PIN on the lock screen. At which point it's no different from typing in a password.
Dude, "thing you have" and "thing you are" are things that are already defined in context of authorization and MFA. You can't "argue" that just because it fits your narrative.
Honestly, just white knighting for one of my favorite developers and biggest inspirations.
Someone lying about the pseudo randomization of the hand drawn efforts to make it seem entirely algorithmically generated rubs me really wrong, especially when that dev has publicly broadcast the reasoning of the decision to eschew procedurally generated mines.
I think that's what I was confused about: I don't see the lie in the comments above. optionalsquid said "[...]did try to implement procedural generation for the mines, but ended up scrapping it"
bombcar said "They're quasi-generated with random elements and fixed elements - similarly to early Diablo procedural generation." (which is true - you confirmed as much in the very next comment - "The levels are all hand drawn, not generated by an algorithm, even if they’re shuffled.". That's all early Diablo was doing.)
"Quasi-generated" seems like an appropriate descriptor here - stringing together level building blocks algorithmically is still "generating" a level in a sense. You're right - it's not correct to say that they were generated in the same way that an LLM generates things, but a) nobody claimed that and b) there is an undeniable element of procedural generation here.
From a technical perspective, it doesn't seem to be _that_ difficult: it seems like KYC but for anyone who wants automated access to telephone networks. I know there are some existing efforts there that are more technically comprehensive than that (SHAKEN/STIR), but I don't know where they're at in terms of adoption/rollout.
reply