The DOT standard isn't good, but the US doesn't disallow helmets that meet other standards. You can buy Bell and Alpinestars MIPS helmets in the US today, no gray market needed: https://www.revzilla.com/mips-motorcycle-helmets
Old school helmets use the philosophy that in a crash, you want your head to be harder than its opponent.
New school helmet use the philosophy that a helmet should absorb or deflect as much energy as possible, so that energy doesn't get translated to your brain.
They are actually diametrically opposed. Fortnine (the same channel I linked earlier) has a video on the SNELL standard. Its origins are as a beefier version of the DOT standard. They recently found themselves at a crossroads where it's impossible to both meet SNELL and meet ECE 22.06 (today's state-of-the-art standard). They ended up bifurcating SNELL into two standards: one that meets old DOT-based SNELL, and another that basically says "if it's 22.06, they can call it SNELL variant B." It was the only way they could keep the SNELL brand alive across both halves of the transition.
Hasn't become more friendly from what I've seen. The project seems largely centered around K8s, and isn't really investing in fixing anything on the "compose" side. I did the same thing as you when Docker first started going down the more commercial path, and after dealing with random breakages for a number of years, fully switched back to Docker (for local dev work on osx).
Podman machine is fine, but occasionally you have to fix things _in the vm_ to get your setup working. Those bugs, along with other breakages during many upgrades, plus slower performance compared to Docker, made me switch back. This is just for local dev with a web app or two and some supporting services in their own containers via compose, nothing special. Totally not worth it IMO.
This seems to run completely contrary to Mazda's own Connected Services Privacy Policy, which states that by default (ie if you aren't paying the subscription for connected services, or never enrolled in it), they don't share info outside of Mazda, other than aggregate data for research purposes. Even the section discussing if you are an active subscriber indicates that your written consent is needed before it's shared with unrelated third parties.
Third-party service providers: We may share your Personal Information with third-party service providers that we contract with to provide you with the Mazda Connected Services, as detailed in this Connectivity Privacy Statement.
The Artity (allstate) SDK offers some utility like "fuel efficiency tips", but it is a cover to collect data.
I can't recall the exact settings to push via ADB, but the Internet Connectivity Check is "easy" to fix. Create a server that's always up that responds with a 301 (or whatever the check expects), and push the address to the phone. Done.
It's a shame that Google's servers are the default, and I wish it were at least called out by Lineage. That said, I doubt they want to cover hosting costs of such a service (although I'd think they'd be fairly minimal).
This internet connection check actually caused problems for us when we started having users in China on android. Our code was checking for a connection before transmitting data and android thought the device was disconnected due to the great firewall. I think there’s just a hack around it for now that disabled the android connection check for those users.
LineageOS + microG here, on a motoX4. It's been the phone I use every day for about a year. My wife has the exact same setup, and generally gets along fine with it. FDroid has _most_ of the stuff we want. Some apps just aren't available there, so we end up using the Aurora store for those, with Warden used to scan those apps and stub out as much tracking code as it can. It's all about compromises, especially for others.
Self-hosted NextCloud replaced Drive/Dropbox, and with some plugins it also does phone/location tracking, secure messaging and video calls, TODO lists, and some more. Self-hosted PhotoPrism replaces Google Photos.
The phone experience hasn't been bad. One thing that came up initially is that most of the open source apps aren't as "pretty", and the UX just isn't as good. I don't care about it too much, and I'm fine with overall using the phone less anyway. The issue that comes up on a regular basis is the Google Maps replacement. OSMand is a great app, but like someone else mentioned it's more of a "look up the address and type it in" experience than a "show me all Thai restaurants in the area" experience. IMO small price to pay, I've been using GPS much less, and I've gotten much better at navigating with my "mental map".
More and more functionality is being shoved into Google Play Services. I have a deGoogled phone running Lineage, but even with that, no Google Play Services, and some custom settings (like changing the captive portal URLs), there's still network traffic to Google. Add in relative unknowns like AGPS and the situation gets even worse. I also have no push notifications for most apps, have to keep a static notification so Android doesn't kill apps like my email client, AND still run micro-G for basic functionality to work. Oh, and thanks to SafetyNet there are still apps that refuse to run, even with systemless "undetectable" root.
Android itself might be really good, but it's pretty obvious that deGoogled phones have a strong chance of being functionally useless in the future.
The ratio of available apps of Android without gapps over pinephone is still more than 1000 fold, despite SafetyNet or other reliances on Google.
For push notifications, microg does fill the gap, so I'm not sure what you're talking about. UnifiedPush is coming to fill this gap without violating Google's ToC, with self-hosting, and fully FLOSS. Is anything like that coming to PinePhone or Librem?
The Google phone-home "features" can be removed, and this is exactly the point of this thread. Android is opensource, you can control this platform however you want, especially removing all connections to Google services.
I'm guessing what you're saying is that you installed some custom Android ROM, and expected it to remove any Google tracker, but that's a wrong assumption, most Android ROMs don't target deGoogling.
Even my AOSP GSI, with FLOSS variant doesn't target removing Google phone-home features. Why? I don't approve of any data collection on Google's DNS, AGPS, or generate 204, which means it is illegal for them to use it to track me without my consent, and I believe that they are not total outlaws. Running a DNS, AGPS, or even generate 204 reliable infrastructure is hard.
> I have a deGoogled phone running Lineage, but even with that, no Google Play Services, and some custom settings (like changing the captive portal URLs), there's still network traffic to Google.
I'm running LineageOS without Play Services too and didn't about know this!
Do you have any reference materials (I guess getting busy with Wireshark and the source is my next step)? I found this Reddit thread[1] talking about a connectivity check but am keen to start tracking down any others.
I got my Pinephone last week, and have been fairly surprised that it's reasonably usable. I viewed the purchase more as a donation and a signal that there is a market, but I've been using it more and my Android phone less as the days go by.
I'd encourage more people here to purchase one, even if just to tinker with. There's so many "I'll buy one when it's ready" replies, but that may never happen if there's no money to fund the companies trying to make an alternative to Android/iOS.
You're correct insomuch as he's not sharing CFD settings, and is bound by what I assume is a pretty strict NDA, but he still has a ton of useful content. Of course, if you want his true opinion/skills on something specific, he'll do so for a price.
I had the same thought as the title of the article go through my head, but we ended up with a simpler setup as I wanted something I don't have to constantly mess with:
* Put together an overbuilt NAS box running ZFS On Linux
* Simple docker-compose file for all services
* Backups through borgmatic (via ZFS snapshots)
* Auto-updates through watchtower
* Punted on email and use FastMail, switched to our own domain from gmail
Services we run include:
* PhotoPrism for semi-Google Photos functionality
* Nextcloud and Collabora for file sync, sharing
* Kodi for home media
* Tiddlywiki
* DDNS through Gandi since we're on a dynamic IP
* PiHole for some ad/privacy protection
* Robocert for SSL
* Nginx to reverse proxy everything
It wasn't _easy_ to set up, but in a year, any given week I typically spend 0 hours dealing with it. No problem that _has_ cropped up has taken more than a few minutes to fix, mostly around docker networking and auto-restarting containers after Watchtower auto-updates them, a problem I've since fixed.
This setup seems way easier than k3s or some other recommendations, doesn't require much new knowledge, and is as portable as I need it to be. If needed I could plop the docker-compose on a new machine, change some mount points, and largely be up and running again quickly. It's let us switch to "deGoogled" phones and unplug from almost every hosted service we used to use.
We've been using Nextcloud in my home for the better part of a year now, almost completely problem free. I even have auto-updates via watchtower. We have 136 GB of data on it (just checked now). Not sure where that lies compared to your data. It is running on a fairly beefy box though, not a rPi. Only issues so far have been needing to set up cron, which took about 5 minutes doing it the "easy" way (host runs a docker command in it's crontab). Collabora was super annoying to set up, but that was a one-time cost.
Interesting. My volumes were similar and I even had issues with my 'beefy' enough DO VPSs. The primary issues for me were with the clients, especially if I, say, moved a folder of 2000 files from one directory to somewhere else within the Nextcloud drive using the UI. Anyway, I'm not here to troubleshoot that - I've long since decided that it's just too much for my personal simple use case of keeping two folders in sync with each other on different devices. Out of curiosity, how did you install Nextcloud? Snap/Docker/Manual?
Ah, during our migration we did try to move thousands of files from a "Dropbox" folder to a "NextCloud" folder, and indeed the Windows client was not happy. Since it was a one-time thing, the solution was to move the files "manually" over SSH and just run the NextCloud "scan" utility to pick up the changes on disk.
I'm running NextCloud via the official Docker image, reverse proxied through nginx.
My good old friend, the Nextcloud scan utility :) I lost count of the number of times I ran that and the trashbin cleanup. These are both problems I never ever want to have to deal with.
eh, I ran the command, alt-tabbed to something more interesting, and checked later in the day to see that it was done. Never had an issue running it, and only ever needed to when I was doing the initial data migration.
