No such implication is there. All I said was serious negotiations, which given the state of facts entails the prospect of territorial concessions. I don't expect the negotiations would lead to a simple redrawing of the borders to take account of what each side materially holds at present. In fact, I don't have much of a preconceived idea of what such negotiations would be like other than I find it extremely unlikely that Crimea will return to Ukrainian control. That's the point of negotiation: finding out what the belligerents can live with.
With more sober assessments of the course of the conflict on both sides of the Atlantic, we may hope for a prompt attempt at serious negotiation and, if fate is kind, an end to the hostilities.
That NATO official has apologised about the form and lack of context, then restated that territorial concessions are likely:
But Jenssen did not walk back the idea that a land-for-Nato-membership deal could ultimately be on the table. If there were serious peace negotiations then the military situation at the time, including who controls what territory, “will necessarily have a decisive influence,” the chief of staff said.
But Ukraine is not a member. There is no reassurance required, or given, by NATO supplying non-members. In fact one could easily make the opposite claim: NATO depleting its own ammunition stores is doing the opposite of reassuring its members, by decreasing its own margins of safety.
As far as I can tell, Stian Jenssen apologised about the way the comment had been made and interpreted, but not about the substance. Specifically:
A day later, he gave an interview to the same newspaper, VG, that had reported on his original comments. “My statement about this was part of a larger discussion about possible future scenarios in Ukraine, and I shouldn’t have said it that way. It was a mistake,” he said.
But Jenssen did not walk back the idea that a land-for-Nato-membership deal could ultimately be on the table. If there were serious peace negotiations then the military situation at the time, including who controls what territory, “will necessarily have a decisive influence,” the chief of staff said.
So clearly at least some people in NATO consider that a peace deal may entail territorial concessions. Which like it or not is a realistic position to take.
At least it doesn't sound like they will have much diplomatic cover to do it. Such an invasion would very simply be a violation of, shall we say it, the rules-based international order(tm).
There's a surprising amount of that, not to mention... not sure whether to go into it but...
That said, there's also a few times when there's the same stuff on men by women, and, I think, on women by men. But since the Aiel wise ones and Aes Sedai alike are societies of women, well, there's a lot of that going on.
Worth considering that this is already the law in the EU. Specifically, the Directive (EU) 2019/790 of the European Parliament and of the Council of 17 April 2019 on copyright and related rights in the Digital Single Market has exceptions for text and data mining.
Article 3 has a very broad exception for scientific research: "Member States shall provide for an exception to the rights provided for in Article 5(a) and Article 7(1) of Directive 96/9/EC, Article 2 of Directive 2001/29/EC, and Article 15(1) of this Directive for reproductions and extractions made by research organisations and cultural heritage institutions in order to carry out, for the purposes of scientific research, text and data mining of works or other subject matter to which they have lawful access." There is no opt-out clause to this.
Article 4 has a narrower exception for text and data mining in general: "Member States shall provide for an exception or limitation to the rights provided for in Article 5(a) and Article 7(1) of Directive 96/9/EC, Article 2 of Directive 2001/29/EC, Article 4(1)(a) and (b) of Directive 2009/24/EC and Article 15(1) of this Directive for reproductions and extractions of lawfully accessible works and other subject matter for the purposes of text and data mining." This one's narrower because it also provides that, "The exception or limitation provided for in paragraph 1 shall apply on condition that the use of works and other subject matter referred to in that paragraph has not been expressly reserved by their rightholders in an appropriate manner, such as machine-readable means in the case of content made publicly available online."
So, effectively, this means scientific research can data mine freely without rights' holders being able to opt out, and other uses for data mining such as commercial applications can data mine provided there has not been an opt out through machine-readable means.
Well, in a way that's what we're doing now, and by and large it works but obviously there's some leakage, which is impossible to bring down to zero but which makes sense working on improving.
The other side of the coin is that the price of this moderation model is subjecting a lot more people to a lot more horrible shit, and I unfortunately don't know any way around that.
Perhaps the manual reporting tool is enough? Then that content can be forwarded to the central ms service. I wonder if that API can report back to say whether it is positive.
The problem with a lot of this tooling is you need some sort of accreditation to use it, because it somewhat relies on security through obscurity. As far as I know you can't just hit MS's servers and ask "is this CSAM?" If something like that were possible it might work.
Can you elaborate on the hash problem?
Sure. When you have an image, you can do lots of things to it that change it in some way: change the compression, the format, crop it, apply a filter... This all changes the file and so it changes the hash. The perceptual hash system works on the basis of some computer vision stuff and the idea is that it will try to generate the same hash for pictures that are substantially the same. But this tech is imperfect and probably will have changes. So if there's a change in the way the hash gets calculated, it wouldn't be enough with keeping hashes, you'd have to keep the original file to recalculate, which is storing CSAM, which is ordinarily not allowed and for good reason.
Some of this is probably inevitable in this type of systems. You don't want to make it easy for someone to hit the servers with a large number of hashes, and then use IPFS or BitTorrent DHT to retrieve positives (you'd be helping people getting CSAM). The problem is hard.
Personally I was thinking of generating a federated set based on user reporting. Perhaps enhanced by checking with the central service as mentioned above. This db can then be synced with trusted instances.
Something like that could work, maybe obscuring some of the hash content (random parts of it) so that it doesn't become a way to actually find the stuff.
Whatever decisions are made have to be well thought through so as not to make the problem worse.
Clearly this particular suit by this particular person is iffy. However, I don't think this framing is very good: the fact Wikimedia is headquartered elsewhere shouldn't make it immune from being sued where an affected party lives.
Also, this part of the article seems a bit contradictory:
Just because someone doesn’t like what’s written about them doesn’t give them the right to unmask contributors. And if the plaintiff still believes he’s been wronged by these contributors, he can definitely sue them personally for libel (or whatever). What he has no right to demand is that a third party unmask users simply because it’s the easiest target to hit.
Ok, but how does he sue them personally without knowing who they are? It's fine to say this shouldn't be regarded as libel (I agree, it's a factual point, should be covered by exceptio veritatis or whatever) but I think it's a bit dishonest to say you can't hit Wikimedia, go after the individual users; but also, Wikimedia shouldn't be forced to reveal them.
Much better if the court would consider this information as being accurate and in the public interest.
Of course the GDPR cuts two ways here, because political information is an especially protected category, with certain exceptions (notorious information). So I'm not sure how the information on this person's affiliation to the far right was obtained and so on.
IMO the hardest part is the legal side, and in fact I'm not very clear how MS skirted that issue other than through US lax enforcement on corporations. In order to have a db like this one must store stuff that is, ordinarily, illegal to store. Because of the use of imperfect, so-called perceptual hashes, and in case of algorithm updates, I don't think one can get away with simply storing the hash of the file. Some kind of computer vision/AI-ish solution might work out, but I wouldn't want to be the person compiling that training set...
I generally agree, though I could be convinced of recurring payment in the case of high speed APIs that need a lot of updates to keep working. Chasing an API can be a lot of work.
Of course, a solution to that is having an up-front payment and letting people update as they wish--if there's new value in the new releases presumably they will.
There were points at which Firefox was difficult to stick with, especially after the extension apocalypse, but I think it's evolving pretty well at this point.
No such implication is there. All I said was serious negotiations, which given the state of facts entails the prospect of territorial concessions. I don't expect the negotiations would lead to a simple redrawing of the borders to take account of what each side materially holds at present. In fact, I don't have much of a preconceived idea of what such negotiations would be like other than I find it extremely unlikely that Crimea will return to Ukrainian control. That's the point of negotiation: finding out what the belligerents can live with.