trulyrandom

Hah, this is pretty cool. Perhaps having a VR headset on would finally allow me to concentrate in an open office environment.

"I plan to rewrite Linux in C# - Linus Torvalds"

Bad: 0.1897 - Good: 0.7988

Looks like we have a winner.

I would also like to know more about why you think Borg's encryption is questionable. I'm not familiar with Borg's internals, but there's not much one could do wrong here, as it should just be simple symmetric encryption. Does it not use a strong cipher? Is the cipher used incorrectly? Is the key derivation method weak?

Huh, isn't that only the case for Android App Bundles?

Because I prefer sticking to APKs signed by the author of the app. F-Droid APKs are signed with different keys, typically.

F-Droid has a pretty strong foundation in my opinion. It just needs more resources to be able to publish app updates more quickly. It also needs a redesign, like you said, but I don't think there's a need to start from scratch

Apparently andOTP was removed for the same reason a couple of days ago: https://github.com/andOTP/andOTP/issues/396.

As mentioned in the announcement, you can switch over to F-Droid (for the time being) to get the latest version: https://f-droid.org/en/packages/com.wireguard.android.

Pi-hole is a basically a glorified DNS filter. While it's great for blocking DNS names across all devices on your network, it is not a replacement for browser plugins like uBlock Origin.

Thanks for the detailed explanation. Sounds like I'll have to give unstable a shot soon.

Interesting. I was not aware of the staging branch. I thought that patches are always merged into master and then automatically trickle down to unstable once all of the integration tests pass.

How often do you find yourself performing a rollback? I've always stuck to the stable channel, but I may give unstable a shot if it doesn't break too often, as you say.

Because it integrates nicely with the rest of systemd. If you use systemd, there's no real reason to also have a crond running.

Whether the claim hold up or not. If you developed a language that's faster than C, would you not advertise that as a feature?

The same goes for GitHub and GitLab, so this isn't surprising. A real strange thing, is that one also needs a Google account to view the Android issue tracker, for instance.

Factory images are also available now for Pixel devices: https://developers.google.com/android/images.

Before I signed, I was presented with a contract with one of those "you and all of your thoughts are our property" clauses. Those never hold up in court where I live, but I still had it changed to only include any work done during work hours and work that conflicts with the interests of the company. I don't have to report hobby projects that fall outside of that.

If I'd want to start monetizing a side project, I do have to report it, but as long as there's no conflict of interest they're fine with it.

Fun fact: you can expose a Go library in the same way using the c-shared build mode.

Automatic updates, I'm guessing.

I've also had some similarly bad experiences reporting vulnerabilities to managed HackerOne campaigns. I'm guessing the HackerOne staff is primarily trained to judge web vulnerability reports. Anything beyond that often triggers odd followup questions or even a rejection like in this case.

The 3900X is also a big hit. It's such a big hit, that stores in Europe have not had any in stock since launch.

Why? Is that quote bad advice?

You're right. It does have an impact on performance. I haven't done a comparison, but the performance is still acceptable in my experience. It depends on the use case, but the local cache that borg maintains helps a lot in simple cases, because any unchanged files simply get skipped.

You can also use sshfs in combination with borg to eliminate the need for the server to support borg.

That's interesting. Where did you learn about this? One would think they'd just make it a UWP app.

> so many sites don't support v1.3 yet, including HN.

That's not surprising. Distributions like Debian and Ubuntu do not have a recent enough version of OpenSSL in their stable package repository yet.

Previous discussion: https://news.ycombinator.com/item?id=20208169

You're right. My observation was just that the discussions often don't go much deeper than "look at this big binary", so I was surprised to find none of that here.

It's interesting that none of the comments so far complain about the size of the binary (13MB!). Nodejs and Electron projects get flak for this all the time, but Go somehow gets away with it.

This is exactly what the team I'm in does as well. It's fun, and people actually learn to lock their machines as a routine pretty quickly.

Because the mascot of Go is a Gopher, and Go programmers are also referred to as Gophers.

Just assume that it's compromised and generate a new one. There is no point in wasting time trying to estimate how long it might take someone to crack it.