Register and share your invite link to earn from video plays and referrals.

Search results for 1030米兵による殺人事件に抗議します
1030米兵による殺人事件に抗議します community
One keyword maps to one global community path.
Create community
People
Not Found
Tweets including 1030米兵による殺人事件に抗議します
The cheapest MiCA-regulated crypto exchanges ↓ (bookmark for later) Revolut – 0% / 0.09% OKX – 0.08% / 0.1% Gate – 0.1% / 0.1% Bybit – 0.1% / 0.3% Bitvavo – 0.2% / 0.3% Blockchaincom – 0.2% / 0.4% Bitpanda – 0.3% / 0.3% Kraken – 0.3% / 0.4% Bitstamp – 0.3% / 0.4% Cryptocom – 0.3% / 0.5% Robinhood – 0.5% Bit2Me – 0.5% / 0.6% Coinbase – 0.6% / 1.2% eToro – 1% Swissquote – 1% / 1% Data from @DefiLlama.
Show more
HERE ARE SOME OF THE STOCKS THAT HIT A NEW 52-WEEK HIGH OR LOW TODAY New 52-week highs • Global Payments $GPN +10.7% • Gilead $GILD +3.6% • Eli Lilly $LLY +3.2% • Cheniere Energy $LNG +3.0% • ConocoPhillips $COP +2.3% • Altria $MO +1.9% • Keurig Dr Pepper $KDP +1.8% • Exxon Mobil $XOM +1.7% • Pfizer $PFE +1.7% • Chevron $CVX +1.6% • AbbVie $ABBV +1.2% • Visa $V +1.0% • Shell $SHEL +0.8% • Mastercard $MA +0.6% • Johnson & Johnson $JNJ -0.3% New 52-week lows • Reddit $RDDT -29.8% • Coinbase $COIN -13.5% • AppLovin $APP -10.6% • Iren $IREN -10.5% • Applied Digital $APLD -10.1% • Cameco $CCJ -9.8% • Kinross Gold $KGC -8.4% • Mobileye $MBLY -7.8% • Alnylam $ALNY -4.8% • Nio $NIO -4.1% • Baidu $BIDU -3.5% • Banco Bradesco $BBD -2.9% • Xpeng $XPEV -1.9% • Take-Two $TTWO -1.3% • Vale $VALE +1.2% Oil, pharma and payments stocks hit new highs, led by Global Payments +10.7%. On the other side, Reddit fell -29.8% and Coinbase -13.5% to new lows after their earnings.
Show more
🧩 Qwen3.8-Flash-Next: A 6B-Active Preview of the Qwen4 Architecture On the same night Zhipu's GLM-5.3-Flash took over the timeline, @Alibaba_Qwen open-sourced Qwen3.8-Flash-Next — explicitly positioned as a preview of the Qwen4 architecture. Zhihu contributor Kitt在进化 argues that for people who actually run models locally, this is the more practical release of the night. The local-deployment groups he is in are, in his words, on fire. His take: the model is called 3.8, but the architecture is really Qwen4 in preview — and it borrows the best ideas from across the field. 1️⃣ Smaller, cheaper, and realistic for local deployment Flash-Next has 125B total parameters with only 6B active — far smaller than the 300B-class GLM-5.3-Flash. The API is priced at ¥1 input, ¥3 output, and ¥0.1 per cached million tokens, roughly matching DeepSeek-V4-Flash's off-peak rates. His comparison, per 1M tokens in RMB — input / output / cache hit: 🔹 Qwen3.8-Flash-Next: 1.0 / 3.0 / 0.1 🔹 GLM-5.3-Flash: 0.4 / 1.4 / 0.115 (limited-time promo rate) 🔹 DeepSeek-V4-Flash (off-peak): 1.5 / 4.5 / 0.05 2️⃣ A Qwen4 preview wearing a Qwen3.8 name The author points out this is the same play Zhipu made: GLM-5.3-Flash's architecture is also completely different from GLM-5.3. Shipping the new architecture as open weights early is deliberate pathfinding. Inference frameworks like vLLM and SGLang, plus the quantization toolchain, all need lead time to adapt before Qwen4 proper arrives. 3️⃣ An architecture that borrows from everyone The author reads Flash-Next as a synthesis of the field's best recent ideas. 🔹 Attention: Qwen's in-house QSA, built to balance throughput and speed on long context. 🔹 Knowledge: it absorbs DeepSeek's Engram line of work, packing prior knowledge into 51B of N-gram side parameters — high knowledge density at minimal compute cost. 🔹 Training: the Muon optimizer, popularized by Kimi, scheduled together with AdamW. 4️⃣ Half the active parameters, still overtaking At 6B active, Flash-Next is nearly half the size of DeepSeek-V4-Flash — yet Qwen's reported benchmarks show it overtaking that model on multiple coding and agent leaderboards. The author says he is not worried about real-world experience: the recent Qwen3.8-27B already proved itself in daily use, and this sits on the same foundation. 🔗 Full Reading: #Qwen# #Alibaba# #Qwen4# #OpenWeights# #LLM# #AIInference# #MoE#
Show more
# Decision Points in AI Agent Development # Temperature 🎯 The Hook Are you using the same temperature for every task in your agent? Temperature isn't just a "creativity knob." In agent systems, structured outputs, tool calls, and user-facing responses each need fundamentally different temperature settings. Using one value for everything is leaving performance on the table. 📋 Overview Temperature controls how "peaked" or "flat" the probability distribution is when an LLM selects its next token. Near 0, the highest-probability token wins almost every time, producing deterministic and stable output. Higher values flatten the distribution, allowing lower-probability tokens through, increasing diversity and creativity. In AI agent systems, the optimal temperature varies dramatically across contexts: generating structured output, assembling tool call arguments, and producing free-form text each call for different settings. Temperature should be treated as a dynamic variable that shifts with task type, not a single fixed constant. 🔍 Decision Points Temperature is primarily driven by task_variability -- how routine vs. creative the task is. The decision flow is straightforward 🧭 1. Structured output (JSON / function calling)? → 0.0-0.3 2. Accuracy-first (fact extraction, classification, summarization)? → 0.2-0.5 3. Dialogue, explanation, communication? → 0.5-0.7 4. Creative writing, brainstorming, candidate generation? → 0.7-1.0 Additionally, higher failure_cost pushes the temperature ceiling down, and high cost_sensitivity environments should account for retry cost increases from higher temperatures. 💡 Key Details Reference values by task type 📊 - Structured output (JSON / function calling): 0.0-0.3. Minimizing schema violations is the priority - Classification, extraction, data transformation: 0.0-0.2. Accuracy and reproducibility are paramount - Summarization, explanation, customer support: 0.5-0.7. Balance naturalness with accuracy - Creative writing, brainstorming, candidate generation: 0.7-1.0. Diversity is the source of value - Tool argument generation: 0.0-0.2. Precise function and argument names are non-negotiable - Planning and reasoning: 0.3-0.6. Some exploration helps, but maintain logical consistency Start structured output temperature at 0. If schema violations occur at 0, the problem is your prompt or schema -- never rely on higher temperature to "accidentally" produce correct output 🚫 ⚖️ Trade-offs Too low and conversations become robotic 🤖 The model returns identical answers to identical questions, giving users a "template response" impression. Best-of-N sampling also breaks down -- candidates become near-identical, costing N times more for essentially N=1 results. Too high and structured outputs start breaking 💥 JSON field names drift, types mismatch, hallucinations increase -- especially dangerous for proper nouns, numbers, and dates. Tool call instability and loss of reproducibility compound the problem. Monitor the retry cost impact of temperature changes. If schema violation rates exceed roughly 5%, consider lowering the temperature. 🛠️ Use Cases Vary temperature by pathway within a single agent 🔀 Planning steps at 0.3-0.5, tool argument generation at 0.0-0.2, user-facing responses at 0.5-0.7. When switching models, adjust temperature simultaneously for a natural fit. Using Best-of-N? You need to raise the temperature. Generating N=5 candidates at temperature 0 produces 5 near-identical outputs. For N>1, set temperature to 0.5-0.8 and let a Judge select the best from diverse candidates. Be careful combining temperature with top_p ⚠️ Adjusting both simultaneously creates multiplicative effects with unpredictable behavior. As a rule, tune one and leave the other at its default. #AIAgents# #SoftwareArchitecture#
Show more
TensorFold 1.0.3 lands with a few cool things. - Living Weights (beta with Nemotron on Metal) and coming to CUDA in 1.0.4 - Nvidia Ampere (beta) for Nemotron, and native Qwen3.8-27B with DFlash2 - Conversation prefix caching - Various bugs fixed and improvements Twelve contributor PRs helped make this happen, so a massive thank you to @niklaslenz_ai and GitHub contributors akol1, jschmied, chaog992, AdrianBinDC and BobClawblaw, and everyone testing, reporting bugs and helping us improve TensorFold. FYI, Living Weights is in very early beta and has sharp edges, but I think I’m on to something. I’d love community feedback to make it better: @plotarmordev @petruspennanen @MiaAI_lab @volatilemarkts
Show more
New Zakura Release: 1.0.3 We've hardened peer networking and mempool gossip, and marked zcashd compatibility mode as stable for Ironwood. Also, some security updates coordinated with Zebra!
Show more
Tokenization 1.0, 2.0, 3.0. Everyone is somewhere on that curve, and almost nobody is standing still. Laeeq Shabir, Partner at @htdgtl, closing out the roundtable on where institutions actually are today.
Show more
🔸 Oracle 1.0 gave contracts data. 🔸 Oracle 2.0 makes that data semantically programmable. 🔸 Oracle 3.0 interprets unstructured evidence and produces intelligence. 🔸 Oracle 4.0 continuously monitors the world and can trigger policy-controlled action. The applications changed. The oracle has to change with them.
Show more
Dynamic Airdrop Conversion 3.0 is LIVE Conversion 3.0 is the first seasonal incentives model from River that balances contributions and sustains token distribution through recurring Seasons. Built on the concept of time-encoded tokenomics from 1.0 and conversion shaped by real participation from 2.0. Convert your River Pts into RIVER any time before the Season ends.
Show more
0
117
379
85
Forward to community