fsck almost certainly isn’t going to cause loss of data, but it will likely inform you about a loss that already occurred if that is the issue you are having.
fsck almost certainly isn’t going to cause loss of data, but it will likely inform you about a loss that already occurred if that is the issue you are having.
Yeah but also this is only for their EU profit, so it’s really an even higher percentage.
It doesn’t really make sense to talk about money they made in other countries when talking about these fines, as if they make 5 billion in profit in country X and get fined 6 billion, they would still have lost money for operating in the country regardless of how much money they made other places. Since they lost money in the country, that fine would be high enough for them to want to fix their law breaking or totally pull out of the country, and so the fine accomplishes its purpose.
I’m pretty sure that it’s true that citing sources isn’t really relevant to copyright violation, either you are violating or not. Saying where you copied from doesn’t change anything, but if you are using some ideas with your own analysis and words it isn’t a violation either way.
I would still say that getting people to the point where they can write safe C code every time is harder than learning Rust, as it’s equivalent to being able to write rust code that compiles without any safety issues (compiler errors) every single time, which is very difficult to do.
This is a growing problem due to climate change (higher temperatures seem to increase arsenic uptake) and pollutants, so this doesn’t make any sense.
Voyager works great for me.
I’m not sure when you were using it, but Navidrome definitely let’s you play individual songs and shuffle.