Skip Navigation

Posts
20
Comments
264
Joined
3 yr. ago

  • Can you edit your message to add a spoiler tag ?

    It's up and running ! The error you get is probably related to the fact you're trying to trace it over ipv4.

  • Thanks for taking on the challenge ! This whole thing is meaningless if there's no one scratching their head at it !

  • Thanks for your message on the guestbook ! I hope you have some fun, good luck !!

  • Looks like you shouldn't ask for anything at all, given that you cannot take a single answer without being a condescending jerk. I'm not affiliated to cyberia.is in any mean by the way just proposing a service that you could use to solve your problem if you were not too busy being a douchebag.

  • Keep in mind that using your own VPS as a VPN doesn't bring anonymity. You're simply replacing one IP tied to your name (your ISP) with another one (your VPS).

    You hide your traffic from your ISP, and delegate it to your VPS provider.

    This will be the same for your DNS. If you want true anonymity regarding DNS, you should use someone else's service, preferably over encrypted channels, eg. cyberia.is DoT.

    I personally use it as a forwarder from a box inside my home (along with others), and use this box as the local DNS when I'm home. This way I know that all DNS traffic is encrypted, and doesn't leak anything to my ISP or VPS or whatever.

  • One could argue that people who say PHP is fine only suffer Stockholm syndrome !

  • Le meilleur moyen de pas se faire voler son vélo, c'est d'en avoir un tout pourri et de le garer à côté d'un moins pourri 👍

  • Okay, good to know. I guess using a shared system remotely overseas doesn't help with fast loading times ^^

  • Do you set the wallpaper from your profile ? I've only tried 9 on a remote system but image handling was painfully slow so I gave up on setting the wallpaper from the Rio theme. Maybe that's faster locally on bare metal ?

  • For it to always work, you should put it in /bin. Every other solution may fail in some corner case.

    Don't do this though.

    The correct way to install a command is to package it for your distro, and put it in a place that's suitable for its usage.

  • I've made something that's both fun and challenging: https://cyb.farm

    It's a tech adventure featuring many challenges about computer science stuff (crypto, stegano, protocols, development, ...). It starts on the 31st of October, and will probably can keep you busy for a few weeks ^^

  •  
        
    $ man up
    man: No entry for up in the manual.
    
      

    Another idea ?

  • Is auto-promotion forbidden ? Also, this game is very unix-y, which is IMO on topic

  • Why so ? It ticks all the boxes from the Rules section ;)

  •  
        
    % pm -i | wc -l
    55
    
      

    That's how many software I packaged myself. They are installed to /usr/local using an alternative package manager because I couldn't be bothered with making an appropriate .deb.

    And as to explain how this alternate workflow is less complex, here's how I go about installing a program:

     
        
    % git clone git://git.z3bra.org/human ~/code/human
    Cloning into '/home/z3bra/code/human'...
    remote: Enumerating objects: 53, done.
    remote: Counting objects: 100% (53/53), done.
    remote: Compressing objects: 100% (53/53), done.
    remote: Total 53 (delta 28), reused 0 (delta 0), pack-reused 0
    Receiving objects: 100% (53/53), 9.35 KiB | 195.00 KiB/s, done.
    Resolving deltas: 100% (28/28), done.
    % cd $_
    % pack
    CC human.c
    LD human
    install -D -m 0755 human /tmp/tmp.rfnbLyIQOz/usr/local/bin/human
    install -D -m 0644 human.1 /tmp/tmp.rfnbLyIQOz/usr/local/man/man1/human.1
    
            > /tmp/human@0.3.tbz
    
    installed human (0.3)
    % pm -i human
    usr/
    usr/local/
    usr/local/bin/
    usr/local/bin/human
    usr/local/man/
    usr/local/man/man1/
    usr/local/man/man1/human.1
    
    
      
  • Talking for myself and not OP: What's complex about apt and yum is the package format per se. The cli is very straightforward and "just works", but whenever you want something that's not packaged and need to package it yourself, you gotta fasten your seatbelt and prepare for the complex task of creating an RPM or a DEB package.

    I know there are tools to help with that, but I've created packages for many distros (Debian, CentOS, Alpine, Arch, Void and Crux), and rpm/deb are just way more complex to create than the alternatives.

  • But I have more vertical space too ;)

  • I'm on the boring side...

     
        
    PS1="% "
    
      

    I like it though, it gives me more room for commands !

  • Crux is also "source first", as you must compile every package from source. However, Gentoo focuses on "use flags" to build the packages, which let's you fine tune every single feature. Crux ports don't have that, so you technically end up with the same software for everyone, except that they're optimized for your architecture.

    Its main advantage is the simplicity of the system as a whole, as well as the build system, which leads to Pkgfile that are very straightforward to write.