• 222 Posts
  • 1.42K Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle


  • Not updating with audit would work if every direct and transient dependency provided security updates for every version. But they don’t. Often, security updates are for the most recent version or versions, and if you’re far behind, you now have to audit a lot more.

    Transient dependencies are an audit problem, too. To audit something, you have to essentially audit recursively. Many libs use many other libs of varied authors.

    Our systems are too open, too vulnerable. A build or check being able to access all resources is a fundamental systematic vulnerability.




  • They’re bash/shell- and bin-dependent commands rather than Git commands. I use Nushell.
    Transformed to Nushell commands:

    • The 20 most-changed files in the last year:
      git log --format=format: --name-only --since="1 year ago" | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20
    • Who Built This:
      git shortlog -sn --no-merges
      git shortlog -sn --no-merges --since="6 months ago"
    • Where Do Bugs Cluster:
      git log -i -E --grep="fix|bug|broken" --name-only --format='' | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20
    • Is This Project Accelerating or Dying:
      git log --format='%ad' --date=format:'%Y-%m' | lines | str trim | where (is-not-empty) | uniq --count
    • How Often Is the Team Firefighting:
      git log --oneline --since="1 year ago" | find --ignore-case --regex 'revert|hotfix|emergency|rollback'

    /edit: Looks like the lines have whitespace or sth. Replaced lines --skip-empty with lines | str trim | where (is-not-empty).

    command aliases
    def "gits most-changed-files" [] { git log --format=format: --name-only --since="1 year ago" | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20 }
    def "gits who" [] { git shortlog -sn --no-merges }
    def "gits who6m" [] { git shortlog -sn --no-merges --since="6 months ago" }
    def "gits fixes" [] { git log -i -E --grep="fix|bug|broken" --name-only --format='' | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20 }
    def "gits aliveness" [] { git log --format='%ad' --date=format:'%Y-%m' | lines | str trim | where (is-not-empty) | uniq --count }
    def "gits firefighting" [] { git log --oneline --since="1 year ago" | find --ignore-case --regex 'revert|hotfix|emergency|rollback' }
    

  • Given the nature of Steam and previous executed data extraction, I’m scared installing and running niche/indie games now. Windows lacks

    A unified GUI framework hasn’t happened yet, not between OSes, nor really within each OS ecosystem. I’m not hopeful about leaps in native interoperability in that regard.

    Web tech interoperability is so established and widely used, packaging and running those natively seems much more viable than any hope for supposed native long term efforts.

    Not everything will be covered by web tech. But for many things, it’s already viable, and exploring native integration of these web technologies is interesting.





  • Git push to Forgejo -> automated build, package, and deploy pipeline -> use secured credentials to upload via scp or ssh or sftp

    Alternatives to copy-upload or upload-package and then extract via command is stuff like rsync (reduce redundant, unchanged file uploads) or a simple receiver service (for example REST endpoint that receives a package with an identifier key and secret key, that it extracts to a configured target folder).

    What solutions are simplest or easiest depend on the target environment, and how much of it you control. If you host the website on Forgejo itself it’s as simple as pushing the static files into the corresponding pages branch.


  • It falls back exactly the way I think.

    This article talks about flashes, and proceeds to say fallbacks should be defined. It explains how fallbacks work, but fails to describe what actually leads to the flashes, how fallbacks get replaced, and fails to say anything about solving that flashing issue they talk about.

    Defining a more similar fallback font may reduce the issue visually, which is not mentioned either, and either way is not a solution for the flashing.

    Dunno why one would expect lower precedence CSS rules be integrated into more specific CSS rules without explicit “inherit”. That’s not how CSS works. Dunno if that’s a common enough misunderstanding to warrant a “not the way you think it is” title.