One word answers are not always the best way to answer. They are acceptable only if you are on a big hurry. The best answer would be to form a sentence.

<rant>I just spent an absurd amount of time setting up my local windows environment to use node 10 and gulp with node-sass and node-gyp (complete BS). I also need to do the equivalent for our Ubuntu pipeline.

And guess what, I just need to do the same for the new team member that just joined and messed his installation with recent versions of everything.

Oh, still find that easy? Lets just throw in crowdstrike and netscope firewalls and proxies for added security and block 50% of node environment and break all TLS/SSL connexion because things are not difficult enough.

Want to use git? Sure, it’s jsut 3x to 4x times slower than on Linux.

Did not pay extra carefull attention or do not know the difference between CR, LF and CRLF? let me just make your git life miserable by changing the line endings on all your files. Good luck fixing it.</rant>

Still better than being forced to develop on windows.

I have tried. It is very difficult. In fact tiktok and Instagram have so many domanin names and IP addresses that it is hard to list them all and block them.

Blocking the main domain would prevent you from accessing the web site, but the mobile app would work. Then you can block the api and stuff, but clients already connected would still work because they rely on the CDNs. When you block a good bunch of the network, the app would just feel Brocken, not blocked. When users keep reloading they will find a CDN you have not blocked yet. Also, they will still get notifications because they are pushed via Google services. They won’t see them in the app however.

So you just need to monitor the logs to keep blocking tiktok domains that pop up.

If you can block via regex or joker chars (*) then, it would be easier for you.

You can look up domains list of tiktok on the internet for a good start.

For my experience, I just managed to make tiktok and Instagram broken enough to frustrate the users and discourage its use over the network.

I konly know about two. What are the other three?

I mean, the learn about people part.

This probably not the case in many countries. All the schools and university you can subscr8be to in my area will impose on you their schedule. You only get to choose a studies path or branch then you will need to pursue with their schedule. You do not get to choose the classes.

But the thing schools are trying to produce, educated young people, don’t fit in to the schedule. Most of them cannot wake up early.

How do you do it?

GNOME is a good interface. They have very good touch support. It is also well polished, beautiful and easy to use. Has a good mix of flat and not flat design. It feelancery fluid.

If she isbised to macos, she will find it good.

Maybe a simple nextcloud instance with some plugins.

deleted by creator

Star Trek is surely a big community, bit it still is a single community. However, for GNI/Linux, we are all around the place here.

Look for a desktop app.

Most often you dont want your close friends and family to know about your problems with your partner for many reasons.

Experiment. Apply scientific pro endure for cooking. Just see what people like and what they don’t so you adjust the recipe.

I guess it is better to spend some little time cleaning up your existing install than doing a fresh one. From what you describe, you just have some leftover configuration files you can delete.

Fresh installs is needed when you messed up your current install with broken packages or missing ones or missing configuration and you just don’t know how to clean it up.

So as long as you can clean up your install, just clean it.

I don’t eat soup. Full stop.

The only two important columns are “Local address: port” and “process”. The later is what process is listening whille the former is the interface that process is listening on and the port.

So you see that I don’t have any process listening on any port other than 80 and 443 iin the host and the regular ones.

That said, you containers will still listen on the ports you want but only on a virtual network interface.

Basically you only need to publish ports 80 amd 443 on the container or pod you have your reverse proxy on. Other containers need to only be attached to the same network as you already did.

Yes this is very important.