I wonder how this is treated in terms of consent (at least from a GDPR perspective in the EU), even if I gave my data to Spirit, I did not consent to it being shared with Google unless they explicitly said they would share it with that partner and I agreed. Surely they can't just retroactively change the scope of consent for data sharing?
Coming from Rust anyway (can't say I'm familiar with Go), nothing about having it as a trait would pollute the method set, traits don't have to have methods (e.g. pin, unpin, send, sync, etc.). Yes a zero length field can be metadata and this is a style complaint but a struct's fields are traditionally its data and the type is its metadata, I feel like it's harmful to mix these two as I at least wouldn't generally look at fields to find metadata for the struct.
The lack of mudguard wouldn't be an issue, almost no mountain bikers fit them to their bikes. There may well be enough space in the frame without a bottle cage to attach it given it's incompatible with full sus bikes anyway, so that may not actually be an issue, could always shove it in a backpack afterall.
The biggest issue to me is the inability to put the seat all the way down given that's quite important, and obviously this won't work at all with a dropper post (which are fairly common nowadays), honestly actual ebikes are quite popular in the mountain biking scene at the minute and they seem like a significantly better fit to me.
I wonder how much torque the motor could put out though without putting a lot of wear on your (probably fairly soft material on mtb) tyres or slipping on knobby, possibly dusty/muddy, tyres; that itself might kill it off for offroad climbing.
I'd be quite worried about breaking it in the not unlikely event of a crash, additionally it looks like it could quite significantly limit how low you could put your seat down on a mountain bike, so that would get in the way. Even if you got your seat down, it would add a significant amount of height above the tyre so you mighn't be able to move your arse far enough back to shift your weight property. It's also adding nearly 4kg weight relatively high up which probably isn't the end of the world but would be better if it wasn't so high up.
It says on the website it will fit hardtails but not full sus, and that it isn't recommended on knobby tyres due to performance which isn't ideal either.
I could be wrong on all of this but those are just the concerns coming to mind as another mountain biker.
Confusingly the proper term for England, Scotland, Wales, and NI is country individually, the UK is a country of countries. They should probably be called states but they never have been, I'd pretty much always assume when someone says England to become the first country... that they mean England exclusively.
The bit that gets me is that people often refer to the UK but actually mean GB or vice versa.
I've come to the conclusion that I actually really like Android as an operating system, the internals seem remarkably well thought out and ideal for the mobile use case (so long as you're running a userdebug build with the ability to adb root in when needed), most of people's issues aren't really with Android (although Google reducing the AOSP release schedule isn't a good sign).
I think the real problem is Google Play Services. It's far, far too tightly integrated in a way that it just seems like Android was designed to be unusable without. It's installed as a location manager internally, which gives it a shitload of permissions by default that you never grant it. There's absolutely no reason everything (notifications, the app store, some location services) has to be packaged together into one thing instead of each having its own module that can be removed at will. Play integrity just plain shouldn't exist and as far as I'm concerned is purely there to ensure no one creates a real play services alternative or another mobile OS with Android compatibility.
The ideal outcome for me would be keeping Android but effectively dissolving Play Services and instead having the concept of a core services, where instead of apps choosing to use Firebase for notifications, they instead bind to the system notifications service, and as the user I choose which implementation I want, preferably with it not installed as a system app. I'm well aware that's not going to happen, but it seems like the most practical way to break up the Google/Apple monopoly to me, Android's great but Google's services aren't.
Pretty much, my car doesn't have navigation built in but supports android auto. I've tried a phone mount before but the experience is so much worse when it's not integrated with the car (volume of announcements and music can't be done independently, can't switch what music/podcast app's playing without grabbing my phone, etc) that I just went back to using it.
AOSP allows the internet permission to be denied per app (hence LineageOS and Graphene exposing it), it's just most OEMs ROMs don't expose it, you can draw your own conclusions from that.
For me to fully drop google someone needs to create something compatible with Android Auto in my car, it doesn't sound like a big deal but that's a big enough thing for me to need it now.
It also solves the issue of potentially not knowing when the author died, with a fixed period (the number isn't so important imo so long as it's sane), a work is out of copyright x years after the first known copy was published.
Don't underestimate the argument of "just to be on the safe side". Someone running a business who doesn't know a lot about cookies will often just put a banner on as an easy arse covering mechanism even when not required.
I gave up on it years ago when they killed off 3rd party clients, I have to say it doesn't seem like I've been missing much. The rare occasion I do need to see something on it, it's just full of deleted accounts and comments. I do also love how VPNs get blocked but accessing it over tor is allowed (genuinely I think allowing access over tor is great, but it seems so antithetical to everything else they've done recently)
I'm trying to use lineage at the minute, but xiaomi has made it next to impossible to even unlock the bootloader on my phone, and even then I'd likely need to move at least one of my banks as I seem to remember it not working on lineage, and I'm the target audience for a custom rom. For mass appeal it needs to be much easier, and without any compatibility issues with stock android. I cannot believe it's somehow standard to not allow bootloader unlocking on a device owned by the user, I am fully aware of the risks of it but phone companies insist on treating me like a complete idiot.
I'd personally rather have E2EE and periodically back things up to an encrypted hard drive so any losses aren't catastrophic, but I am probably more cynical than most in my trust of companies/other people with my data and am technical so understand the risk model both ways better than most people.
Thr one solution I see to that is sponsorships, the number I've heard is they typically pay 10x the ad revenue of a video, and this wouldn't be affected by the platform, just the viewership numbers.
The starter motor turns the engine in a defined direction, this acts as a turning force directly on the crankshaft so it doesn't matter where the crankshaft is. The pistons only start firing after the crankshaft is already moving.
It is actually possible for an engine to turn the wrong way, this occurs on motorbikes with kick starts. When you don't kick start it correctly (or if the ignition timing is way out), a piston can fire prematurely before top dead centre and force the crankshaft against the direction that the kick lever turns it, this is known as kick back and is about as fun as it sounds when the engine's force goes through the kick lever.
AOSP has network as a regular permission for apps, so on Lineage at least (idk about Graphene as I haven't used it) you can disable network for any app including google play services etc. I have no idea why most phone companies remove this permission from their roms but android itself supports it perfectly fine.
The PKGBUILD files specified npm as a dependency, so it would've been installed prior to installing the malicious file, so not having npm is by no means a guarantee.
To be fair in this case it looks like npm was used as a way to run arbitrary code in a way that wouldn't look out of place immediately in a PKGBUILD file. All of this could have been done from within the install hook or anywhere else really in the PKGBUILD, it would've just been more obvious at a cursory glance if there was now randomly a curl | bash in the file.
Tools exist (e.g. pkgctl) to allow you to test building and installing the package on a clean image to catch these kinds of things, maintainers should really be using these before publishing.
In my experience as someone who rides a bike with hydraulic disc brakes and drives frequently, they really don't stop very quickly. I pretty much always am more confident I can stop my car faster. The bike may have a lot less mass but it also has a lot less traction and it's much easier to lock up a wheel and skid instead of stopping quickly, especially in poor conditions/on road paint. I do cycle fairly fast, but this is on a mountain bike on the road, certainly not fast compared to a fit person on a road bike.
I will give you that they're much more maneuverabile and accidents can often be avoided by putting the bike into a space in the road that a car couldn't go into.
You say it requires a little acclimatisation, but the caller may well just not know anyone with that specific accent/have never had the chance to acclimatise to it other than this phone call, there's an awful lot of accents in the world.
Additionally I find even though I can understand an Indian accent for example quite well in person, I really struggle with it over the phone due to the compression causing quite poor sound quality and lack of facial expressions to be able to read (which I would be using in person to help me understand a strong unfamiliar accent), whereas when accent is more familiar to me, the poor audio quality and lack of body language isn't nearly as much of an issue, presumably as I just have way way more exposure to the accent so can fill in gaps better.
The whole thing with GPL code seems like a mess and surely couldn't be set as actual precedent, right? It is totally infeasible for me to check every single GPL project on every code hosting platform to see if the code Claude etc produced is too similar. If a set of training data used for the model was released to check against that would be one thing, but you can't honestly expect someone to check every repo available from all time to see if a model (that you are not informed of what it was trained on and therefore could reproduce) might've reproduced code from it.
That's not at all like checking the dependency chain of a dependency or anything as you can just read the licence of anything you're choosing to use. Surely the precedent would have to be that a model trained on GPL code has itself been infected by GPL, and therefore must have all source/weights released too if the assumption here is that it can have embedded the code well enough to be able to reproduce it?
It sounds like the real solution to this is to be able to control permissions at an OS level for network per app, as you would be able to do if you had root access. I have no idea why regular Android distros don't allow you to do this, it seems like a really sensible thing to expose in app settings given the permissions model of Android.
The difference I see there is any line in a C codebase could have these issues, whereas in Rust they're specifically marked as unsafe sections, with the language having a clear list of invariants it expects the programmer to uphold in an unsafe block. Additionally Rust has a culture of developers specifically justifying the unsafe block and why it's correct in comments. It's a massive reduction of the scope of the code that needs audited, that doesn't mean there can't be mistakes in it, just that it's easier to verify certain properties of the whole codebase.
What all these breaches tell me is that personal data should not be required, and especially not stored unless absolutely necessary. I cannot verify how my data is treated once it leaves my device, so how can I possibly trust it will be treated properly and not leaked?
This is a major reason as to why I am so strongly against all this verification shit governments keep trying to push, the best way to keep data secure is not to have it in the first place, therefore my personal data should not leave my device except in the strictest of circumstances for things like my name/DOB/address/SSN.