| 27 Jun 2024 |
 hexa | https://github.com/NixOS/nixpkgs/pull/322905 | 13:02:38 |
 nbp | In reply to @hexa:lossy.network
https://blog.mozilla.org/en/products/firefox/firefox-news/ai-services-on-firefox/ I just tested, it also works with open-webui services from NixOS unstable. | 13:03:31 |
| hexa | interesting | 13:04:00 |
| hexa | I currently have at least ollama running | 13:04:11 |
| hexa | * I currently have at least ollama running for dabbling with voice stuff on home-assistant | 13:04:24 |
| nbp | I wish it would have been using the API from Ollama, but apparently it just embed the web-page of whatever chatbot you use. | 13:04:50 |
| nbp | I have not much played with it, but you can add additional context menu options by looking at about:config and searching for browser.ml.chat.prompt | 13:07:36 |
| hexa | I'm not on nightly, so it will take a few weeks until I can test that interaction | 13:08:49 |
| nbp | Ah ah, you thought you could avoid it that easily, here is the command:
nix run github:nbp/nixpkgs-mozilla/master?dir=flakes#firefox-nightly | 13:19:41 |
| nbp | * Ah ah, you thought you could avoid it that easily, here is the command:
nix run --impure --no-write-lock-file github:nbp/nixpkgs-mozilla/master?dir=flakes#firefox-nightly | 13:20:15 |
| 29 Jun 2024 |
 Xandor Schiefer | In reply to @hexa:lossy.network
I was under the impression we merged one of those PRs fixing colliding binary names 🤔 If you're referring to this PR: https://github.com/NixOS/nixpkgs/pull/235912, then: kinda, but not really. That change changed the names of the wrappers, but the underlying binaries still collide, which is a problem for e.g. Home Manager users, whose buildEnv doesn't allow collisions, unlike NixOS's.
Also, it aligned the binary names with their nixpkgs attribute names, not with Mozilla's binary names, which are different for firefox-devedition-bin, whose actual binary is firefox-developer-edition, not firefox-devedition.
| 12:09:54 |
| hexa | thanks for clearing that up | 12:10:16 |
| 2 Jul 2024 |
|  Janik (they/them) left the room. | 13:53:10 |
| 4 Jul 2024 |
|  @ryxalor:mozilla.org joined the room. | 08:06:50 |
| @ryxalor:mozilla.org set a profile picture. | 08:15:08 |
| @ryxalor:mozilla.org left the room. | 08:20:15 |
|  Philip Taron (UTC-8) left the room. | 15:46:17 |
| Philip Taron (UTC-8) joined the room. | 15:52:50 |
| 7 Jul 2024 |
|  @1h0:matrix.org left the room. | 08:53:16 |
|  @dminca:matrix.org joined the room. | 09:38:21 |
| hexa | for some reason firefox interacts badly, when I have video running in two tabs in parallel | 15:37:30 |
| hexa | controlling the video in the second tab will make the audio in the first tab stutter for the time of the interaction | 15:37:54 |
| hexa | sometimes pipewire even becomes unresponsive and video playback just blocks | 15:38:58 |
| hexa | another bug that I've seen is with my new-ish camera, which is connected to the USB hub of my monitor, that if I power up my monitor after some time, then firefox crashes somewhere in pipewire due to some weird camera interaction | 15:41:53 |
| 8 Jul 2024 |
|  poscat joined the room. | 00:22:52 |
| nbp | I can suggest to file a bug, and if needed you can ping Paul ( @padenot:mozilla.org ) | 10:45:26 |
| hexa | yeah, I was planning to if 128 did not solve it | 16:20:14 |
| hexa | need to find some time to collect the details and put them into coherent wording | 16:20:38 |
| hexa | https://github.com/NixOS/nixpkgs/pull/325594 | 17:40:11 |
| hexa | https://github.com/NixOS/nixpkgs/pull/325672 | 23:46:02 |
