Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)WE
within_epsilon @beehaw.org
Posts 0
Comments 7
Can you code? We need your help to improve lemmy
  • I probably should start learning TypeScript. Foundry VTT and VSCode also use TypeScript. I haven't had motivation professionally. I might need to take it up as a hobby.

    I professionally develop in C, C++, C# and Python.

  • How many steam deck folks are here and what are you playing?
  • The Steam Deck is great for Dead Cells. The game is heavy on randomness. I beat Hand of the King recently with a great run. I hope you get some great runs soon.

    I stacked Brutality, got the assassain dagger (crits when hitting from behind) and phaser (places character behind enemy for long enough to backstab). My criticals were around 40000. It's the best run I have had so far.

  • Compile with AI
  • I now understand the goal a little better.

    Installing F-Droid is spooky. I like the alleged functionality, but I am not certain the source code of the binary is what is running on my device. I also want better guarantees of integrity from F-Droid.

    My software developer tendencies are itching. I will pitch some bad ideas on verifying integrity and creating trust.

    The initially proposed AI could be a federation of build servers. Each build server compiles the source code providing a hash of the binary. Hashes showing up more frequently implies more of the federation have the same binary. Bad binaries presenting a different hash could be filtered by the consumer based on consensus.

    I am hesitant to make an AI level decision like dropping less frequent hashes from consumers entirely. The possibility of the more frequent hashes being incorrect is worrying. A drawback is the lack of automation in forcing the consumer to choose a hash. Maybe the consumer can choose settings to make an AI like decision to always accept the most frequent hash. That decision would be opt in.

  • Compile with AI
  • I develop software in C++, C# and Python. All the languages mentioned feature package managers to manage compilation and delivery of binaries. I can force them to compile from source in the case I do not trust binaries created by some other person. Recompiling is expensive with regard to time.

    Conan, a package manager for C++, uses hashes of source code and packaged binaries for verifying integrity. I am of the opinion that even the most clever systems for maintaining integrity can be broken. I have no idea how AI fits into the problem of package management and trust.

    An AI to compile any repository sounds nice. I am the goto build engineer on my current team. We have four projects slightly different build processes. I wrote the CMake and Python to meet the needs of the developers. Some want flattened include heirarchies, others want hidden headers, so on and so forth. The continuous integration is the same however, so maybe we can standardize the DevOps work. I assume continuous delivery is where the AI would live. I am wary of taking control of the build process away from software developers.