Chat Logs

  1. bluehi phaleth
  2. phalethhi blue
  3. phaleththis is cool https://docs.opnsense.org/development/api/core/interfaces.html
  4. nevetInterfaces โ€” OPNsense documentation
  5. bluewhat is that
  6. blueit's an API for managing your comp?
  7. phalethAPI to manage VLANs
  8. phalethREST
  9. bluenice
  10. phalethpeople are building all the things we need https://github.com/AthennaMind/opnsense-exporter
  11. blueholy guacamole
  12. bluebut'd need to use freebsd
  13. bluetime for superarch
  14. phalethheh, yeah
  15. phalethfreebsd is the goal anyway
  16. blueman I friggin' despise those modern people with their 'main' branches
  17. * blue spits
  18. blueone more reason not to use github
  19. blueI think once RP is up, I'll move primate as well
  20. blueI don't really inherently care for GH stars, and I despise GH enough to want to completely move away from it
  21. bluethe only reason to stay is that if you get over 1k stars, you get clanker freetime with claude, and I've cancelled my claude subscription anyway, clankers produce only nonsense
  22. phalethpeople do main branches outside of github as well
  23. blueyes, unfortunately, this cancer has spread everywhere
  24. phalethheh
  25. phalethit's nice that contabo allows to install freebsd, even if outdated, I think I still got the freebsd upgrade steps somewhere, cause opnsense is installable on top of freebsd using some bootstrap script, so there will not be a need to pay contabo for custom image storage
  26. bluecoolsies
  27. blueso one mistake I think zig did (beyond moving to codeberg), was that they left the old issues open on GH
  28. blueshould have migrated them
  29. phalethyeah, prolly, they are busy jumping from one place to another
  30. phalethit's complicated to migrate from github, for example gitea is still trapped there
  31. phalethbut at least that makes gitea discoverable
  32. bluethe only thing it requires is guts, otherwise you'll never break GH's awful monopoly
  33. bluebut zig have chosen the worst of all worlds. they could have selfhosted, AND they should have migrated all the issues and set the repo on GH to archived/readonly
  34. blueI'd say a gitea selfhost could have been the right path for zig
  35. bluebut now you have a situation where there are over 3k open issues on GH, and every bug needs to be checked twice
  36. bluetypical andrew
  37. bluepeople often forget there's a difference between a good engineer and a good maintainer, andrew is a great engineer and a terrible maintainer
  38. phaleththere is a non-profit behind codeberg that cares about the hosting and zig devs can't even be bothered about setting up nginx properly on their Hetner VPS
  39. blueyes, but would *you* trust an ideological german non-profit? I wouldn't
  40. phalethI think it's better for them to stay zig compiler focused
  41. phalethwell, they can always move again later, at least now they are not too bothered
  42. bluetrue
  43. phalethgitea is still cool, straightforward to setup, but when you have nobody doing devops and only compiler people then you need some help
  44. phaleththe cool thing about non-profits is that the expenses are tax deducible, doesn't matter if it's german
  45. phalethbut for sure germans are crazy about software
  46. bluemy problem with codeberg is mostly that they are ideological, and I don't like ideological people in software
  47. blueyou could say RMS is ideological too but I don't mean software ideology, I mean political ideology
  48. bluesoftware should just be software. we should all use master, drop the cocs nonsense, and focus on creating the best product
  49. blueI've added a `migrate` option to store creation in primate
  50. bluebecause more than one store can facade a table, it could become impossible to run migrations
  51. blueso you'd need to set `migration: false` on the store you want to exclude
  52. blueor migrate: false, rather
  53. phalethif they manage to get some projects of off github then that's fine, lot of people prolly self-host git remote solutions nowadays
  54. blueyes
  55. phalethnice
  56. bluesomeone warned me migrations is a can of worms but it's such a big can
  57. blueit's a small can of worms
  58. blueit's not such a big can*
  59. blueso far the complexity isn't very great
  60. phalethyeah, but still it would be great if you could implement them only for postgres and possibly also mariadb if there are similarities
  61. blueI'm writing the cli part now. I already finished implementing the primitives for postgres, mysql, sqlite and mongo
  62. bluethe drivers have two primitives, 'introspect' and 'alter'
  63. bluethat's all you need
  64. phalethah, ok
  65. bluewell technically you also need the table create primitive if there'a store file but no table, but it already existed
  66. blueI don't get eslint sometimes
  67. blue`if (!store.migrate) continue;`
  68. blue1. Unexpected any value in conditional. An explicit comparison or type conversion is required. [@typescript-eslint/strict-boolean-expressions]
  69. bluethat's so weird. `migrate` is already a boolean, inverted booleans aren't 'any'
  70. phalethmaybe it expects three exclamation marks !!!
  71. blueI don't really mind writing `store.migrate === false`, but it's not more strict of an expression than !store.migrate
  72. bluelol
  73. blueI think something's broken here
  74. blue"Forbids usage of non-boolean types in expressions where a boolean is expected. boolean and never types are always allowed"
  75. blueoh yeah, itwas some weird artefact. I reloaded the file and the error is gone
  76. phalethheh, cache
  77. phalethsilly webdevs
  78. bluepenultimate boss of software, caching, final boss, complexity
  79. phalethI wish zig succeeds with the zig run watch thing and that it's very fast and flawless
  80. bluewhat's that, reload on changes?
  81. blueor rather, recompile
  82. phalethrecompile, yes