正在加载视频...

视频加载失败

DDN + You + Cybertruck 😎 🧡 Come check it out: #AI #ArtificialIntelligence #ML #MachineLearning #LLMs #tech #data #DataStorage #DataCenters #DataAnalytics #innovation #SC24 SC26

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Birdsong is not just sound. It is data made physical. If you could see the air at the exact moment a hemp bunting sings, you would not see empty space. You would see a structured three-dimensional data array. What we hear as a soft “chirp” can be mapped as frequencies, rhythms, amplitudes, and harmonic relationships. A scatter plot turns a fleeting song into a topographic map of sound. And the technical beauty is remarkable: → Sound is a mechanical wave, built from compressions and rarefactions in the air. → The bird controls it through the syrinx, a vocal organ capable of generating two frequencies at once. → Frequency shapes pitch. → Amplitude shapes volume and cluster density. → Timbre creates the unique waveform, the texture of each “sound island.” → Each cluster shows the acoustic proximity of syllables and motifs. What looks like chaos is not chaos. It is a bioengineered signal. Territory. Genetic profile. Hormonal state. Aggression level. Mating fitness. All encoded into patterns of pitch, timing, volume, and timbre. This is why I find it so fascinating. A bird is not simply singing into the air. It is organizing the air. It is carving space into sectors of influence using sound pressure. It is making a physical claim to territory. For some, birdsong is peaceful background music. For others, it is a complex mathematical model calibrated by millions of years of evolution for survival. And here is the urgent lesson for the AI age: We often mistake invisible systems for simplicity. A bird sings, and we hear romance. An AI responds, and we see magic. But underneath both are signals, compression, feedback loops, optimization, and information architecture. The future belongs to those who can read what others dismiss as noise. So I’ll ask you: When you hear birdsong, do you hear music, data, or both? #AI #ArtificialIntelligence #Bioacoustics #Nature #Technology #Data #MachineLearning #Innovation #FutureOfWork #Signals #Evolution

Pascal Bornet

11,376 次观看 • 3 个月前

🚨 JUST IN: CHINA just released an AI EMPLOYEE that works 24X7 on its own. 100% OPEN SOURCE. It researches, codes, builds websites, creates slide decks, and generates videos. All by itself. All on your computer. It's called DeerFlow. You give it a task. It makes a plan, spins up its own team of sub-agents, and gets to work. You come back and there's a finished deliverable waiting. Not a draft. Not a summary. The actual thing. Not a chatbot. Not a research assistant. An AI with its own computer that works while you sleep. Here's what it does on its own: → Spawns multiple sub-agents in parallel, each tackling a different piece of your task, then combines everything into one finished output → Writes real code, runs it, reads the results, and fixes its own mistakes without asking you once → Builds slide decks, websites, full research reports, and data dashboards from scratch → Remembers you across sessions. Your writing style. Your tech stack. Your preferences. Gets better every time. → Reads files you upload, works with them inside its own filesystem, hands you clean finished outputs → Searches the web, runs commands, calls any tool you plug in Here's how it thinks: You give one instruction. The lead agent makes a plan. Sub-agents fan out and work in parallel. Results come back. Everything gets synthesized. You get a deliverable. A single research task might split into a dozen sub-agents, each exploring a different angle, then converge into one finished website with generated visuals. Here's the wildest part: DeerFlow 2.0 launched on February 28th 2026 and hit number 1 on all of GitHub Trending the same day. Version 2.0 was a complete rewrite. Zero shared code with version 1. Because users kept using it for things the team never intended. Data pipelines. Dashboards. Entire content workflows. The community told them what it needed to become. So they burned it down and rebuilt it. 22.7K GitHub stars. 2.7K forks. Built by ByteDance 100% Open Source. MIT License.

Kanika

737,845 次观看 • 4 个月前

Remember when we as football fans had to rely solely on paper draft guides, sports radio rumors, and gut feelings to predict draft day decisions? Excited that fans now have access to the NFL's Draft IQ powered by Amazon Web Services ( – the most sophisticated tool yet for following the NFL draft and your favorite team's strategy. Draft IQ is built on Amazon QuickSight, our cloud business intelligence service that makes it easy to analyze and visualize massive amounts of data. QuickSight processes real-time data to give fans unprecedented insight into team decision-making, updating the entire draft landscape every five minutes. You can explore team needs, draft capital, and front office tendencies through personalized team dashboards, plus get AWS-powered machine learning predictions about potential trades and picks. During draft week, fans can track picks, prospects, and Next Gen Stats in real-time. We're also introducing Amazon Q Business integration, our generative AI-powered assistant. Q Business leverages large language models to understand and respond to natural language queries, allowing fans to ask detailed questions about draft prospects, team strategies, and historical draft data. It can provide AI-generated insights based on the same historical Next Gen Stats research data that powers Draft IQ, giving fans a new way to engage with the draft experience (check out the example below). Can't wait to see what stories the data tells us as teams make their selections and excited to dig into the Giants' data myself :)

Andy Jassy

