> Can the EU sign treaties that are binding on all member countries?
That depends on the topic of the treaty.
The EU member countries have delegated their decision making powers on certain limited number of topics to the EU institutions, like The EU Commission, The EU Council or possibly others. One such topic is the trade. As a result, all EU countries share the same trade policy.
For other topics, where there is no such delegation in place, everything needs to be ratified by every member country individually.
I am unsure into which category this particular treaty falls.
> You can't fence off the sidewalk and claim that someone trespasses when they walk on it.
Perhaps a better analogy would be:
If you go out into a public space, you have to accept that by doing so you lose a certain portion of your privacy. You cannot expect that other people will agree to your "terms and conditions" before being allowed to talk to you. They will just talk to you if they so like.
Are you implying that if a US "service" consists of e.g. publicly accessible HTTP endpoints, it is illegal to use these endpoints in the US without "accepting" some terms and conditions that the provider of these endpoints requires its users to accept before using them?
I do not understand how such a requirement would be legally enforceable for public endpoints.
You can reasonably assume that if no terms and conditions were offered, then your use of a publicly accessible endpoint is authorized.
But if terms and conditions ARE offered to you, and you bypass acceptance somehow, then you're knowingly accessing the system without being authorized.
I really doubt this would be prosecuted except as part of some much larger misbehavior, but it is there.
If I use wget to mirror a site and there are terms and conditions that I never see then I'm "using a public facing API while being unaware of terms and conditions".
I mean, the CFAA being discussed is a notoriously broad law that's far too easy to run afoul of without realizing it.It's totally possible a court could seem that illegal.
Simply violating a TOS is not a federal crime, as long as it doesn't circumvent a technical barrier like a subscription wall. This is a new SCOTUS interpretation of the Computer Fraud and Abuse Act as of 2021, in Van Buren v. United States.
That's a different situation. Those urls weren't meant for public use, and provided private information on user devices.
Furthermore, on reading the wikipedia page, his conviction was vacated.
> On April 11, 2014, the Third Circuit issued an opinion vacating Auernheimer's conviction, on the basis that the New Jersey venue was improper,[60] since neither Auernheimer, his co-conspirators, nor AT&T's servers were in New Jersey at the time of the data breach.
> While the judges did not address the substantive question on the legality of the site access, they were skeptical of the original conviction, observing that no circumvention of passwords had occurred and that only publicly accessible information was obtained
Much less active than it used to be when it was run by Hector Martin. The core development is a lot slower. Although the graphics stack, for instance, has reached a very mature state recently.
> Is it ready as a daily driver?
It depends. Only M1 and M2 devices are reasonably well-supported. There is no support for power-efficient sleep, Display Port, Thunderbolt, video decoding or encoding, touch ID. The speakers overheat and turn off momentarily when playing loud for a longer period of time. The audio stack in general had to be built from ground up and it seems to me like there are bits and pieces still missing or configured sub-optimally.
> Is it getting support from Apple?
Not that I am aware of.
> are they (Apple) hostile to it?
Not to my knowledge.
> Are there missing features?
Plenty, as described above. There has been some work done recently on Thunderbolt / Display Port. Quite a few other features are listed as WIP on their feature support page.
> Can I run KDE on it?
Of course. KDE Plasma on Fedora is Asahi Linux's "flagship" desktop environment.
"power-efficient sleep" refers to discharging 1-2% battery over night rather than 10-20%. I.e. there's room for improvement, but the device can still be used without worrying much about battery life regardless (especially given how far a full charge gets you even without sleep).
> Display Port, Thunderbolt
Big item indeed, but it's actively worked on and getting there (as you mentioned).
> video decoding or encoding
Hurts battery performance, but otherwise I never noticed any other effect. YMMV for 4K content.
> touch ID
Annoying indeed, and no one has worked on this AFAIK.
> The speakers overheat and turn off momentarily when playing loud for a longer period of time. The audio stack in general had to be built from ground up and it seems to me like there are bits and pieces still missing or configured sub-optimally.
Sad to hear since I thought the audio heat model was robust enough to handle all supported devices. On my M1 Air I've never seen anything like this, but perhaps devices with more powerful speakers are more prone to it?
My experience is also based on a M1 Macbook Air. I have repeatedly experienced sudden muting of the speakers for a second or two while playing conversations on a high volume.
I only assume it is caused by thermal management of the speakers but I did not actually verify it.
Perhaps check if there are any log files in /var/lib/speakersafetyd/blackbox. The fdr files in particular contain human-readable error reasons. If there are no log files, it's probably something else.
Am I misrepresenting the situation or did the whole project seemingly fall apart over an argument between Hector and Linus Torvalds in the mailing list about getting some driver merged?
I would consider that to be a misinterpretation. The whole project did not fall apart because Hector Martin left. But as with any project where the leaders depart, it definitely got slower.
The argument was originally about merging some Rust code into some parts of the Linux kernel if I remember correctly. It did not involve Linus Torvalds directly. Rather, the respective maintainers of those specific parts were unwilling to merge some Rust code, mostly because they did not know Rust well and they did not want to acquire the responsibility to maintain such code.
I do not see a rational reason why a mobile carrier should have any say in which connectivity technology is enabled for use with its mobile network on a particular phone model.
It should work based on standards, mobile carrier's capabilities and phone's capabilities. If a phone supports capability X, such as VoLTE, then it should just work with all mobile carriers that support that capability. No conditions.
As an imperfect analogy, consider a road, representing a mobile network. This road has some capabilities, such as speed limit. There are cars driving on this road, representing mobile phones. And then consider that a road management company, representing the carrier, would impose different speed limits on different cars, depending on whether they are affiliated with the road management company or not.
Would that be acceptable in a physical world?
If not, we should not accept anything similar in a digital world either.
The official reasoning is that the spec documents and certification testing aren't good enough, and each cellular cores has each its own quirks, interpretations, parameters, and they don't know if the phone is compatible with each networks unless Carrier Acceptance/Inter-Operability Test is done at carrier certified tests.
So why not actually perfect the spec and cut those uncertainties and costs...? idk.
It's not even the mobile carrier that has a say, it's just Google. If Google doesn't sell the phone in a country, they just disallow the feature for everyone, instead of just allowing it as long as the carrier supports it. The carrier doesn't mind (if they did, they'd block by IMEI and the workaround wouldn't have worked)
Depends on how the rollout of mobile networking historically went in a particular country. (Mostly, from what I can see, if it was the entrenched landline monopolists from the start or if they had to outcompete a few upstarts first.) In some places (Russia, Ukraine) you have to explain to people what a carrier-locked phone even is, and they get (understandably) appalled at the concept. Others (Turkey) have went as far as to have infra to IMEI-block you after you spend too much time in the country until you pay up.
> whitelist/blacklist phones depending on extensions available
That would be, I believe, fine. Those are capabilities-based restrictions.
From my point of view, the issue would be if the same phone worked with the same technology over the same mobile network when connected via a carrier A but the same phone on the same network refused to work with the same technology when connected via a carrier B.
> From my point of view, the issue would be if the same phone worked with the same technology over the same mobile network when connected via a carrier A but the same phone on the same network refused to work with the same technology when connected via a carrier B.
But thats the whole point of carrier profiles ( If I didn't understand wrong. )
Eventually it is the carrier who decides what you can do. ( this can also may be related to deals they made with manufacturers )
I think in this case, it is just missing carrier profile. ( which is like a config file )
> As an imperfect analogy, consider a road, representing a mobile network. This road has some capabilities, such as speed limit. There are cars driving on this road, representing mobile phones. And then consider that a road management company, representing the carrier, would impose different speed limits on different cars, depending on whether they are affiliated with the road management company or not.
> Would that be acceptable in a physical world?
A number of cars on the road today can be remotely disabled by a device built-in to the car.
While personally I think this is risky, in the U.S., we also have police, sheriffs, highway patrol, M.P.s and others that have authority to tell other cars to stop or to physically stop them, which is just another way of doing the same thing. They also enforce speed limits.
So, no I don’t think that the ability to drive a vehicle as fast as one would like is a global right, per current laws.
In general I do not think that a research which does not lead to a full resolution of the primary issue can be dismissed just because it does not actually resolve the issue.
Every step of the way towards the resolution of the issue is important. Even ruling out what does not work is important.
Without those incremental advancements, we may never reach the end goal.
Of course we should try to learn from past research.
But sometimes the lesson to be learned is that what we were is a bad approach, and we need to rethink things. We can't simply run experiments and get results. We also need to study whether our experiments are telling us what we think that they are telling us. Because if we don't know what our experiments are actually telling us, we're going to misunderstand the results.
https://people.cs.uchicago.edu/~ravenben/cargocult.html is worth a read on this. Among other examples, it includes an explanation of what actually has to be done in order for a rat running a maze to actually test the rat's memory. And how it is that we know that this is what has to be done.
The fact that psychologists ignored that experimental procedure marked psychology as a cargo cult science. (Some 40 years later, the replication crisis forced psychologists to at least talk about the issues that Feynman raised...)
The fact that we continue testing animal models of Alzheimer's that we have proven to be a bad model of humans, likewise shows that Alzheimer's research has become a cargo cult science.
>The fact that we continue testing animal models of Alzheimer's that we have proven to be a bad model of humans, likewise shows that Alzheimer's research has become a cargo cult science.
Partially. It also, more primarily, shows that medical funders and ethics committees demand very strong evidence in one animal model before they allow you to move a step "up the ladder" towards humans. What you can test on mice, you haven't managed to get approval to test in nonhuman primates. What you can test in nonhuman primates, you might get approval to test in humans. What you can test in humans, might finally prove useful for treating humans.
But the broad assumption is that if something fails in mice, we can know it would have been unethical to try it on humans first.
When I encounter a website which does not allow text selection, copying or right click, I usually enable the "Absolute Enable Right Click & Copy" browser extension which removes all of these restrictions.
Such restrictive practices, in my opinion, not only make the website less useful to the user. It also intentionally alienates its users.
I cannot think of a rational reason to do something like that.
Only the tinkerer-type techies. Most people don't understand why right click doesn't work, they don't have a mental model of what is responsible for what and things are often broken in mysterious ways anyway. If users are not alienated by how the web looks without an adblocker (try it once on some mainstream news site or blog or recipe site!), they surely won't be alienated by unselectable text.
The rational reason is to avoid getting their content "stolen", or having the user leave the site to do something else with the saved content.
Anecdotal: I am surprised how the basic Tesla autopilot often cannot even read the speed limit signs correctly. In perfect lighting conditions. It just misses a lot of them. And it does not understand the traffic rules enough to know when the speed limit ends.
I know that the basic autopilot is a completely different system than the so-called FSD.
But equipped with that experience from the basic autopilot, it does not surprise me that a large debris on the road was completely missed by the FSD.
In FSD, there's an annoying bug where Georgia minimum speed signs are misinterpreted as speed limit signs. It's because most states that do minimum speed signage combine it with the speed limit into a single sign, but Georgia has separate, freestanding minimum speed signs. Thankfully, recent versions of FSD don't immediately start slowing down anymore when a misinterpreted sign makes the car think that the speed limit on a highway is 40; but the sign comprehension bug has remained unresolved for years.
It is unclear if it can even read signs at all. FSD, not Autopilot, on the current version can not read “Do Not Enter” and “Road Closed” signs and will entirely ignore them. It would be reasonable to assume it can not read any signs at all. But it will be safer than a human driver in just negative 9 years.
I use autopilot for local driving (city - suburbs) and I pay for FSD when on long road trips (>300 miles). You are correct, they are completely different things so one doesn’t correlate to the other one.
That they are different things is really disappointing. If you want people to trust the system enough to buy FSD, the autopilot mode should use the same system, with limited functions. There is no reason why the vision/detection systems should be different. Especially if you already have the proper hardware installed…
You mean like it has become a mistake when the story about it broken up and went viral?
But if Hack Club did not complain about it, you would have happily took and kept taking their money?
That kind of a "mistake"?
In all seriousness, why should anyone believe what you are saying?
It seems to me that your story about a "mistake" is just as plausible as this kind of behavior simply being Slack's business strategy. Be ambiguous. Change the terms of the sale after the sale. Try poking. See which tactics works. If someone bites, take advantage of it. If they complain, call it a mistake and do damage control. Collect profits. Rinse and repeat.
In my opinion it is unclear what you are referring to because many people have different views on what the term piracy actually means.