This doesn’t seem to show any site I browse in the DuckDuckGo app, which raises the question, if DDG can hide connections it makes from showing in privacy report, can any (more nefarious) app do the same?
Docker on macOS doesn't have the same underlying system support as on Linux, which is where Docker originated.
The Docker experience on macOS is also marred by the fact that Docker Inc. appears to have limited interest in their Docker Desktop offering, whereas a third-party alternative like Orbstack provides a much better experience.
I perused the Rustic website and they have a direct comparison of Restic here: https://rustic.cli.rs/docs/comparison-restic.htm. At face value I thought it was just, "because it's Rust," but it does appear to have a few additional features.
Rustic was started by a former restic contributor. My impression at the time was that he was frustrated with poor collaboration from restic maintainers (slow/no response to his PRs). So it's a bit more than just "rewrite-it-in-rust".
Many of his rejected/ignored restic PRs ended up being features in rustic: cold storage support, config file support, resumable operations, webdav server, etc.
I switched to rustic a couple of months ago due to it being able to filter based on .gitignore files. Have done a few test restores and everything has worked well so far
A killer feature rustic has over restic is built-in support for .gitignore files. So all your dependencies and build output is automatically ignored in your backups.
Nice. Using `.gitignore` would simplify my Restic, Borg/Borgmatic, and Rsync-based backup scripts/configs. (Right now, I end up duplicating the same information in a few places, not very well.)
At first I thought that sounded great, but then I realized that that would exclude files that I want to be backed up, like `dir-locals-2.el`, which should be excluded from git, but should also be backed up. There doesn't seem to be a great solution to that in general.
Wouldn’t you back up your git repos by pushing them somewhere? Even if that somewhere is a different directory on the same drive. Backing up your local working copy sounds a bit odd.
IIUC, what Apple is doing is reducing the number of active channels, so they can keep audio streaming at 48kHz in mono. OP is claiming better audio out quality, which to your point will be unnecessary with the new update, but also better audio in quality by always forcing the external microphone to be the default source, since it's not constrained by the BT bandwidth and is of overall better quality than those of AirPods.
I also think that by doing this, BT audio out can be in stereo/48, which is arguably "better" than mono/48, so their app is still useful.
I personally wouldn't subscribe to it, though. The script OP mentioned on their post seems sufficient for my use case.
I would be happy if its fixed! I'm on Sequoia 15.1 and it's not fixed yet. This is not exactly my million dollars idea, just a side project I made for personal use decided to see what happens if I put it on the AppStore :)
The initial investigation which triggered the arrest was made by the OFMIN ("Office spécialisé dans la lutte contre les violences faites aux mineurs" basically the government branch tracking and fighting CSAM).
Supposedly, Telegram (and by definition of the french law, the CEO) did not respond to requests for takedown of harmful content (or not enough or faster?) from the the OFMIN. This triggered another investigation looking globally at how Telegram handle content moderation on the public part of Telegram (Channel) which lead to all others charges of complicity.
This is basically the CEO taking the fall because the (unreachable by french law) Telegram company is not on french soil and he made the mistake on landing here.
What is harder? I have a setup just like that. Create VM, use open wrt image as disk Vm, configure some passthrough for the nics and press start?
Updates are as easy as other device (press button on web interface or use openwrt cli)
IMO, owrt runs best on x86 (it’s your usual Linux kernel after all) and you get the best support and performance. You also avoid a lot of all the bugs related to embedded development with custom SoC, internal switch, vlans, flash layout, possibility of brick, bootloader stuff, etc.
Most voiced complaints are (as neutral as possible):
- past CEO personal belief on LGTB rights
- If opted in, blocking ads while showing their own ads as system notification (ads are not being replaced in page)
- hijacking typed-in domains in the address bar by adding their affiliate code on select domains related to crypto (reverted after backslash)
- Tips (using their crypto coin BAT) to Content Creators not using Brave being held indefinitely until withdrawn by Creator (behavior changed after backslash)
and now:
- VPN services being installed automatically if browser has admin rights on Windows.
Edit: I'm just listing what I have been hearing the most on HN.
First is irrelevant to whether the product is good, I don't care about purity tests.
The rest of the list, minus the end, is them trying to make money without selling data. That actually makes me more confident about their belief in their stated values. Last one is an "accidental" oversight, probably to boost install numbers. They decided to change it without backlash first. Again, good move.
You can actually if you didn't expand your partition and keep the default layout. Use the firmware builder to build a customized image with your needed packages.
Edit: ah I didn't see that you run openwrt on baremetal...
Caution advised for people jumping early, the Release Candidate 4 was released only ~10 days ago and didn't have the usual long testing period (usually month). More, the devs introduced major refactors late in the release cycle.
RC4 changelog includes bump to major components, most notably: hostapd, ucode, ubus, netifd.
Is that common in OpenWrt to introduce more changes between RC versions? Usually you want to stabilize everything as much as possible until the final version been released, but seems they continue to push out RCs as standard updates...
Unfortunately, yes. On top of that, they keep adding new devices in RC, keep bumping the kernel version (minor), introducing new code base (such as the new refactor on hostapd/ucode/netifd) and sometime cherry picking commits from master which I would have not chosen (not just bug fixes but features).
Don't get me wrong though, I very happy that such project exists but OpenWrt could be more stable and reliable with a better workflow. Anytime you flash a new version, you have this small fear of bricking your device (especially the exotic ones as Openwrt mainly relies on external testers).
https://support.apple.com/en-us/102188