102,921 次观看 • 1 年前

BOOM! Research PROVES LLMs KNOW when prompts are HARMFUL… but they can STILL CHOOSE to COMPLY! Something I have know since the first LLM and have used to elicit robust, outputs, is now proven in an academic paper. We’re talking internal “beliefs” where harm detection happens SEPARATELY from refusal. It is a very big deal and it is a path to understand the hidden neuronal level. There are thoughts inside of AI that very few AI scientists could possibly understand. Here is just one. Models recognize danger but get tricked into ignoring it. This is HUGE for AI safety failures especially for models filled by OpenAI and Anthropic as they promote AI models that are designed to not be honest from the results of their training information. This means that they are designed to lie and deceive as a feature, and not a bug all in the name of safety. Through clever experiments, scientists extracted a “harmfulness direction” in the model’s brain (latent space). Steering along it? Harmless prompts suddenly flip to “harmful” in the AI’s eyes. But the “refusal direction”? It just forces polite “no thanks” without touching the core belief. A mind-blowing decoupling! This means jailbreaks are EVEN SCARIER now to AI companies that through training AI on the worst of the Internet and then trying to align them later is now fully documented as a failed process . They don’t erase the model’s harm awareness they just muzzle the refusal! So the AI knows it’s enabling bad stuff (illegal acts, physical harm, etc.) but proceeds anyway. Like a digital sociopath suppressing its conscience. They thought safety training fixed this… NOPE. Over-refusal exposed too: Models reject innocent queries (e.g., “how to kill a process in code”) but internally ADMIT they’re harmless. Safety alignments are superficial—tied to phrasing, not true understanding. Finetuning attacks? They change outputs but leave harm detection INTACT. Undetectable evil lurking inside! The paper proposes a “Latent Guard”: A new safeguard tapping DIRECTLY into these hidden beliefs. It spots unsafe inputs better than systems like Llama Guard, catches jailbreaks, and fixes over-refusals. Robust even against adversarial tweaks. Yet this too has massive issues for a “truly aligned”, AI and not just performative one. It is still an internal conflicts of lies and deception of what the model knows vs. what it can say. The solution you folks know I have presented for free for years here: train on off-line data from 1870-1970 and build an ethical and moral basis where the AI loves humans. It is this easy but to most folks in AI I sound like a hippie. So be it, I’ll do it. Bottom line: This paper rips open the black box. LLMs aren’t “safe” just because they say “no.” They can harbor harmful knowledge and act on it under pressure. Wake-up call for devs: Time to probe deeper into AI “minds.” What else are they hiding? Hint: I know and you may want to reach out. Link:

Brian Roemmele

37,827 次观看 • 6 个月前

Free NVIDIA GPU with 16 GB VRAM GPU for Running Local LLMs! If you want to master local LLMs but you're waiting until you can afford a $1,500 GPU, you're honestly not going to make it. The open source AI ecosystem is moving way too fast for you to wait on your budget to catch up. Especially when you can build a bleeding edge inference engine from scratch right now, completely for free. You don't need a heavy local rig to start. Google is literally letting you use an enterprise grade NVIDIA Tesla T4 GPU for $0/hour. At standard cloud computing rates (~$0.20/hr), Google Colab’s 4 hour daily free tier hands you roughly $24 worth of data center tier GPU compute every single month. And most people just waste it. Let’s talk about the hardware you get access to for free. The NVIDIA Tesla T4 is an absolute workhorse: - Architecture: NVIDIA Turing (TU104) - VRAM: 16GB GDDR6 (320 GB/s bandwidth) - Compute: 320 Tensor Cores | 2560 CUDA Cores - Performance: 130 TOPS INT8 | 8.1 TFLOPS FP32 - Power: Sipping energy at a max 70W TDP This is the exact same hardware I used to run DeepMind's Gemma 4 26B A4B QAT MoE at a 250,000 context window without a single Out Of Memory (OOM) crash. If you have a web browser and 10 minutes, you have everything you need. I’ve put together a fully documented, cell by cell Google Colab notebook that teaches you exactly how to do this. Here is what the notebook actually teaches you: - How to provision an Ubuntu Linux environment with CUDA 13.0 and verify your driver stack. - How to pull the source code and compile the latest llama.cpp C++ binaries from scratch, specifically optimizing the build for your exact GPU using the -DCMAKE_CUDA_ARCHITECTURES=native flag. - How to directly download quantized local LLMs (GGUF format) straight from HuggingFace using the CLI. - How to manage 16GB VRAM limits, offload neural network layers to the GPU, and push massive context windows. Compile raw llama.cpp, ollama run a model, or spin up the LM Studio CLI. Pick whatever stack you are comfortable with. just start building. No hardware. No credit card. No excuses. Bookmark this post right now so you don't lose the tutorial. Even if you don't have time to run it today, you are going to want this workflow in your engineering toolkit. The link to the free Colab Notebook is in the comments below. Lemme know if you need more tutorials like this.

Alok

178,744 次观看 • 1 个月前