正在加载视频...

视频加载失败

Introducing OpenVenice — an open-source, customizable frontend for Venice. Your API key stays in your browser, talks directly to Venice. No server, no backend. - Chat, image gen, audio, music, video, embeddings — everything venice offers in one clean UI - Visual workflows — chain models together (vision →...

40,500 次观看 • 5 个月前 •via X (Twitter)

0 条评论

暂无评论

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

相关视频

Venice recently added API & Credit purchases to the list of $VVV burn mechanisms, which 3x'd the rate of VVV burn overnight. Two thing are happening here: - More of the Venice business is directly connected to VVV burn. - VVV holders can now infer Venice API/Credit revenue by proxy of the VVV burn from this line of business I talk to Jon Venice about this: "The latest credit burns in the credit side of the business has been growing tremendously over the last couple of months. And that includes both people using the app, and buying credits to do things like use pay per use models, create videos, use professional image models...." "So all this this basically takes that whole side of the business that wasn't on chain yet and puts it on chain and ties it to the burn. So what you're seeing there with the credits is that we're averaging, somewhere in the range of $120,000+ credit purchases a day on Venice on top of subscriptions" "I expect to see this credit burn grow just because, that part of the business did not even exist, seven or eight months ago. So that's gone from nothing to almost, you know, in the range of like 50% of our business on an average day. So now that all flows directly back to the VVV token economy." "This just adds everything we've been saying, you know, since we launched VVV, since we've been talking about this over the last couple of years, we really do want to buy and burn as much VVV as we possibly can. We want Venice to grow into a large enough business to be able to afford and buy and burn very large amounts of VVV." "So we're just going to keep marching on that plan."

David Hoffman

10,461 次观看 • 1 个月前

I spent $4,699 on a DGX Spark and used it as a chatbot for six months. Not proud of it. But I think most Spark owners are doing the same thing, so let me tell you what changed. The moment was dumb. I had a recording of a client call, needed notes, and my first instinct was to open a browser tab and upload it to some transcription SaaS. Then I looked at the box on my desk. 128 GB of unified memory. Sitting there. Running a chat model I'd asked maybe 30 questions that day. And I thought: I have a supercomputer and I'm about to pay a stranger to listen to my client call. So I tried to do it locally. And here's where it got annoying: - my LLM can't hear audio - the ASR model I found is great but it's a CLI script - the transcript came out in two languages, need translation - summary needs the LLM again - now I want a mind map, that's another tool - oh and here's a scanned PDF from the same meeting, OCR, another tool Copy paste copy paste. Output saved to ~/Downloads/final_v2_REAL.txt. That's when it clicked: tokens per second was never the point of this box. A 24 GB gaming card forces you to pick ONE model, so everyone picks the biggest generalist and asks it to do everything. But 128 GB doesn't force that. You can keep six specialists loaded at once. A 1.7B speech model transcribes better than a 35B chat model ever will. A tiny translation model just translates and doesn't get creative. The big LLM does the thinking, and only the thinking. The hardware was never the problem. The missing piece was the thing that ties them together. So I built it. SparklingKit. (the name is a tribute to the Spark. also: a spark is one flash, sparkling is when it keeps going) What it actually is: → transcription, OCR, translation, image grounding, text-to-image, mind maps, chat. one panel. → six models hand-picked to fit together in 128 GB with room left over → queue-first: drop a 3-hour recording, go get coffee, check from your phone → nothing is a dead end: finish a transcript and "translate / map / chat with it" are already waiting → visual workflows: chain the steps once, run them forever → everything is a file. one folder. no database. copy it to back up. point Obsidian at it. → nothing leaves your machine unless you send it. The thing I care about most: if you stop using SparklingKit tomorrow, nothing happens to your data. It was already a folder of markdown and json. There's no lock-in to escape. Spark owners: you bought room, not a faster chatbot. This is how I'm using the room. No Spark? The panel runs anywhere Docker runs. Point it at your own endpoints. It's open source, and it's version one. Rough edges exist. Issues and PRs very welcome. Full details and a one-line install at If you've ever uploaded something private to a cloud AI and felt weird about it, this is for you.

stevibe

52,072 次观看 • 4 天前