与「RESPECT_V」相关的搜索结果

"President Xi and I have forged a friendship, a truly great friendship actually, built on the mutual respect and the vital interests of our people." President Trump welcomes President Xi Jinping, Madame Peng Liyuan, and the Chinese delegation to the White House to begin their State Visit, reciprocating the hospitality President Xi extended when he hosted President Trump in China earlier this year.

📢🎀RESPECT FOR GEEKS VOL.５参加決定🎀🎤 ＼\特別メンバーで歌唱ライブ‼/／ 「絆のアリル」が渋谷WOMBにて開催する「RESPECT FOR GEEKS VOL.５」に参加！ ぜひぜひ、チェックしてくださいね💫 詳しくは⏬ ＃allele_anime ＃アリルアニメ ＃キズナアイ

I analyzed eleven New York Times reports on the Jensen Huang story. Most notably, NYT makes the "spy" claim 30 times in these 11 reports. The original report cites unnamed officials who had been "briefed" on the intelligence. Not who had seen it themselves -- but who had been "briefed". This is a game of telephone with plausible deniability. Nobody named. No specific details of the intelligence used to draw the conclusion that the woman was a spy. Anonymous "officials" "briefed". This was used to try to take Jensen Huang down. When that didn't work, journalists resorted to viciously digging up and scandal mongering about Jensen Huang's other alleged affairs. Then he was removed as CEO. Without an investigation. Without due process. And now officials and intelligence agencies are contesting the New York Times characterization. This is unethical. It is unjust. It is an absolute disgrace. If anyone should resign now, it is Nvidia's board who aggressively removed Jensen Huang without an investigation, after he gave decades of his life to make the company what it is. And any investigation that proceeds from here should involved not just the "spy" claim, but the New York Times -- who has engaged in potentially unethical behavior. Jensen Huang deserves due process -- not mob justice. He deserves respect for everything he has done for technology and America -- not a disgraceful removal after anonymous, unsubstantiated allegations, several parties removed from the source.

NVIDIA letting Jensen go is a huge mistake, for America and for humanity. It's Apple firing Steve Jobs all over again, but much bigger, given the role of AI in defining the future of our world. I've been keeping quiet on this out of respect for Jensen's family and team, who I've met and who are amazing humans, and because I personally hate infidelity. So my heart goes out to them in this difficult personal family moment. But I can also say that Jensen is human, and makes mistakes like all of us do. Not that I matter at all, but I've known Jensen for a long time and have gotten the chance to spend a lot of time with him, behind the scenes, away from mics and cameras. I have seen him show kindness, humility, care to everyone around him, including strangers, including from the poorest most struggling parts of society, treating all the same with the same thoughtfulness and attention, because they are fellow humans and not because he has something to gain from them. That shows rare character, to maintain humility and humanity through all of it. Another data point is what people who know him well have said privately to me about Jensen over the years. I've never had anyone tell me anything but how awesome he is or how much they love him. Probably over a thousand people at this point. This includes hundreds of engineers, CEOs, colleagues, friends, etc. Also, since there was some spy talk. Jensen is as proud an American as it gets. I'm in shock frankly at all of this, including the mass hysteria around it. I love America, and I think NVIDIA letting Jensen go is terrible for America. I stand with Jensen. Love you all ❤️

We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work. First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs. Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue). Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main. Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown. The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in. Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way."). This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours. All of this works on mutual trust. It ONLY works with mutual trust. Everyone at all times has to trust that they've got each others back: 1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts). 2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer. 3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly). We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago. In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.

