与「digapp」相关的搜索结果

[RADIO INFO] 本日オンエア！よろしくお願いします🐰 ニューアルバム『NOW』のことや最近digしているものについてお話しています🔍 FM宮崎「dig app!」 8月4日（日）18:00〜18:55 コメント出演 📻 #radiko# #15th_abemao# #digapp#

BREAKING: President Trump speaks out about the Department of Justice's move to drop the Reflecting Pool vandalism case. "That was the one mistake with the reflecting pond, they hadn't put up the cameras yet... If they would have had them up, we would have had a lot of- it would have been a lot easier. And I was disappointed with Jeanine Pirro, really disappointed with Jeanine Pirro. She folded like an umbrella and people get away with things, and it's a disgrace."

Arday scandal exposes "moral rot" in academia - racist identitarianism, "opinion dressed up in incomprehensibility", "grievance studies". Pathologies won't disappear overnight, but things could improve if honest academics seize the moment and give the charlatans a roasting.

RAG system that skips HTML parsing entirely! PixelRAG is an open-source visual RAG framework that renders documents as screenshots instead of parsing them into text. Most RAG pipelines start by converting HTML to text. Tables flatten into unstructured rows. Charts disappear. Layout context is gone before the LLM ever sees it. The paper measured this directly: HTML-to-text conversion accounts for 36.6% of retrieval failures on SimpleQA. PixelRAG skips that step entirely. It renders pages as screenshot tiles using Playwright, embeds those tiles with a fine-tuned Qwen3-VL-Embedding model, builds a FAISS index, and passes retrieved images directly to a VLM reader. No text abstraction in between. Benchmarked across six datasets against the strongest text-based baselines: - SimpleQA: 78.8% vs 71.6% (+7.1 points) - NQ-Tables: 48.8% vs 42.5% (+6.3 points) - EVQA: +15.5 points - LiveVQA: +11.3 points One honest caveat from the authors: this requires Qwen3-VL-4B class models or larger to see the benefit. Smaller models trail text retrieval. The authors also recommend using PixelRAG as an enhancement layer alongside existing text systems rather than a full replacement. Ships with a pre-built Wikipedia index covering 8.28M articles across 28.1M screenshot tiles. A Claude Code plugin lets Claude take screenshots of any URL and reason over the visual content directly. Key capabilities: • Renders web pages, PDFs, and images as screenshot tiles via Playwright • Fine-tuned Qwen3-VL-Embedding model for visual retrieval • FAISS index for fast vector search • Pre-built Wikipedia index: 8.28M articles, 28.1M tiles • 3x token cost reduction via image compression • Claude Code plugin for direct URL screenshot and visual reasoning • LoRA fine-tuning support via pixelrag-train 100% open source. I've shared the link in the replies!

Today, I want to share something that happened to me on Kraken. I’m completely new to crypto, and this was my first time using Kraken. All I wanted to do was convert USDC into USD. Unfortunately, because USDT and USD differ by only one letter, I accidentally selected USDT instead of USD. I didn’t realize my mistake until the transaction had already been completed. In less than a minute, a single misclick resulted in a loss of approximately 810 USDT—more than $800. To be honest, I was shocked and devastated. Like many newcomers, I assumed that all major stablecoins were worth roughly the same, so converting between them would involve little or almost no loss. I never imagined that such a simple mistake could instantly cost me more than 1% of my funds. I immediately contacted Kraken Support, hoping they would understand that this was an honest human error and review my case, or at least consider making a one-time exception. What disappointed me even more was that almost every response came from AI. I was never able to speak with a real support agent. The only explanation I received was that the transaction had already been executed, the conversion details had been displayed before confirmation, and therefore nothing could be reversed or refunded. I understand that Kraken may not have violated its own rules, and I acknowledge that the final amount I would receive was displayed before I confirmed the transaction. But I believe that “the information was displayed” does not necessarily mean “a new user truly understands what it means.” As a beginner, I saw what I believed was a normal stablecoin conversion. I had no idea that the number shown on the confirmation screen meant I was about to lose more than $800. If a platform expects users to recognize an $800+ pricing difference on their own, instead of proactively warning them that the conversion is unusually unfavorable, I don’t believe that’s a user-friendly experience—especially for beginners. I believe that a platform responsible for customers’ assets should do more than simply display numbers. It should also be designed to help users avoid obvious mistakes that can lead to significant financial losses. Crypto is already complicated enough. The risks users take should come from the market—not from a product design that makes such costly mistakes so easy to make. This experience has left me deeply disappointed and has almost completely destroyed my trust in Kraken. I’m not trying to deny Kraken’s rules, and I’m not asking for special treatment. I’m simply asking @kraken and @krakensupport to review my case, seriously consider improving the user experience, provide real human support when genuine mistakes happen, and consider a one-time resolution for customers who make an honest human error. If this could happen to me, it could happen to any newcomer entering the world of crypto. I hope my experience helps others avoid making the same mistake. Please double-check every click. @krakenfx @krakenpro @krakensupport

Grok Build just got another meaningful upgrade, bringing permanent session deletion, smarter diagnostics, better keyboard guidance, and stronger reliability across session management, background tasks, and compaction Release Notes: v0.2.118 Features: • Sessions can now be permanently deleted from the dashboard by pressing Ctrl+X twice on an idle row, or from the welcome list with d then y. • Keyboard shortcuts help (Ctrl+.) now shows how to browse prompt history and search the conversation. • grok doctor now warns when tmux is reducing colors and can fix the config. Bug Fixes: • /btw now retries on temporary model overload instead of failing immediately. • Session sharing is temporarily disabled. • [stop] / Ctrl+C during /compact now cancels instead of no-opping. • Automatic recaps no longer appear twice after the same turn. • Background task wait timeout descriptions and limits now match the client's actual configured ceiling. • Background tasks no longer stay stuck as 'Running' in the tasks pane when they finish quickly. • Plan mode indicator now disappears right after approving a plan instead of lingering. • Dragging the scrollbar in the plan preview now works as expected. • Compaction now correctly handles certain context-length errors from the inference API.

Got a disappointing pelican from DeepSeek-V4-Flash-0731 at default reasoning mode - on the left - but then I bumped reasoning up to high (via OpenRouter) and got the much better one on the right

Steph Curry wanted LeBron James to come to the Warriors. He thought Golden State had a chance. Once it became clear that wouldn’t happen, Curry quickly returned to the truth of his situation, one he’d already grappled with months ago. The disappointment of missing out on yet another difference-making addition, something to get the Warriors out of the Play-In purgatory they’ve been in the last four years, had already morphed into acceptance.