今日已更新 235 条资讯 | 累计 37786 条内容
关于我们

今日精选

HOT

最新资讯

共 37786 篇
第 1832/1890 页
开源项目 GitHub Trending

🔥 OpenMOSS / MOSS-TTS - MOSS‑TTS Family is an open‑source speech and sound generatio

GitHub热门项目 | MOSS‑TTS Family is an open‑source speech and sound generation model family from MOSI.AI and the OpenMOSS team. It is designed for high‑fidelity, high‑expressiveness, and complex real‑world scenarios, covering stable long‑form speech, multi‑speaker dialogue, voice/character design, environmental sound effects, and real‑time streaming TTS. | Stars: 2,051 | 53 stars today | 语言: Python

2026-05-28 21:00 6 原文
开发者 The Verge AI

Qualcomm promises $300 Windows laptops with new Snapdragon C

They started at $1,000. Then $700. Then $600 budget machines. Now, Qualcomm says the price of its Arm-based Windows laptops will hit $300 this year. Even though RAMageddon has yet to subside and PC prices keep climbing, the company says it's built a new budget laptop platform called Snapdragon C - "C" as in "Compute" […]

Sean Hollister 2026-05-28 21:00 28 原文
创业投融资 The Verge AI

Xiaomi 17T Pro arrives with the company’s biggest battery yet

Xiaomi has announced the 17T and 17T Pro, two cheaper spins on its 17 series flagships. As is usual for the T-series, the focus is more on performance than photography, with the biggest batteries Xiaomi has included on any of its phones outside China yet. The 17T includes a 6,500mAh silicon-carbon battery, while the 17T […]

Dominic Preston 2026-05-28 21:00 45 原文
AI 资讯 Reddit r/MachineLearning

A new dataset with more that 100M hi-quality, curated images, with captions and meta data! [P]

Hello everyone. The new dataset is named MONET, is Apache 2.0 and available on HF: https://huggingface.co/datasets/jasperai/monet MONET is open, Apache 2.0-licensed image–text dataset. It was built from 2.9 billion images and refined to 104.9 million high-quality samples. We are also publishing a paper that explains how the dataset was created if you are curious and 3 compagnions projects A umap to visualize the distribution A retreival tool to do text or image search A codebase to train T2i model based on MONET Hope this will be usefull! submitted by /u/dh7net [link] [留言]

/u/dh7net 2026-05-28 20:59 6 原文
AI 资讯 Reddit r/webdev

Has anyone actually used the experimental window.translation API in a real project?

I'm working on a few client sites where translation costs are getting ridiculous. I started looking into whether we can do more on the client side and came across someone or a company? experimenting with Chromium's built-in translation neural net instead of calling external APIs. Has anyone here tried building around window.translation yet? How flaky is the model loading? What kind of fallback are you using when the browser hasn't downloaded the language pack? Mostly curious about the architecture, especially around handling the initial load and performance on lower end devices. (I apologize if links are not allowed, not use to posting much) submitted by /u/Old_Acanthisitta1396 [link] [留言]

/u/Old_Acanthisitta1396 2026-05-28 20:57 5 原文
AI 资讯 Dev.to

Stop letting LLMs hallucinate dates — a tool for AI agents

If you're building an AI agent that touches dates — booking flows, scheduling bots, "remind me on Friday" assistants — you've probably noticed: LLMs are terrible at dates. They hallucinate weekday-to-date mappings. They fencepost-error ranges. They forget what "next Friday" means in Ukrainian vs English. Asking the model to "be careful" doesn't fix it — what fixes it is moving date interpretation out of the model and into a deterministic tool. That's what whenis is. Use it as an agent tool Define a resolveDate(expression, reference) tool that calls whenis . Let the model invoke it instead of guessing. import { createParser } from ' @whenis/core ' ; import { uk } from ' @whenis/locale-uk ' ; import { booking } from ' @whenis/booking ' ; const parser = createParser ({ locales : [ uk ], plugins : [ booking ], options : { preferFuture : true }, }); const ref = new Date ( ' 2026-05-28 ' ); parser . parse ( " наступної п'ятниці " , { reference : ref }); // → { type: 'date', date: '2026-06-05', confidence: 1 } parser . parse ( ' з 5 по 10 червня ' , { reference : ref }); // → { type: 'range', start: '2026-06-05', end: '2026-06-11', nights: 6 } parser . parse ( ' після свят ' , { reference : ref }); // → { type: 'fuzzy', reason: 'holiday_ref', // metadata: { suggest_next_month: true } } English works the same way: import { en } from ' @whenis/locale-en ' ; const parser = createParser ({ locales : [ en ], options : { preferFuture : true } }); parser . parse ( ' next Friday ' , { reference : new Date ( ' 2026-05-28 ' ) }); // → { type: 'date', date: '2026-06-05', confidence: 1 } How it differs from chrono-node Multi-candidate output. A bare "Friday" mid-week emits both this Friday and next Friday with confidence scores. Your agent re-ranks using conversation context — no silent guessing inside the library. Locale as data. Adding RU/PL/CS is one source file with no engine changes. The Ukrainian locale ships full inflection: months × 7 cases, weekdays × 4 cases, pointers, conne

Fedishin Nazar 2026-05-28 20:52 6 原文
AI 资讯 Reddit r/webdev

How do you handle a real backend with nextjs?

Hey guys. We used to write our backend code primarily in python flask. And then we added nextjs/react for frontend. But the way it was done by previous devs was nextjs talks to flask internally on localhost and passes requests onto flask after handlingu the auth. As there's only one public subdomain. But often times it feels so ceremonial. Because flask has a route. Then nextjs has an equivalent route. And for basic stuff it almost looks equal size in the 2 places. There's endpoints just to pass a request on. And then someone suggested to do rewrites for certain stuff but that just splits the ability to where do you find code related to a certain thing like whitelabel. You go and first find it in nextjs routes, then u see if it's in any of the rewrites. And then you go and dig the flask equivalent. Since nextjs is totally really a real backend. And it anyways sits in the middle to interject every request due to auth etc. Makes me wonder if it's a bad idea to let it handle most of the crud stuff. Because rn it gets a request to say serve a logo. It gets a route handles headers etc and sends a request to flask hey can you grab that logo for me. And then ships it back. But it's gonna take just a few lines more for nextjs to end up doing the whole thing itself. Now the only issue is. That would sort of split the duties a bit. And the line might be slightly arbitrary. I personally prefer if we can keep all the business logic in python as that's what our team understands best. And also do certain data science stuff for which you anyways need python. But overall is it a bad idea to split duties between 'backends' like this. Especially the simpler crud stuff. Or how else would you suggest the backend handles the requests. Is route handlers the way or rewrites. Thanks. submitted by /u/Consistent_Tutor_597 [link] [留言]

/u/Consistent_Tutor_597 2026-05-28 20:51 5 原文