Skip Navigation

Posts
0
Comments
252
Joined
2 yr. ago

  • It just bothers me that I have to use a tool outside of the ecosystem for that. Doesn't it also behave differently though? Like doesn't it assume everything is root when you use the socket required for docker-compose?

  • I just wish podman-compose wasn't so scuffed. I submitted a PR about some garbage months ago and it just seems dead.

  • If a hallucinating AI with marginal direction enslaves us all, we deserved it.

  • For desktops it doesn't make much sense, but now everything's so oriented to systemd its actually starting to affect embedded Linux applications... so lets try our best to keep the alternatives alive.

  • I just don't like the idea of supporting a company as large as Cloudflare. That and their pricing system doesn't make a lot of sense. I have to wonder where they are making their margin back.

  • I really want to use porkbun but I don't want to write scripts to integrate a custom name server api into ddclient. (I know some people have written their own wrappers but they've yet to make it upstream.) Namecheap it is then.

  • One argument against using DD is that sometimes the optimized default flags for FS creation change between kernel releases so its nice to take the opportunity when getting a new drive to reformat partitions. In addition to this, dd is slow if you haven't completely filled up the partition because it doesn't attempt to use fs metadata to seek sparse data on disk and instead copies all bytes of the partition. (Completely unnecessary and just causes extra wear on solid state medium)

    I use rsync instead of cp so I get verbose messages, hash checks, and resume functionality during large copies. https://wiki.archlinux.org/title/Rsync#File_system_cloning

  • This unless it's bandcamp Friday or it can be found secondhand.

  • We do not defend companies in these parts. If everyone's bad then everyone's bad. There shouldn't need to be a "relative to x, y isn't that bad."

  • I'm just patiently waiting on TBSync to support it so my calendar at work normalizes. Otherwise its golden.

  • You'll need to do 4 things:

    1. Refresh your keyring
     
        
    pacman-keyring --init
    pacman-keyring --populate archlinux
    
    
      
    1. Remove the archlabs section from your pacman.conf
    2. pacman -Syyu
    3. Maintenance: https://wiki.archlinux.org/title/System_maintenance#Check_for_orphans_and_dropped_packages

    This should be everything. You'll need to be careful with removing packages with no upstream. I'm not sure how archlabs distributed their configuration files but if they were packages you'll have to be selective about what you remove. Ideally you'll slowly drop those configs for your own versions with future upgrades.

  • I'm not betting on the 51%, but it's still on the table. I'm more convinced they'll start throwing garbage over the protocol and uninformed users will migrate to instances that support that garbage because of peer pressure, features, or just wanting to get rid of the encoded messages. It'll turn into the green chat bubble argument with some people feeling their instance is superior in the way it deals with it.

  • Eh, they could still do the scummy shit Apple and Google were doing to each other with SMS. Start encoding "extra features" in the standard messages and pushing that garbage out to the rest of the network. Or hit it with a 51% attack and scramble everything that can't defederate fast enough. Still problematic.

  • I'd also like an industrial drone for dispersing pesticides and liquid based fertilizers.

    Yamaha: Would you like it to match your motorcycle?