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/)Q
Posts
141
Comments
685
Joined
3 yr. ago

I joined Lemmy back in 2020 and have been using it as @qaz@lemmy.ml until somewhere in 2023 when I switched to lemmy.world. I'm interested in systemd/Linux, FOSS, and Selfhosting.

  • Don’t engage with these ignorant assholes man, they are all in banking’s pocket.

    Shit you got me, you ruined our perfect psyop!

  • fiat ecosystem (including mining, storing and transport of gold)

    Gathering / transporting valuables is not a part of the fiat ecosystem. The value of fiat currency does not depend on any underlying materials (like gold, silver, etc.) like the currencies before.

  • Yes. It was an amazing proof of concept, but it has been surpassed on all fronts.

  • The ASICS also produce e-waste, the electricity could have been used for other things, and the energy use puts more strain on the energy grid when that is already an issue in many countries.

  • Yes, but that still means that the other half is fossil fuel.

    Bitcoin mining's distribution makes it difficult for researchers to identify the location of miners and electricity use. It is therefore difficult to translate energy consumption into carbon emissions. As of 2025, a non-peer-reviewed study by the Cambridge Centre for Alternative Finance (CCAF) estimated that bitcoin consumed 138 TWh (500 PJ) annually, representing 0.5% of the world's electricity consumption and resulting in annual greenhouse gas emissions of 39.8 Mt CO2, representing 0.08% of global emissions and comparable to Slovakia's emissions.

    I think people should really reconsider using PoW cryptocurrencies. Ethereum was able to reduce their energy consumption by 99.95% by switching to PoS and it's still doing fine. IMO Bitcoin is outdated technology that is just used as a pyramid scheme due to its name recognition.

  • Assuming that Trump fires Powell

  • Perhaps, but bitcoin isn't exactly the best example of that.

  • Yeah imagine that

  • Waar heb je het over?

  • There are 27 countries in the EU, there is only one USA. Most people don't seem to care about each other's national happenings.

  • https://github.com/Shadlock0133/cargo-vibe

    I thought it was a joke, but this is actually viable and even configurable

    By default, cargo-vibe will, on success, vibe full strength for 3 seconds.

    You can change that by setting CARGO_VIBE_PATTERN environment variable. For example, to set it vibe for 1.5 second on 20% strength, you can do:

     shell
        
    CARGO_VIBE_PATTERN="0.2 1.5s" cargo vibe <cmd>
    
      

    You can also set full patterns of vibes to run, by separating them with slashes /. Here is one example:

     shell
        
    CARGO_VIBE_PATTERN="0.4 1s/0.6 1s/0.8 0.75s/1.0 0.25s"
    
      

    Wait, there's more! https://github.com/funkeleinhorn/cargo-shock

    To let Cargo Shock trigger your shock collar use: cargo shock build

    To use it everytime you can alias cargo="cargo shock".

    Cargo Shock can also be combined with other tools like Cargo Mommy and Cargo Vibe like this: cargo mommy vibe shock build ...

    And they have a really slick site: https://openshock.org/

  • You're talking about YAML? /s

  • The real problem is merging before waiting for that one slow CI pipeline to complete

  • I was never banned, but I disliked how it was controlled by a single unreliable company. The API restrictions were the final straw for me.

  • It depends, if report federation issues are a major concern then yes, if not, then you can do without.

    I've had issues with reports being missed because one instance didn't federate any of them to anywhere, so I'm using it with multiple accounts.

  • I've been using ClickHouse too and it's significantly faster than Postgres for certain analytical workloads. I benchmarked it and while Postgres took 47 seconds, ClickHouse finished within 700ms when performing a query on the OpenFoodFacts dataset (~9GB). Interestingly enough TimescaleDB (Postgres extension) took 6 seconds.

    All actions were performed through Datagrip

    1 Insertion speed is influenced by reduced networking overhead due to the databases being in-process.

    Updates and deletes don't work as well and not being able to perform an upsert can be quite annoying. However, I found the ReplacingMergeTree and AggregatingMergeTree table engines to be good replacements so far.

    Also there's !clickhouse@programming.dev

  • Aren't they a berry?