House Minority Leader Hakeem Jeffries on Jensen Huang: “There are real concerns that need to be addressed with respect to the Nvidia situation” Jeffries was asked about Nvidia's CEO after a classified briefing for congressional leaders: Q: “Mister Leader, I know you just talked about Jensen Huang, but just to put a finer point in it, you had that briefing downstairs. We know that it came up. You said earlier that you would be asking about it. Are you concerned by what you’ve seen publicly in this Huang case?” JEFFRIES: “There are real concerns that need to be addressed with respect to the Nvidia situation. The briefing was primarily about Iran and the situation as it currently exists. It was undertaken by the director of national intelligence, Jay Clayton, and the CIA director, John Ratcliffe. What is clear, and the NVIDIA issue did come up, but that we’re going to need a full briefing specifically as it relates to the NVIDIA issue so we could all get to the bottom of what has happened and what the implications are in terms of America’s national security.”

13M followers It’s easy to look at that number and forget there was a time when almost nobody knew who CZ was. Back in 2013, he discovered #Bitcoin# through a poker game One conversation changed his direction He studied Bitcoin…He believed in it…He took a massive risk, even selling his apartment to go all in on the industry he believed would change the world Then came @Binance in 2017 No billion dollar brand No millions of followers Just a vision, a small team, and the belief that crypto should be accessible to everyone The rest became history Today, 13 million people follow @cz_binance But to me, the most powerful part isn’t the 13M, It’s remembering the journey from one person discovering Bitcoin and then building #Binance# to becoming one of the most recognized faces in crypto 🫡 Respect, CZ ::

SAM ALTMAN JUST SAID THE WORLD SHOULD "ACCEPT SOME BAD THINGS HAPPENING" FOR AI on politicos new show decoded: "We believe the world should accept some bad things happening for the benefits of this technology." and he went further: "I wouldn't take a trade of saying we will make sure there's no major hacks, there's no misuse of this technology, there's zero scams" same weekend, to vanity fair, he warned about "a coming tidal wave of cybersecurity problems" from open source models so bad things are acceptable when they come with openais progress, and a tidal wave when they come from open source 6 days ago openais president signed the white house accord. internal controls on cyber, bio and chemical risks, outside auditors, board oversight to be fair, hes saying out loud what every lab believes. no technology this big ships with zero misuse. cars, the internet, phones, all of them came with damage the scariest part is who decides which bad things are "acceptable". right now its the company shipping the model personally, id respect it more if the same rule applied to everyone. you cant ask the world to accept your risks and call everyone elses a tidal wave

Grok Build just got another bug-fix update, this time focused heavily on permissions and tool safety Hook permission prompts now show up regardless of approval mode, WebSearch/WebFetch and image generation properly respect prompt_policy and rule decisions, and “Allow once” now really means once......only the next shell command There’s also an extra safeguard for pkill -f and pgrep -f patterns that could accidentally kill their own shell wrapper Release Notes: v1.0.49 Bug Fixes: • Hook permission prompts now appear regardless of approval mode. • Web searches, fetches, and image generation now correctly respect the prompt_policy setting and rule decisions before prompting. • Allow once in permission cards now applies only to the next shell command instead of the whole session. • pkill -f and pgrep -f commands are now rejected earlier when the pattern would kill their own shell wrapper.

Grok Build just got another update, and this one gives you much better control over complex agent runs /rewind now only shows prompts you actually typed, WebSearch and WebFetch properly respect Ask rules, and cancelling one tool call no longer kills unrelated commands running in parallel File tools are also more reliable with large, special and binary files, while authentication recovery now requires a manual resend instead of automatically retrying a refused prompt More predictable parallel execution and fewer things happening behind your back Release Notes: v1.0.48 Bug Fixes: • `/rewind` now only lists prompts you typed yourself and skips automatic runtime turns. • Custom model tables in config.toml now preserve the original model's notice banner. • `read_file`, `search_replace`, and `grep` now handle large files, special files, and binary content more reliably and surface better errors. • Ask rules for WebSearch and WebFetch now correctly show a prompt instead of auto-running. • Cancelling one tool call no longer kills commands started by other parallel calls. • Authentication recovery no longer automatically retries refused prompts after login; the sign-in block now requires manual resend.