I may or may not be any number of unfathomable beings.

  • 0 Posts
  • 132 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle



  • Someone must still be responsible for monitoring all this, pulling the trigger on platforms that fit the criteria, and then actually enforcing that trigger pull, though. They will be, by definition, one step behind the public at all times, following them from platform to platform to tell them “you can’t be here anymore”.

    People want X (variable, not ex-twitter), the government doesn’t want people to have X, so the government bans X. The people still have X. This fits into the same nutshell that the War on Drugs does and the drugs are winning that one pretty resoundingly, and you have to actually go out in public and buy those. I don’t see a reason why the War on Social Media is going to go differently especially when anyone can set up a VPN from the comfort and privacy of their living room.
















  • Hey, I was working on the same problem the other day and maybe you can help me with it a bit further. If you don’t mind.

    I like to run gotop on my second monitor so I can watch my system resources, and normally I just open a terminal window and type gotop and it runs and stays open and continually updates. I’ve made this command into a shell script to run at startup. Using this script presumably halfway works, because a terminal window shows up, but it tells me “the child process exited normally with status 127.” and prompts for relaunch (which does nothing except present the same message again).

    Now the internet tells me that 127 generally means “command not found” which doesn’t really make sense to me because gotop is in my PATH and can be run normally without any kind of special arguments or location if I pop open a terminal and do it myself. So I’m not really sure where the problem lies. The script in question is currently parked on my desktop and when I run it manually, when logged in and everything, nothing changes except that I also get an additional terminal window that states the child process exited normally with status 0.

    I’m brand new to both Linux and shell scripting so I barely have any idea what I’m doing here, I’ve gathered through individual research that I should also have a line starting the file with #! /bin/bash but I’m not actually even too confident about that part. Currently the entire script reads as follows:

    #! /bin/bash gnome-terminal -- sh -c gotop

    I’ve tried with and without quotes on gotop and I’ve tried with and without the hashbang and none of the four options have given me different results, which makes me think I’m barking at the wrong tree. I have made the script executable so I don’t think that’s the problem.

    O wise one, please bestow upon the poor noob your knowledge. (This request is also open to other wise ones who may be passing by.)