Hacker Newsnew | past | comments | ask | show | jobs | submit | thelopa's commentslogin

I’ve been running Linux for ~20 years. Proton is, without a doubt, a huge leap forward for the ecosystem. I stopped dual booting Windows for games ~5 years ago and haven’t looked back. It’s positively wild to me that native Linux builds for games are often harder to get working than just using proton and the game’s windows build.


They needed to compile the kernel because they were using the full kernel. The main package repository (and thus the main binary caches) only include a de-blobbed version of the kernel. To get standard Linux including all the blobs, you need to use the “nonguix” package repository. The nonguix folks do have a binary cache server, but using it during install is slightly annoying. I currently have a guix vm compiling Linux for exactly this reason. Since you likely won’t be installing much else from nonguix during system setup, you only need to compile the kernel and other bloby things you choose to include (e.g. firmware, microcode).


Isn't an hour a long time for a kernel compile?


I would argue that you should do something similar in Haskell, too. It would ensure that practically everything accessing the allow list fails to compile unless it had been adapted to the new model. Haskell’s strength is the compiler and its ability to pedantically enforce type errors. Use it! Let it help you!


And yet, Elon has decided that a term used in academic medical research for nearly a century, “cisgender”, is a slur and banned from the platform. Funny how he wants to protect objectionable speech that aligns with his political view while restricting “objectionable” speech that doesn’t.


From Wikipedia, while the concept has been discussed since at least 1914 the actual term cisgender has apparently only been used since 1994: https://en.wikipedia.org/wiki/Cisgender


Cisgender is recent, but it’s also primarily used to serve as the counter to transgender. To understand “cisgender”, it’s useful to study the history of “transgender”. Transgender was introduced as a term because it encompassed a larger group of people and avoided the stigma surrounding “transsexual”. Transsexual has a history dating back about a hundred years. Since “trans-“ and “cis-“ are antonym prefixes, once you have transsexual, you have cissexual. For the purposes of Elon’s rule, it doesn’t matter whether it’s CISsexual or CISgender, he objects to “cis”.


One reason why many people, particularly feminist women, find "cisgender" a disagreeable term is because it's a linguistic concession that makes it more difficult to argue for the rights of actual female women, as it implicitly redefines "woman" to include males and "man" to include females.


Disagreeing with a particular taxonomic way of describing different types of people simply because it makes it hard to advance your political beliefs does not mean the words involved in that taxonomy are slurs. “Slur” has a particular meaning, and it isn’t “makes it hard for me to achieve my political goals”.


The Korean approach is still wrong, arguably. If you want to include the totality of the life of the baby, the next normal stopping point would be conception. That would make the child ~9 months old, not 1 year.


In practice, you normally don't know the exact date of conception, you can only roughly estimate, but any estimate is likely to be a few days out. There are exceptions – e.g. IVF, or the parents know they only did it once and remember the exact date they did it on (but their memories may be fallible, etc). Birth is better because (in developed countries where babies are normally born in hospital) the bureaucracy almost always knows the exact date every person was born – in many cases even the time of day, not that anyone really cares about that.

Plus, any proposal like that is inevitably going to get mixed up with the politics of abortion, which is another reason why it won't happen.


Conception as a result of sex can take place up to one week after the act, even if it only happened once.


A error margin of +/- 7 days still beats a error of 9 months.


The Korean approach does not account for preconception well at all. It counts the number of calendar years a person has been present for postpartum.

A person's Korean age starts at 1 sal, and increments at New Years. A baby could be born on December and be 2 sal by January. A baby born in January would be 1 sal until next year, and be considered 1 sal younger than the December baby, even though they were only born 1 month apart. Everyone born in the same calendar year is in the same age cohort.


They could have fixed just that.


I disable password authentication and use fail2ban. It's unlikely they will be able to brute force my key, but no server is perfect. sshd might be compromised one day. I’d rather have an extra layer of defense just in case.


It's impossible they will brute force your key if you have a decent length.

While I'm sure it is possible for some (mainly government) actors to brute force keys, I'm also sure these do not include the same low-hanging-fruit vandals blasting brute force attacks. And I'm also pretty sure you're not one of the select targets of these highly advanced actors.

A vulnerability in sshd is indeed possible and happens once in a while. Fail2Ban won't stop this though because a known exploit will let them through on the first attempt.

I personally view fail2ban more as nuisance control when it comes to SSH with password auth disabled. Minimizing the log crap, the wasted CPU resources by the failed handshakes. It's not really a security protection in that scenario. In other cases (e.g. web logins where passwords must be used) it of course is.


Unless the maintainer of your distro's ssh package accidentally introduces an error that reduces the number of possible keys to, say - 32,767 total possible keys.[1] That's a brute-forcible number of keys that fail2ban would help mitigate.

(1: https://research.swtch.com/openssl)


Or the NSA subverts a cryptographic standard in order to produce predictable seeds for cryptographic random-number generators that are used to produce private keys. [1]

(1: https://www.bbc.com/news/technology-24048343 )


INCONCEIVABLE!

You keep using that word. I do not think it means what you think it means.


Many of the str functions in the C standard library assume a nul terminator.


Yes, but aside from string literals pointed out by a sibling comment, nothing in the language itself dictates this convention. The C library could be augmented with functions which expect strings structured in other ways.


> nothing in the language itself dictates this convention.

String literals are nul-terminated, e.g.: "foo"[3] == '\0'


I’ve used Mac’s at my job for about 10 years + a few years of personal use before that. I’ve had ample time to get used to the Mac workflow.

macOS’s approach only works nicely if you expect to have one simultaneous task per app OR you don’t expect to switch between apps. Once you have multiple simultaneous tasks in multiple apps, it becomes really cumbersome to use command tab. My job tends to involve exactly the pattern of window switching that macOS isn’t made for.


I've been using two monitors for a long time at this point, which might be part of why the macOS workflow works for me. I make heavy usage of virtual desktops, with "primary" apps going on desktops on the main monitor and secondary/auxiliary apps going on the secondary monitor. With this I can mix and match entire sets of windows very quickly and efficiently and very rarely manually manage windows.


Some models of the Turing machine have an infinite tape in only one direction. Some also don’t require every state to have an exhaustive set of transitions. Those models generally consider going off the end of the tape or failing to find a transition to be a halting state.


The paper makes explicit how this is dealt with:

> For the purposes of defining the halting problem H, one should specify whether it officially counts as halting or not if the head should happen to fall off the left edge of the tape. Although the truth of the main theorem will not depend on these details, provided we adopt a uniform answer, let us be definite and regard such computations as having not officially halted, as the halt state was not reached.


It’s unclear to me why restricting ourselves to that model is useful here


Changing the model wouldn't change anything. A turing machine is equivalent to any computational machine you want to put in there. It doesn't matter what the machine is. The turing machine is the goto because it was first used for them.

Any other machine that can simulate a turing machine can simulate failing in those same ways. You can't escape the problems of turing completeness without losing it.


It does matter, the second and last sentence of the abstract is "The proof is sensitive to the particular computational models."


It’s the simplest model which can simulate all useful models of computation we have so far.

So, if you want to prove something about the limits of computation, a Turing machine is usually the right choice.


I think interaction nets [0] is actually a simpler model and can simulate Turing Machine efficiently. I wish courses in Computability/Complexity theory would be taught in interaction nets instead of Turing Machines as the program written would be so much nicer and compose easily. It also has real-life uses in compiling functional languages. [1]

[0]: https://en.wikipedia.org/wiki/Interaction_nets [1]: https://github.com/HigherOrderCO/HVM


How is this simpler?

It seems to me a more complex lambda calculus.


Symmetric interaction combinators (an instance of interaction nets like 2-state 3-symbol Turing machine is a particular type of Turing Machine) only has 3 agents and 3 rewriting rules. This makes it about as simple as lambda calculus with 3 possible terms (variable, application, and abstraction) and α-equivalence, β-reduction, and η-reduction. The advantage of interaction nets is that each rewriting rule is local and "atomic" unlike subsitution step in β-reduction which can take arbitrarily long time as it is defined recursively.


I was referring to the instantiation of a TM as having a one sided tape.


It is true that some models define halting that way, but in this paper they explicitly do not.


This narrative about trans shooters is disconnected from reality. If you take every trans shooter in the last decade, you get less than 10… out of thousands. For context, last year America has nearly 700 mass shootings. Trans people are actually under represented in mass shootings. Estimates put trans people at up to 1% of the population. We would naively expect 7 shooters last year to be trans, but none were. Saying that the recent shooter is part of a trend of transgender shooters requires outright ignoring all evidence to the contrary.


The desperation to argue against a straw man is real. If trans people went from no school shootings to one in 2020 and one in 2023 there may or may not be a "trend" but it's still worth finding out why that is happening.

Edit:

re pupptailwags: Yes we should be examining whenever people are engaging in violence, factors behind that happening. I'm quite certain, unlike assertion made below, that people indeed have studied the qualities of males in particular engaging in this kind of violence.

rethelopa: I was replying to a comment talking about why something (male disposition to this kind of violence) hadn't been studied; it has.

[note I'm rate limited, which is reason for replying this way]


I’m assuming I’m the “assertion made below”. I made no such claim. Let me rephrase it.

There have been 8 mass shootings in America in the last 7 days. No one was running to twitter to speculate about their causes. No politicians were raising concerns about troubling trends. The shootings were going completely unremarked on in national politics… until a shooter happened to be trans.

If you want to speculate that commentators and politicians are giving the other incidents the same attention, we would literally never hear the end of it. On average, almost 2 mass shootings happen per day. But, for some reason, those incidents weren’t given national attention. Curious.


We didn't apply this standard to all men when we went from no school shootings to one school shooting in 1840. I don't see a reason why we should apply it to another gender.


You optimize for the common case, not the uncommon one. Shouldn’t we figure out why shootings in general are happening rather than fixating on a specific case because it involved an unpopular minority group?


I think searching for a general common solution is precisely why we are getting nowhere. It may be there are some "unpopular" opinions that turn out to be factors. Many small pieces make a large one, and important hints often come in unexpected places.


But, again, why are you focusing on a group that is statistically less likely to commit mass shootings compared to the average person? Even if you find some root cause for trans shooters, you’d be, at best, eliminating what amounts to about 0.1% of cases. Why not look at groups that are over represented?


One day I'm in a coal mine and 1 canary dies, the next day 100 canaries die. I probably think the coal or some mineral in the mine just kills canaries.

Eventually a dog dies. Now I start wondering "Well dogs are only 1% of the dead animals, may as well not focus on that..." I may miss out on an important observation.

If your presumption is true, that trans are more robust against these kind of acts, now I'm wondering. Maybe unhinged poorly socialized young males are the canaries and trans are yet something new. What's wrong in the coal mine and what can I learn by focusing on the newest subjects.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: