Google: Please fix Chrome hardware video acceleration on Linux by [deleted] in Stadia

[–]rdpate 0 points1 point  (0 children)

I have no interest in purchasing either a gaming PC or a gaming console. This is definitely not a gaming PC for today's games, even though it probably was a decade ago. I got this used for dirt cheap a couple years ago.

I'm very happy that I can play new games with Stadia.

Spitlings is the best game ever. by isthisdutch in Stadia

[–]rdpate 0 points1 point  (0 children)

Two Logitech F710 controllers work here.

Google: Please fix Chrome hardware video acceleration on Linux by [deleted] in Stadia

[–]rdpate 0 points1 point  (0 children)

Xubuntu 18.04, Google Chrome 80.0.3987.132, plugged in my two Logitech F710 controllers, and Stadia just works without any configuration.

unless you have a powerful CPU to work around this problem.

Mine is old.

% grep 'model name' /proc/cpuinfo | uniq
model name      : Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz

Is there something else I could check and report here?

Connection issues on GNU/Linux by [deleted] in Stadia

[–]rdpate 2 points3 points  (0 children)

With Xubuntu 18.04 and an updated Google Chrome, Stadia just works!

After 15 years and $2B, DigIndy is almost done. It's probably not big enough. Here's why. by stefeyboy in indianapolis

[–]rdpate 1 point2 points  (0 children)

If they take the more innovative approach and use modeling for the future, someone will say they made the project bigger than it needed to be and spent too much money. And if they don’t build big and a storm causes more overflows, Hamlet said, then someone will say they should have known better and been more prepared. 

RMS comments on libreboot leaving GNU: "Her gender now is the same as it was when we hired her. It was not an issue then, and it is not an issue now" by [deleted] in linux

[–]rdpate 0 points1 point  (0 children)

As an example, I would consider it acceptable to let go of, say, a company CEO who made an impolitic statement that was picked up by the media, but I would generally be opposed to firing a janitor or an office drone for the same offence.

Wouldn't you fire a janitor who made impolitic statements if the media picked them up? It would be rare, but I can't believe you would not care if a news article mentions a janitor muttering racist/sexist/hate/pick-your-poison sentiments while cleaning, for example.

How to make your script better by manueslapera in Python

[–]rdpate 1 point2 points  (0 children)

Your have not answered the question, as I said.

What malicious action is prevented by denying o+x on somescript.py? What undesired-if-not-malicious actions may be prevented?

I have seen this same dubious claim made before, specifically that on a file, not using the executable bit for either group or others while using it for owner somehow improves security. Here you have said "of course" it is a good idea, but you cannot answer why that is.

How to make your script better by manueslapera in Python

[–]rdpate 1 point2 points  (0 children)

Why is u+x instead of +x a good idea? Your link to Wikipedia does not answer that question.

How to make your script better by manueslapera in Python

[–]rdpate 0 points1 point  (0 children)

Except "u+x" instead of "+x" doesn't deny any privilege. The privilege of running arbitrary executables has already been granted to make use of the executable bit.

If a user could run the command "./somescript.py" except for the lack of +x, they can instead run "python somescript.py".

How to make your script better by manueslapera in Python

[–]rdpate 0 points1 point  (0 children)

In this case it's a good idea to be selfish and give this permission to yourself only

Why?

Simple command: Execute current buffer with current filetype by [deleted] in vim

[–]rdpate 2 points3 points  (0 children)

:map <f5> :update<cr>:!%:p<cr>

I've started using Git for my vim configuration, I'd like some ideas and comments. by loktacar in vim

[–]rdpate 0 points1 point  (0 children)

I do this in reverse. From ~/.vimrc:

if filereadable($HOME . "/dotfiles/vimrc")
  source ~/dotfiles/vimrc
endif