To be fair I see two separate ways CS students use LLMs, one is to just complete assignments in the same way you could by asking someone else to do it, the other way is by getting an LLM to explain certain concepts in another way, or create more examples of them to aid in understanding quicker/in more depth. I actually think in the 2nd case they can be incredibly useful and can assist in creating a deeper understanding, but in the 1st case they obviously create fundamental gaps in understanding.
In a way it's on the student to make sure whatever they're doing, they actually understand it, or come exam season the gaps in their knowledge sans Claude will become quite obvious.
There's not much of a fissure in Ireland, the consensus there is pro Palestine. They see parallels between how Israel is treating the Palestinians and how the UK treated Ireland. Generally they don't view the bigger country next door trying to take over a smaller country favourably, and that's even without the mention of the word genocide which certainly doesn't help Israel's case.
Enigma wasn't one time pad based (although these were used a lot during the war), enigma does have known weaknesses such as letters never being decrypted to itself. Enigma was based off daily settings (rotor positions, plugboard settings etc), which could be mostly recovered by the end of the war, unlike actual one time pads which are only crackable by bad key hygiene/brute force.
How would that work for things like films or music when it genuinely is a group of people making something? I agree that copyright is way, way too long and should be a fixed length, but there's definitely a use in corporations being able to hold it.
As someone from outside the US, I had only heard of coaster brakes from this article. As a child all my bikes had rim brakes and now my bike has hydraulic discs, coaster breaks seem very strange to me.
I use Auxio from F-Droid. It's quite simple (which to me is a benefit) and my only real complaint is how similar shuffle on and off look on Android Auto. It handles non ASCII titles correctly where some others didn't (from what I remember due to weirdness with the Android media store) and it picks up new media/edited quickly and reliably which can be a sore spot with others. I don't know how Android's media store is apparently so incompetent that most music apps don't work correctly using it.
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.