ubergeek77

A bit too late for that now. Once they killed Inbox I just migrated everything to ProtonMail. Don't even use my Gmail address anymore.

No one is calling you a cheapskate. It's just that when you said this:

its not a noble cause to pay some dude who made an app we dont need

...in context, it comes off as "Sync is not necessary to exist, therefore no one should pay him."

I understand what you mean now, but you worded it terribly.

And by the way, going around in the comments being unnecessarily hostile and calling people "dumbfuck" or "asshole," when they were just as confused at your poor phrasing, makes you come off as an asshole, so maybe work on that :)

Sync isn't trying to replace all Lemmy frontends or other FOSS apps, it's trying to provide a Reddit-like experience for people who miss it.

People just find reasons to be upset, I swear.

its not a noble cause to pay some dude who made an app we dont need

Do you think professional independent developers shouldn't be paid for their work? Do you think this kind of development is effortless?

I don't understand why people keep parroting this. The app is free. It's a professionally developed app, where the quality tradeoff is either ads (which can be blocked) or your choice of ad removal payments.

This isn't some company trying to exploit the community here, this is a full time app developer who just had his livelihood completely cut off. People begged him to make a version for Lemmy, and he did. He deserves to be paid for the hours and work he put in to make it happen. You can't make an app if you can't buy food or pay rent.

And if you don't like that, then don't use it. He's never pressured users into paying, and he's never suggested everyone on Lemmy should just send him money. He isn't even spamming posts advertising the app, enthusiastic users are.

Why is everyone so upset?

Rough day at work today, OP...?

Obviously I'm not going to give you the exact character count of my password :p

Same issue, but I run my own instance. The password is 1,000% correct, not sure what's wrong.

I love seeing all the CrossCode recommendations, and on Lemmy of all places. Here I thought no one knew about it!

Easily my favorite game of all time. I don't think it ever drops the ball, the combat is awesome, the story is incredible, and the characters are so well written that you'll think they're actually real people.

The biggest criticism is the game's puzzles, but they aren't really as bad as some (very impatient) people make them out to be, and there are options to decrease the difficulty of the puzzles.

Yeah it's pretty universal. Similar feeling when a limb "falls asleep."

I'm not advocating for running containers as root, I was correcting your suggestion that container breakouts are trivial and easy to perform. But let's walk through those 2022 breakout vulns shall we? I even found one more.

CVE-2022-0847 - DirtyPipe, a Linux kernel vulnerability, and one of the most major and prolific Linux kernel vulns to date. In addition, it wouldn't have mattered if the container ran as root or not, this was a significant Linux kernel flaw. In fact, the PoC runs the container as an unprivileged user.

CVE-2022-0492 - Needed CAP_SYS_ADMIN to be exploitable, isn't exploitable anymore, and falls under my remark of "the user doing something stupid."

CVE-2022-0492 - Vulnerability due to cgroups, and wouldn't be exploitable as a root container user unless a very specific set of 5 prerequisites were met. "Just being root" was not enough for exploitation.

CVE-2022-23648 - Was a read-only vulnerability relating to volume mounts, root vs non-root was not relevant to the vulnerability, and it only allowed for "breakout" in situations where you're running in a Kubernetes cluster and the container can read service account tokens. Running as a non root user would not have prevented this.

I'm not saying "running as root doesn't matter," running as a non root user is a best practice, yes. But breakout vulns are more rare and harder to exploit than even your response to me is trying suggest.

It's pretty hard to break out of Docker unless the user does something stupid, like mount the host's Docker socket into the container.

Casual container breakouts are not common at all, they're a big deal, and fixed pretty quickly.

Use pict-rs, it's what Lemmy uses for image storage, it supports MP4s and GIFs too:

https://git.asonix.dog/asonix/pict-rs