BREAKING NEWS: Guy who sells AI hardware says his employees must use more AI.

Now you just need Meta to allow you on their networks to inspect packets and reverse engineer their servers because as far as I know, WhatsApp messages are not P2P.

/edit I betcha $5 that the connection from client to server is TLS(https), good luck decrypting that to see what its payload is.

That’s where it shot itself in the foot.

It is not UNIX’s job to stop you from shooting your foot. If you so choose to do so, then it is UNIX’s job to deliver Mr. Bullet to Mr Foot in the most efficient way it knows.

s/UNIX/Linux/g

https://www.cyberciti.biz/humour/terry-lambert-quote-it-is-not-unixs-job-to-stop-you/

Classic. I haven’t seen that one in about 20 years. 💟 FreeBSD

You probably use it everyday and didn’t know it https://github.blog/engineering/architecture-optimization/building-github-with-ruby-and-rails/

Got a source on that? The co-founder just stepped down from the CEO role recently, due to cancer. If his replacement is shady, I’d like to know.

The word “hack” is pre-internet. A “hack” journalist or a “hack job” is basically something unprofessional. It is movies that turned “hackers” into someone that gained access to the “mainframe”. In the realm of computer systems, I would argue that a “hack” is doing anything the system was not intended/designed to do. A successful DoS or DDoS needs to find some component of the system that wasn’t designed to handle the amount of traffic about to be sent to it.

There are protections for DDoS (iptables, fail2ban, Cloudflare and so on), you have to figure out a way around them, that’s a hack.

From the article https://icespy.org/

I use if__name__main__ often when working with AWS Lambda, but I also want to run it locally. Lambda wants to call a function with the params event and context. So I would do something like this:

def handler(event, context):
    things
    return {
        'statusCode': 200,
        'body': 'Hello from Lambda!'
    }

if __name__ == '__main__':
    event = {}
    context = {}
    response = handler(event, context)
    print(response)

Neither ~/bin or ~/.local/bin are part of most shell’s default $PATH so you’re going to have to modify the user’s shell profile (or rc) to include it. It’s possible that your favorite distro includes it but not mine. For example(s):

﬌ unset PATH                                             

﬌ /bin/bash --noprofile --norc         
bash-5.2$ echo $PATH
/usr/local/bin:/usr/bin

or

﬌ unset PATH

﬌ /bin/zsh --no-rcs --no-global-rcs
Sinthesis% echo $PATH
/bin:/usr/bin:/usr/ucb:/usr/local/bin

﬌ ls -l /bin
lrwxrwxrwx. 1 root root 7 Jan 23  2024 /bin -> usr/bin

That was on Fedora. The funny thing is /bin is soft linked to usr/bin, weeeee.

This is on Debian

Sinthesis@debian:~$ /bin/bash --noprofile --norc
bash-5.2$ echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

I’m not sure why you’re bringing the XDG or systemd “standard” into this. POSIX standard would be more appropriate but they don’t say anything on the matter, nor should they really. The most important thing is, be predictable. If the user has a problem with one of your scripts, what do they do first? which wolf_bin will show them the full path to the script. So really, the location does not matter much.

That said I would go with one of these two options:

1. Make a package for your distro. This may be overkill for a couple scripts but you did say they’re in a git repository so you could automate it. The package would install to /usr/bin which would require sudo or root. If the scripts are only allowed to be run by one user, set the rwx and group permissions.

2. A pattern I like, especially for lightweight things such as scripts that don’t require compiling or OS management and also are using git; a “hidden” or “dot” directory in the user’s home where the repo lives e.g. ~/.lemmywolf/ Then add scripts directory to the user’s $PATH e.g. PATH=$PATH:~/.lemmywolf/scripts. This is what some fairly large projects like pyenv or volta do. You could take it a step farther and modify this installer script to your liking https://github.com/pyenv/pyenv-installer/blob/master/bin/pyenv-installer

/edit 20 year Linux user (Redhat AS2.1) and 5 years of Unix (HPUX & Solaris) before that.

/edit2 I just noticed the pyenv-installer does not modify the user’s shell profile. That could easily be added to the script though.

:motions at trillions of times people that signed up for Fb, Ig, Twit, TkTk, etc/everything without reading the Terms of Service:

Ok, just be sure it has an integrated circuit breaker otherwise its just…a surge protector. You’ll also need to identify what load it triggers at. For example, I use these on my gear https://tripplite.eaton.com/isobar-4-outlet-surge-protector-6-ft-cord-3300-joules-diagnostic-leds~ISOBAR4ULTRA and they’re rated to 12A which should protect a 15A rated smart plug. I put rated in italics because errrryone is buying CE (instead of UL listed) smart plugs.

Place a surge protector between the smart plug and the PC to be safe.

What benefit does this serve in this situation?

shows your internal IP

nearly everyone uses 192.168.1.1 for their local-non-enterprise network

Verizon as an ISP

You missed BLTMND = Baltimore Maryland, this is the only thing that is identifying but if Bmore is large metropolitan area so youve narrowed it down to ~million people

edge server is hosting your connection

shows their gateway not whatever you just said

your external IP

no it doesnt.

/edit carriage returns