Sorry for chuckling at your disappointment.

I try to follow Bash strict mode. It can protect you from some foot shooting.

No thanks

Same in Sweden.

Yes, unstable Debian is still hella stable. But you probably don’t want to suggest it as the first Linux dust since you need some extra carefulness when updating.

You cannot seed files that are altered. It’s not the same files anymore.

So yes, as long as you want to continue sending, you need to keep the original files around.

I agree with this but I suspect that a lot of the backend is dependent on other in-house infrastructure so it’s not as easy as most people think.

Won’t that allow for crap to fall into the USB port?

Try Rdx, it’s great for read access to Reddit.

More info in the GitHub repo.

The package name is the unique id. If you want to distribute multiple variants (like two versions with differing signatures) they should not have the same identifier. If they are not the same the id/package name should not be the same.

Having different package names would also prevent the Google play store from trying to update it.

It’s a problem of trust. Differing signature is an indication of third party tampering. People shouldn’t start to see difference in signatures as an ordinary occurrence. It should be an high alert event.

Mismatched signatures have been discouraged since day one of Android. A mismatched signature is a sign that some one other than the original publisher built this package, and the user needs to be aware that it might be malicious.

That F-Droid went with this setup with mismatched signatures was always going to make their apks look suspicious.

This is an f-droid problem. If they use the same package name, they need to use the same signature. That has been the case since long before f-droid existed.

They could just build apks with alternate package names and this wouldn’t be an issue.

Now my 1000/1000 for 429 SEK (about 40$) doesn’t sound as good. At least the candy is cheaper here in Sweden.

We have well established ways to deal with secrets. Also, everyone is responsible enough to not self approve changes where they do things they are uncertain of.

We very seldom resort to self approvals. Everyone in the team see code reviews as important. But also that progress trumps code review.

Who said anything about only requiring 1 reviewer? And no, I did not drop an /s. You should try working for a healthy team where everyone takes collective responsibility and where the teams progress is more important than any one person’s progress.

We decided that everyone in the team is allowed to approve changes. If no one has reviewed your change within 24 hours you are allowed to approve it yourself. It will usually come up in the daily sync that a self approval is imminent, which usually leads to someone taking a look.

Yes, the top most directory, /, is the root directory.

Each directory is a branch in one giant tree structure. For example, if you have a directory containing two other directories, that is a branch that is splitting into two branches. All directories are descendants of the same root.

To blow off steam without focus on a story is very much inline with what we are after.

The downside with rocket league is that if we create tournaments, it is elimination rounds. What do the eliminated people do while the tournament completes. Or maybe I’m overthinking it, they could just play local matches until we decide to start a new tournament.