| 12 Jun 2024 |
 vcunat | Off the top of your head, is it normal to see something like this?
(profilingPhase) JavaScript error (foo bar): can't find profile directory
| 08:30:26 |
 hexa | it throws all kinds of warnings and errors in profiling | 08:31:00 |
| vcunat | OK. I'll hope that it actually gets a reasonable profile. | 08:32:58 |
| hexa | Did you notice any regression? | 08:33:42 |
| vcunat | Incidentally, things are slower, but I don't think it's just the browser, so it's probably something else. I noticed this line by accident when fixing a build regression. | 08:36:04 |
| 16 Jun 2024 |
|  @gunboat_diplomat:matrix.org joined the room. | 21:31:27 |
| 19 Jun 2024 |
 Xandor Schiefer | In reply to @zeorin:matrix.org
That would totally work, sure. But it still leaves out anyone else without enough Nix knowledge to even think of such a solution. I'd rather have it fixed in nixpkgs. https://github.com/NixOS/nixpkgs/pull/294971 | 08:09:57 |
| Xandor Schiefer | I created the above PR a few months back, would appreciate any reviews & feedback 🙏 | 08:10:47 |
| hexa | I was under the impression we merged one of those PRs fixing colliding binary names 🤔 | 09:33:32 |
| hexa | I might be wrong | 09:34:06 |
| hexa | https://github.com/NixOS/nixpkgs/pull/320991 | 10:38:37 |
| hexa | 127.0.0.1 wen | 10:39:23 |
 nbp | I asked for it … but we do not do patch-level release unfortunately. | 10:43:55 |
| vcunat | $ ping 127.0.1
PING 127.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.042 ms
| 10:50:06 |
| vcunat | i.e. it already works (partially) with some of these 127.x releases. | 10:50:58 |
| vcunat | * i.e. it already works (partially) with some of these 127.** releases. | 10:51:07 |
 @aloisw:kde.org | PING 127.0 (127.0.0.0) 56(84) Bytes an Daten.
64 Bytes von 127.0.0.0: icmp_seq=1 ttl=64 Zeit=0.053 ms
| 10:51:43 |
| vcunat | The IPv4 addresses with less than four components are a kinda horrible thing, but I actually use ping 1.1 commonly 😊 | 10:52:31 |
| hexa | dtag stopped routing 2600:: a few weeks ago | 10:56:49 |
| hexa | it is horrible | 10:56:54 |
| hexa | how else do you test ipv6 connectivy???? | 10:57:09 |
| hexa | https://blog.mozilla.org/en/mozilla/mozilla-anonym-raising-the-bar-for-privacy-preserving-digital-advertising/ | 11:18:39 |
 K900 | Can they acquire some tree style tabs instead | 11:19:27 |
| vcunat | In reply to @hexa:lossy.network
dtag stopped routing 2600:: a few weeks ago 2a09:: and 2a11:: perhaps? They're short and they even serve DNS. | 11:22:23 |
| hexa | yeah, either could work, need to fix my muscle memory | 11:23:13 |
| vcunat | Or maybe I misunderstood? ping 2600:: works for me. | 11:23:33 |
| hexa | yeah, it works from here as well | 11:26:31 |
| hexa | but in the hackerspace we have DTAG (AS3320) and they don't route it | 11:26:50 |
| hexa | inb4: dtag/cogent dispute | 11:27:48 |
| vcunat | Ah right. Feels like routing disputes almost always involve Cogent... | 11:30:22 |
