| 2 Jul 2021 |
 @hexa:lossy.network | sounds like a version to me 🤣 | 00:00:01 |
| @hexa:lossy.network | we could download the file from archive.org instead | 00:05:02 |
| @hexa:lossy.network | and remember (or forget) to update it once every month | 00:05:19 |
| @hexa:lossy.network | maybe add an updateScript, that checks the last changed header, so r-ryantm can update it? | 00:05:56 |
 dotlambda | In reply to @hexa:lossy.network
maybe add an updateScript, that checks the last changed header, so r-ryantm can update it? It's updated daily as far as I know. I don't know if we want daily PRs. | 06:56:28 |
| dotlambda | Actually no, that's just on linuxnet.ca | 06:59:18 |
|  Irenes joined the room. | 21:38:06 |
| 3 Jul 2021 |
| @hexa:lossy.network | the latest tts release depends on gruut, which depends on python-crfsuite, which has a native library that needs to be built. | 19:12:27 |
| @hexa:lossy.network | Redacted or Malformed Event | 19:15:41 |
| @hexa:lossy.network | _________________ ERROR collecting tests/test_itemsequence.py __________________
ImportError while importing test module '/build/python-crfsuite-0.9.7/tests/test_itemsequence.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/nix/store/2nhfiak8a30vw67mxksc2kdb69np2jcw-python3-3.8.9/lib/python3.8/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_itemsequence.py:5: in <module>
import pycrfsuite
pycrfsuite/__init__.py:2: in <module>
from ._pycrfsuite import *
E ModuleNotFoundError: No module named 'pycrfsuite._pycrfsuite'
| 19:16:11 |
| 4 Jul 2021 |
| dotlambda | I just learned that https://www.nabucasa.com/config/remote/ wasn't designed with MITM in mind. Wouldn't it make way more sense to use self-signed certificate? | 09:27:59 |
| 5 Jul 2021 |
| @hexa:lossy.network | dotlambda: imo pulling the oui.txt into its own derivation and setting the last-changed date as veresion is the best we're going to get | 11:47:23 |
| @hexa:lossy.network | * dotlambda: imo pulling the oui.txt into its own derivation and setting the last-changed date as version is the best we're going to get | 11:47:32 |
| @hexa:lossy.network | we can leave it lagging behind, every once in a while r-ryantm while come across it hopefully and execute it's updatescript | 11:48:06 |
| @hexa:lossy.network | it's just the way it is I guess | 11:48:17 |
| @hexa:lossy.network | for stable source links we could use archive.org though | 11:49:54 |
| @hexa:lossy.network | yeah, I don't like any of this | 12:01:52 |
| @hexa:lossy.network | we need to create something like https://github.com/Mic92/iana-etc | 13:21:39 |
|  spacesbot - keeps a log of public NixOS channels joined the room. | 19:21:03 |
 Zhaofeng Li | In reply to @hexa:lossy.network
we need to create something like https://github.com/Mic92/iana-etc Looking at the list of assignments, I'm surprised how "easy" it is to get a port assignment. For example, there is "norp" (TDP/UDP/SCTP 1528) assigned this year. | 19:35:57 |
| Zhaofeng Li | There are no specs that I can find and the name even has a typo ("Not Only a Routeing Protocol") | 19:36:36 |
| @hexa:lossy.network | yeah, with the iana you just kindly ask for allocations | 19:37:10 |
| @hexa:lossy.network | everyone can do that | 19:37:12 |
| @hexa:lossy.network | with OUI otoh you pay for your allocation | 19:37:18 |
| Zhaofeng Li | That's weird, given that port numbers are much more precious than MAC and IPv4 addresses | 19:40:55 |
| @hexa:lossy.network | uh, I think the important ports are allocated, lots of them have useless allocations | 19:42:14 |
| @hexa:lossy.network | and everyone else reuses ports despite their official allocation | 19:42:27 |
| @hexa:lossy.network | so what does it matter | 19:42:30 |
| @hexa:lossy.network | https://www.iana.org/form/ports-services | 19:43:14 |
| @hexa:lossy.network | here you go | 19:43:17 |
