Falcon @ Falcon @lemmy.world

Posts

0

Comments

72

Joined

2 yr. ago

I didn’t realise Red Hat, SUSE, Microsoft etc. didn’t pay their staff?

Of course, imagine e.g. games. Setting the refresh rate can be important for a program to work correctly and also performance. In the case of Mull that’s a part of the Rest Finger Printing (RFP) stuff they rolled out around 102.

It’s much the same where I come from.

The high quality institutions have Linux in their labs (either a separate lab or dual boot) and a server with say access for training ML models etc.

The dodgy ones have only Windows with no software and require students to buy a second laptop and install Linux. If they don’t the students fail. Those tests were done in handwriting but they are still an accredited university :(

Am I mistaken in believing it is an already a browser option?

Off the top of my head Qutebrowser and Falkon both support not-saving 3rd party cookies.

Although, Mull is only 60hz. If you do a lot of reading on your phone this can be frustrating.

I often install both.

Could you share the link to some of your driving videos?

I like cars and I’d love to see your stuff.

I have no clue how dangerous running Firefox as root is, but it begs the question…why would you do that?

Create a user account for managing things and create a separate user for each service and/or containers.

For managing things use tmux with ssh, if you want to manage files etc. just use ranger/lf/mc. One can also mount the file system with sshfs.

Yeah there’s a bit of scope to review what op is doing here.

Why is there even a DE on a server if it’s headless. If it’s not headless why not write up some Dockerfiles and manage it from a non-root account?

Are the services running as root?

Also, is it being accessed via wireguard/ovpn? It would be unwise to run a server as root with an open port.

Oh no, I was just pointing it out for others. I think using the title post is perfectly reasonable.

Thank you for posting, I found it interesting.

It’s worth noting that OP simply used the article title.

The article title is a little biased, individuals must take greater personal responsibility.

users knowingly opted into a feature that had a clear privacy risk.

Strong passwords often aren't at issue, password re-use is. If un-{salted, hashed} passwords were compromised in a previous breach, then it doesn’t matter how strong those passwords are.

Every user who was compromised:

1. Put their DNA profile online
2. Opted to share their information in some way

A further subset of users failed to use a unique and strong password.

A 2FA token (think Matrix) might have helped here, other than that, individuals need to take a greater responsibility for personal privacy. This isn’t an essential service like water, banking, electricity etc. This is a place to upload your DNA profile…

The Deb and ppa will have the same content, the ppa is just automatic, assuming the owner maintains it.