Can the controller be updated without a PS5?

Yes, but mumble. Fuck that discord noise and back to the old ways.

OpenSuse (back then the “normal” one, then Leap and now the rolling release Tumbleweed). It just works really well and keeps on trucking. Updated my old machine for ten years through all the openSuse releases without reinstalling. The repositories are very well kept in order and the build service easily provides anything I might find lacking.

Also, I quite like using Yast for system administration. There are many areas that I rarely touch and having a GUI available is super helpful.

Update: today I was able to update to kernel 6.7.5 and the issue disappeared for me.

And that nonsense is why I’ll switch to a Pixel phone

Did nobody really question the usability of language models in designing war strategies?

Correct, people heard “AI” and went completely mad imagining things it might be able to do. And the current models act like happy dogs that are eager to give an answer to anything even if they have to make one up on the spot.

Yup I’m hit by the exact same bug currently. But I was able to go back to before I updated with Snapper and now I’ll wait until the fix is in the Tumbleweed repos.

But other than that I’m much happier with the AMD than with my Nvidia (on Linux that is). VRR with Wayland on multiple monitors just works without issues. And before this week I never had any issues at all with the 7800XT.

Angry downvotes because people don’t like to hear that a meme language is a meme language.

Sniffing the fumes has become part of playing games on the deck.

If you get access to the media files that the streaming service sends you without recording it yourself it’s WebDL. Could also be done by decrypting media you “downloaded” in their app to watch later.

WebRip is basically exactly that: capture audio/video during screening. WebDL is secret magic to tickle the streaming service for the files it sends to the browser during streaming.

Thanks for posting. Encountered this today and gave up after half an hour of fighting battlenet in lutris. Starting the game directly with wine worked well enough.

I have explained my issues in my other posts. Do you have a specific question?

How does it compare to LocalSend?

wow you are getting in quite a nonsensical defensive mood here. I gave my opinion on it and warmaster asked for clarification. If you want to use it go ahead I just pointed out the red flags. If you think it is hateful that people read the readme of your favorite project you really need to grow up. A readme is not the place for absurd ‘promotion’ like it’s a product sold on TV.

Also it’s not FOSS but a selfmade variation on Apache 2. Check the reddit link, even the author claims it is not FOSS.

It is becoming an important threat to you. Managing servers, applications and data is very complex, and the problem is that you cannot do it on your own: how do you know that the server application where you store your family photos has a secure code? it was never audited.

How do they fix this? Do they audit and approve all source code? Do they submit security patches to the apps they have in their repo?

In fact, the recent LastPass leak happened because a LastPass employee had a Plex server that wasn’t updated to the last version and was missing an important security patch!

How do they fix this? Auto updates? Those are going to bite you in the ass extremely hard at some point.

Things like this are completely untrue:

Additionally, because every new self-hosted applications re-implement crucial systems such as authentication from scratch everytime, the large majority of them are very succeptible to being hacked without too much trouble. This is very bad because not only Docker containers are not isolated, but they also run as root by default, which means it can easily be used to offer access to your entire server or even infrastructure.

Most tools currently used to self-host not specifically designed to be secure for your scenario. Entreprise tools such as Traefik, NGinx, etc… Are designed for different use-cases that assume that the code you are running behind them is trustworthy. But who knows what server apps you might be running? On top of that, a lot of reverse-proxies and security tools lock important security features behind 3 to 4 figures business subscriptions that are not realistic for selfhosting.

Scaremongering and lies.

Then let me tell you this: Cosmos does not solve any of the risks they paint in their vision. You are lulled into a false sense of “security” after they frightened you.

Why use Cosmos?

If you have your own self-hosted data, such as a Plex server, or may be your own photo server, you expose your data to being hacked, or your server to being highjacked (even on your local network!).

It is becoming an important threat to you. Managing servers, applications and data is very complex, and the problem is that you cannot do it on your own: how do you know that the server application where you store your family photos has a secure code? it was never audited.

Even a major application such as Plex has been hacked in the past, and the data of its users has been exposed. In fact, the recent LastPass leak happened because a LastPass employee had a Plex server that wasn’t updated to the last version and was missing an important security patch!

That is the issue Cosmos Server is trying to solve: by providing a secure and robust way to run your self-hosted applications, you can be sure that your data is safe and that you can access it without having to worry about your security.

Yeah, no, thanks. That sounds 100% like some snake oil salesman trying to sell me nord vpn or some trash because HaCkeRs.

I’ve been looking for this just yesterday but apparently all sync info is end to end encrypted anyways and Mozilla has no access to the synchronized data? Is there a reason to self host this but just for the principle of it?

Thanks I’ll keep an eye on that project. I did try pandoc and LyX in the past to ease the pain but typst appears to have the courage to finally let LaTeX be and not build a new wrapper around it.