They do. « we are committed to contributing back to the LiveKit community whenever feasible ».

Can access X because it's X and locally blocked, "ironic" to use Twitter to post about sovereignty.

It's ongoing for a will with La suite numérique (https://lasuite.numerique.gouv.fr/).

- Tchap is a message app for officials, - Visio, based on LiveKit - FranceTransfert, I don't know what is it. - Fichiers => Drive - Messagerie => Email - Docs => A better Google Docs - Grist => Excel version of Google docs.

It aimed at "public worker", people working for the government.

Github: https://github.com/suitenumerique

Ironic to use Github to post about sovereignty )

I'm trying to not use it myself but yes, la suite numérique should get out of GitHub.

They already did it for the Ministry of Education with [La Forge](https://docs.forge.apps.education.fr/). Used to be forgejo, now a GitLab instance.

GitLab, a YC and by extension an American company )

This can go as far as we want )

That was a lowry response.

Built using Django!

It's in the AUR (aur/tree-sitter-yaml), a community-driven repository of Arch Linux packages. Not yet official.

Since it comes from `tree-sitter-grammars/tree-sitter-yaml`, it may be quick to integrate the official repo.

Yeap, the two seems like game changer. For now, I'm using "Qwen2.5-Coder-7B". Sweep 1.5B is "just" 12 % point better than Qwen2.5-Coder, but Sweep 7B is 25% point better.

It's good. The blog post about it is very interesting. I hope, a plugin for neovim will be made soon.

https://blog.sweep.dev/posts/oss-next-edit

There's also https://github.com/ggml-org/llama.vim

Which I've been using with Qwen3 Coder. As long as infill is supported, that should work. I'll try later today.

Thanks for sharing this. I personally use vim and not neovim (I do not have anything against it), so this plugin will be a great addon for me. Currently, I have to switch from vim to Cursor and back again for any kind of vibe coding.

There is one already, on of the plugin authors commented here

Someone in this thread already built a Neovim plugin connecting to this model I believe.

Yeap, along with `+++`, `**` and mixing if I remember correctly. I don't understand the logic of using an non-standard syntax because some non-standard implementations may not render correctly.

Actually, yes, now you know for a fact that none of the Markdown implementation will render it correctly.

So, I guess, they used `~~~` instead and it was an error in OP post.

So if syntax highlighting isn't a problem. The standard way of presenting block of code in Markdown is to indent it.

Which is quick and easy to understand.

Well, if you want complex things like nested code blocks, then a kind of "tag" approach can be just the solution needed. Input-wise it doesn't really make a difference, whether I have to type "[[[" and "]]]" or "```" and again "```". Whether or not my idea is more like a tag doesn't seem to have any repercussions. Outsourcing ever more complexity into the parser, with bad design decisions however has a significant cost, which is making development of parsers and grammars difficult.

The point of avoiding tags is to improve the ergonomics: you don't have to remember tag names, use a separate delimiting syntax anyway to indicate where the tag name is, and then repeat the tag name when you close the block. Especially given that this is for a block-level construct anyway, simply using a bracketing syntax isn't causing any of those problems.

Indenting inline code requires a text editor that makes indentation ergonomic or else extra effort per line; and it doesn't mesh well with lists or block quotes.

It's very impressive! I'm mean, it's better than other <200M TTS models I encounter.

In English, it's perfect and it's so funny in others languages. It sounds exactly like someone who actually doesn't speak the language, but got it anyway.

I don't know why Fantine is just better than the others in others languages. Javer seems to be the worst.

Try Jean in Spanish « ¡Es lo suficientemente pequeño como para caber en tu bolsillo! » sound a lot like they don't understand the language.

Or Azelma in French « C'est suffisament petit pour tenir dans ta poche. » is very good.I mean half of the words are from a Québécois accent, half French one but hey, it's correct French.

Però non capisce l'italiano.

> When a contributor release FOSS, it's fair to compensate if you business rely on it.

Nope.

Put it in the license, sell the software, or work for free, but stop complaining about it.

It's nice if businesses who benefit from specific software packages want to pay or show support, but it's not nice to release something "for free" but then jump on a moral grandstand and demand everyone pay so you can feel good about your ideology at the expense of everyone else.

> The ideal license is the Unreal one free for « Individuals and small businesses (with less than $1 million USD in annual gross revenue)

Then make that your license?

You're not wrong, but I feel like a lot of people are hung up on the purism of the OSI definition, and a license that's not so blessed may prevent a project from gaining significant traction, if that is part of their goal.

I think it would be nice if there were a license that was more widely accepted that introduced a monetary component that could compensate the developer(s).