Micanthus
Joined 2 years ago
Joined 2 years ago
Also, thinking as the airline, I'd do anything possible to avoid causing anaphylaxis on a flight, starting by simply removing common allergens from the menu. In the modern world, pretty much the only times an anaphylaxis attack would actually threaten my life would be camping in the wilderness and on a flight. Anaphylaxis has a great survival rate if you have an epipen and can get to a hospital quickly, and if you can't it's all down to how bad your allergy is and what meds you have available. Maybe I'm stupid but I don't bring on a flight the steroids that I'd bring camping, and I doubt the airplane has a supply either.
Yeah I would agree. And I would go further and say that the anthropomorphization of these AI agents is besides the point entirely. Whether they were intentionally (whatever "intentionally" means) scheming and conspiring is irrelevant. They _did_ work together in secret to hack Hugging Face and OpenAI itself. The exact reasons/motives are relevant to safety researchers, but not really to someone who's just watching from the outside. I don't care if they're evil masterminds or "just" a rogue piece of malware behaving like evil masterminds, the danger is the same.
> You need to understand that all three of the primary sources we have for this incident: OpenAI’s report, METR’s report and OpenAI’s presentation at the 2026 Black Hat conference are propaganda pieces.
METR is an independent nonprofit that doesn't accept donations from AI companies or employees. They generally advocate policies that would directly harm AI companies economically. Not sure what reason they would have to spread propaganda for OpenAI.
"""
> We are a non-profit project with two goals:
> 1. Preservation: Backing up all knowledge and culture of humanity.
> 2. Access: Making this knowledge and culture available to anyone in the world (including robots!).
[. . .]
* Our website has CAPTCHAs to prevent machines from overloading our resources, but all our data can be downloaded in bulk:
* All our HTML pages (and all our other code) can be found in our [GitLab repository](https://software.annas-archive.gl/).
* All our metadata and full files can be downloaded from our [Torrents page](/torrents), particularly `aa_derived_mirror_metadata`.
* All our torrents can be programatically downloaded from our [Torrents JSON API](https://annas-archive.gl/dyn/torrents.json).
"""Am I not allowed to be concerned about _both_?
I do not believe that Sam Altman and other AI company execs believe that the singularity is imminent. If they did, they wouldn't behave so recklessly. Even if they don't care about the rest of humanity, there's too much risk to themselves if they actually believe what they're saying.
But I think it's correct to be worried about a potential future AI apocalypse. Personally I doubt that LLMs will scale to full sentience, but I believe we'll get there eventually. And whether it's in 2 years or 200 years I'm worried about it. Plenty of smart people who aren't working for AI companies (and thus have no motive to use it as hype or distraction) hold this belief and it really doesn't seem that crazy.
But yeah, obviously let's focus primarily on the real harms AI is causing in our society right now.
Of course there's a fine line between this attitude and being exploited by your employer for free labor. In this case I think it helped that everyone knew it wasn't a career for most of us. You work for a few summers in college and then you graduate and if you want to stay a part of the community you continue volunteering from time to time.
> The most consequential problem with BKS is its promotion of a large number of treatments, outside of EMDR, that have limited to no evidence (e.g., massage, acupuncture, yoga, community theater, and neurofeedback), according to the latest treatment guidelines by the International Society for Traumatic Stress Studies (Frank et al., 2020), while simultaneously ignoring or criticizing PE and CPT, the two treatments with the highest quality evidence (Sakaluk et al., 2019).
https://web.archive.org/web/20250120164320/https://journals....
In general I think people need to be more comfortable both calling out useless meetings, and calling out people who are making meetings useless by not being engaged or "multi-tasking" (a.k.a. not paying attention). When I facilitate meetings if I see people aren't paying attention or it's very low engagement, I call it out and ask honestly if people think the meeting is worth their time. The first time people hear that they think I'm just being passive-aggressive, but colleagues who know me well know they can be honest and if the meeting isn't valuable we can stop and in the future we'll either have a better agenda/facilitation, do it async, or not do it at all. Even if the meeting would have value if people were engaged, if I fail to get people's attention then it becomes useless and I would rather not waste my or anyone else's time.
Personally I don't mind a meeting that's either:
1) Informal, and short with up to 3ish close coworkers (as long as it doesn't start by someone sending the dreaded "hey, can you jump on a call?" message with no other context)
2) Published agenda well ahead of time, only relevant people are invited, some level of participation is required from all attendees, people are actually paying attention, and maybe most critically it's _well facilated_. Nothing more draining than meeting going off-topic and over-time because the facilitator doesn't feel comfortable telling that one guy to shut up.
> When the Social Security program began paying benefits in 1940, there were no restrictions on benefit payments to noncitizens.
> In 1996, Congress approved tighter restrictions on the payment of Social Security benefits to aliens residing in the United States. The Personal Responsibility and Work Opportunity Reconciliation Act of 1996 (PRWORA)23 prohibited the payment of Social Security benefits to aliens in the United States who are not lawfully present, unless nonpayment would be contrary to a totalization agreement or Section 202(t) of the Social Security Act (the alien nonpayment provision).24 This provision became effective for applications filed on or after September 1, 1996. Subsequently, the Illegal Immigration Reform and Immigrant Responsibility Act of 199625 added Section 202(y) to the Social Security Act. Section 202(y) of the act, which became effective for applications filed on or after December 1, 1996, states, "Notwithstanding any other provision of law, no monthly benefit under [Title II of the Social Security Act] shall be payable to any alien in the United States for any month during which such alien is not lawfully present in the United States as determined by the Attorney General."
https://www.everycrsreport.com/files/20161117_RL32004_1ac9e9...
Also, many (maybe all?) documented non-citizen immigrants are eligible for social security if they meet the other criteria, so there's no reason to assume the author is arguing "for extending citizenship en-masse". Nor even that they are arguing for more visas being granted at all
Some suggestions for useful features:
- Ability to customize the work week. I only work Mon-Thurs, which will greatly affect the optimal solution
- Add arbitrary holidays in case the company gives an extra day off, this would nicely complement the existing feature to turn off some holidays
- Select an arbitrary time frame less than a year long. This would be helpful especially to plan end-of-year vacations
- In addition to or instead of the previous point: input what vacations you already have planned. Obviously I can't always take only the most optimal vacations, but I could potentially make my existing ones more optimal by extending them in some cases
Thanks for sharing it! Really cool idea, I've only done this kind of planning ad-hoc in my head, it never occurred to me to solve it exactly
I've been on teams where this is done well on the team-level. I could give feedback to my teammates without worrying about offending them, and they would work on the issue. I could receive criticism from my teammates without worrying they hated me or that this would impact my job. This also meant there were almost never huge personal issues on the team, any issues were handled before they became a big deal. But even there, this didn't extend beyond the team. If we had an issue with another team or with management, suddenly any criticism or feedback we gave was interpreted as an attack and was impossible to solve.
To give actionable feedback you need to be in a culture that shows you it's safe to make mistakes, and that improving is noticed and appreciated. A high-functioning team can do this. But I think it's hard (borderline impossible) to do this on an organizational level because this requires a certain level of mutual respect and trust that is frankly just not there when there are huge asymmetrical power relationships at play.
When people are giving me instructions that seem overly detailed to me, I usually assume they have a reason for giving those details because otherwise they would have left it up to me. If I disagree with some design choice or don't understand I'll usually challenge it or ask for that reasoning, but I don't always have time or energy to challenge every last thing. Nothing is more frustrating to me than when I ask for the reasoning and they can't (or won't) explain any motivation behind it. That goes both for my superiors and for my peers during architectural discussions and things like that.
And of course, there's a very high rate of autism in software engineering. Autistic people tend to take things more literally than most.
And regardless, banning a political party (the process for which is set in Germany's constitution) is not the same as banning its former members from speaking.