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

I could be armchair astronomying wrong here - but something that blows my mind: this image represents 6.2 arcminutes across in the field of view, that's 10x smaller than the size of Andromeda in the night sky. Imagine what's behind Andromeda!?


… imagine what’s behind our galaxy!


everything and nothing :)


We can see some things behind it, with neutrinos and gravity waves.


arguably we wouldn't have JWST without Hubble, so cost adjusted they're about the same, then again, there is probably some "prior art expensive project" associated with Manhattan, but I didn't check :)


That's ... a somewhat freighted avenue, and it's difficult to determine where to draw lines.

Hubble itself strongly leveraged Key Hole, as a further extension:

<https://en.wikipedia.org/wiki/KH-11_KENNEN>

As for the Manhattan Project, it was sufficiently close to the first direct theoretical and applied theory and proofs of sustainable nuclear chain reactions (roughly a decade or less following each), and a lack of understanding of the corresponding risks (which greatly increase costs) that there simply wasn't time to have spent all that much money.

By contrast, Hubble and JWST are both late-stage, highly-evolved technologies, pushing the engineering envelope in many dimensions simultaneously, all of which tends to increase costs.

See for example the ELT (extremely large telescope), an Earth-based instrument currently under construction in Chile as part of ESO (European Southern Observatory). Tom Scott's 'splainer video on the project explains how costs risk exponentially with increased size for numerous reasons.

<https://en.wikipedia.org/wiki/Extremely_Large_Telescope>

<https://yewtu.be/watch?v=QqRREz0iBes>


unless you find a way to poison the AI so that it remembers you :)


I am in the South East too, but I see lots of vultures, but one weird? thing I noticed in the past 4 years is that I see them a lot more often in suburban areas/on sidewalks eating roadkill than I had seen them in the past (usually seeing them circling freeways or rural areas)


For me being a bbs sysop is how I connected with the local tech community. Some of them were criminals, others were just other kids and teens. Back then there weren't many ways to find like-minded nerds if you were not in college, so I took what I could get.


Have you ever sat through any diversity training in your career? I have quite a few times and it's... it's really not that controversial or disruptive.

If you have, I'm curious what subjects where raised that you found unhelpful or distracting to your professional work.


having concepts you're already aware of parroted at you in order to check off a box on a spreadsheet somewhere isn't a productive workday -- so mandated diversity training is a waste of time for some people.


I’ve learned something new almost every time I’ve sat through any kind of management or leadership training. Including DEI. Like any kind of training, you only become better with more reps.


or we could demand that users of free software shouldn't dictate the culture of the community and that maintainers don't need thick skin. Instead maybe we should ask that users should be respectful and courteous.


People do ask, but the abrasive ones will double down on it a lot of the time. All I do on my two projects is just block them/ignore them. I've had people make up whole new accounts to get at me again after a block on reddit and twitter


You cannot do that with the current tools. I'd even argue that Microsoft's corporate goals are a bit at odds with the community best interests, e.g. adding friction to Github or to join/add to a project would decrease Github use, which is likely a KPI internally.


Wishful thinking. Humans suck. That won't change, and it's only gotten worse. It's not a fun reality, but it's reality. The sooner you can come to terms with that fact, the sooner you can begin to navigate around it.


Every time I see someone being harassed for writing software in the open I'm going to think of the social campaign against the xz maintainer.


That nobody is talking about the person's IP addresses (the xz project was hosted on a personal server of the maintainer), or any details about their actions indicates to me it was a state actor and the original xz maintainer is cooperating with law enforcement to uncover their actions.


Based on working hours Israeli is likely

https://rheaeve.substack.com/p/xz-backdoor-times-damned-time...

There are other countries on the same time zone, but only Israel has history of using and selling hacks of this level.


Or someone further west who did this after work during the evenings.

Or someone further east with a classical hacker "let's get up late in the afternoon, and start the serious hacking late at night."


From that article, "To further investigate, we can try to see if he worked on weekends or weekdays: was this a hobbyist or was he paid to do this? The most common working days for Jia were Tue (86), Wed (85), Thu (89), and Fri (79)." That makes it more likely this work was done during working hours; someone doing things outside of work hours would be more likely to produce the same amount (or more) on weekends and holidays.


Yes, that would point towards regular office hours and not hacking hours.


Moscow is the same time zone as Israel.


Whilst the ip addresses and email headers etc should be examined meticulously, in the distant hope that they lead somewhere, the chances are that they won't. Very basic opsec.


I thought it was on GitHub pages?


Before pages the project was hosted on the server of the original maintainer.


CISA is investigating it.


or they are totally nonplussed because they are not even a single individual, and a state actor who is doing this on 10-20 other projects for the past 5-10 years which haven't got the same attention. This is their job, being compromised is always a risk.


It doesn't matter if it's a team working for a state actor. You'd still be pissed your 2 year project failed so close to the finish line.


Not if this is one of a few dozen or few hundred similar ongoing operations. The risk is always there, they have to expect some amount of failure. Open source software is constantly being probed for vulnerabilities in every way possible, from random commits to high level members of committees for standards. Every operation is one in a grab bag of disposable and deniable efforts.

I also am a little biased and assume being burned in state-sponsored acts is similar to the no-blame culture of breaking infrastructure in tech :) because by all accounts this compromise was extremely well done, until it wasn't.

Also, we can't be sure the compromise wasn't intentionally telegraphed to cause some other action (using a different library) on purpose.


>Not if this is one of a few dozen or few hundred similar ongoing operations. The risk is always there, they have to expect some amount of failure.

That actually makes me think it's not happening at a larger scale, since we'd likely have heard of at least a few similarly elaborate cases being uncovered by now. If not during the attempt itself, then at least at some later point in time.

Either almost all of these operations remain undetected, because they are even more sophisticated and much of the world's software ecosystem has been secretly compromised for years or there aren't actually that many such operations.


They might even get a kick out of people discussing how clever their hack was. A rare bit of public acknowledgement, in a way.


So what? The nature of the project matters. Seriously F all of the people who worked on it however many or few it was.

It's one thing to attack a target, it's quite another to try to give yourself a master key to every rpm or deb linux box in the world.


Unrelated note: I had always thought "nonplussed" was basically a synonym for something like "bewildering confusion." But the way you used it in this context suggested the exact opposite. It turns out that "nonplussed" has also come to mean "unperturbed": https://en.wiktionary.org/wiki/nonplussed

Quite confusing, because the two different meanings are nearly opposite to one another.

See also: https://www.merriam-webster.com/grammar/nonplussed


> Quite confusing, because the two different meanings are nearly opposite to one another.

It's pretty easy to see where the innovative sense came from: "plussed" doesn't mean anything, but "non" is clearly negative. So when you encounter the word, you can tell that it describes (a) a reaction in which (b) something doesn't happen. So everyone independently guesses that it means failing to have much of a reaction, and when everyone thinks a word means something, then it does mean that thing.

You see the same thing happen with "inflammable", where everyone is aware that "in" means "not" and "flame" means "fire". (Except that in the original sense, in is an intensifying prefix rather than a negative prefix. This doesn't occur in many other English words, although "inflammation" and "inflamed" aren't rare. Maybe "infatuate".)


That's pretty much what my second link is about. :-)


Wow, now I need to go figure what source material I misinterpreted to thoughtlessly use this word incorrectly. Thanks!


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

Search: