You are not gonna protect abstract ideas using copyright. Essentially, what he’s proposing implies turning this “TGPL” in some sort of viral NDA, which is a different category of contract.
It’s harder to convince someone that a content-focused license like the GPLv3 protects also abstract ideas, than creating a new form of contract/license that is designed specifically to protect abstract ideas (not just the content itself) from being spread in ways you don’t want it to spread.
I don’t think we would be throwing USB-C away completelly, because it even became mandated by law in EU with the goal of trying to slow down the rate at which people generate trash by getting new cables and power bricks for every new generation of connectors.
But I agree that at the very least there should be a clear labeling mandated by consumer protection laws as well… it’s a nightmare and a scenario that opens the door for a lot of scams… this is even made worse by the fact that nowadays you can even have malicious software running inside of the connector of a cable plugged into an extremely capable port without realizing it, messing up with your device even though the only thing you wanted was to charge it.
I have something like this myself, it’s useful for knowing the power delivery of the cable/port combination, but I’m not sure if that really helps when it comes to determining the speed of the data transmission that the cable/port is capable of, or other features like displayport support, or which version of USB4 it might be supporting (I believe they have the same power delivery, even though the transfer speed is double).
This one is p2p: https://github.com/schlagmichdoch/PairDrop (or just try it in https://pairdrop.net/ )
But that also means that you need to keep the page open while the other device downloads.
Another p2p alternative is using webtorrent: https://instant.io/
Ah, I see. Sorry, the text was too long and I’m not dutch so it was hard to spot that for me too.
But I interpret that part differently. I think them saying that there’s an ambiguous section about risks does not necessarily mean that the ambiguity is in the responsibility of those who choose to not implement the detection… it could be the opposite: risks related to the detection mechanism, when a service has chosen to add it.
I think we would need to actually see the text of the proposal to see where is that vague expression used that she’s referring to.
It seems the reason companies are currently allowed to do this in the EU is because there was in 2020 a temporary derogation from certain provisions of the e-Privacy Directive.
But it was temporary, so it will expire in April 2026. With this new law the intention is to make that “voluntary detection” a permanent thing they allow service providers to do, as a norm. The providers still have the choice to not do it, so I don’t think this affects services like signal, as far as I understand.
Thanks for the link, and the clarification (I didn’t know about april 2026)… although it’s still confusing, to be honest. In your link they seem to allude to this just being a way to maintain a voluntary detection that is “already part of the current practice”…
If that were the case, then at which point “the new law forces [chat providers] to have systems in place to catch or have data for law inforcements”? will services like signal, simplex, etc. really be forced to monitor the contents of the chats?
I don’t find in the link discussion about situations in which providers will be forced to do chat detection. My understanding from reading that transcript is that there’s no forced requirement on the providers to do this, or am I misunderstanding?
Just for reference, below is the relevant section translated (emphasis mine).
In what form does voluntary detection by providers take place, she asks. The exception to the e-Privacy Directive makes it possible for services to detect online sexual images and grooming on their services. The choice to do this lies with the providers of services themselves. They need to inform users in a clear, explicit and understandable way about the fact that they are doing this. This can be done, for example, through the general terms and conditions that must be accepted by the user. This is the current practice. Many platforms are already doing this and investing in improving detection techniques. For voluntary detection, think of Apple Child Safety — which is built into every iPhone by default — Instagram Teen Accounts and the protection settings for minors built into Snapchat and other large platforms. We want services to take responsibility for ourselves. That is an important starting point. According to the current proposal, this possibility would be made permanent.
My impression from reading the dutch, is that they are opposing this because of the lack of “periodic review” power that the EU would have if they make this voluntary detection a permanent thing. So they aren’t worried about services like signal/simplex which wouldn’t do detection anyway, but about the services that might opt to actually do detection but might do so without proper care for privacy/security… or that will use detection for purposes that don’t warrant it. At least that’s what I understand from the below statement:
Nevertheless, the government sees an important risk in permanently making this voluntary detection. By permanently making the voluntary detection, the periodic review of the balance between the purpose of the detection and privacy and security considerations disappears. That is a concern for the cabinet. As a result, we as the Netherlands cannot fully support the proposal.
It seems the article is misinterpreting things. It’s not that it’s “voluntary for individual EU states”… but rather “voluntary” for service providers. The service providers don’t have to implement this chat detection if they don’t want to.
The thing is that if they don’t pass something like this, then by April 2026 a bunch of current services that are already doing CP detection would be breaking the law, since the temporary derogation of the e-Privacy Directive will expire. But I don’t think this affects services like signal/simplex who voluntarily choose to not try to detect it.
Where is this explained? the article might be wrong then, because it does state the opposite:
scanning is now “voluntary” for individual EU states to decide upon
It makes it sound like it’s each state/country the one deciding, and that the reason “companies can still be pressured to scan chats to avoid heavy fines or being blocked in the EU” was because of those countries forcing them.
Who’s the one deciding what is needed to reduce “the risks of the of the chat app”? if it’s each country the ones deciding this, then it’s each country who can opt to enforce chat scanning… so to me that means the former, not the latter.
In fact, isn’t the latter already a thing? …I believe companies can already scan chats voluntarily, as long as they include this in their terms, and many do. A clear example is AI chats.
The thing is… that even if there are countries publicly rejecting this, once the infrastructure is in place and a backdoor exists due to it being enforced by some other country, how can you be sure it’s not being used / exploited?
Even in the (hypothetical) case that the government is not using it (regardless of what they might say to the public), I wouldn’t trust that this backdoor would be so secure that nobody else than a government could make use of it.
I believe Germany is now in favor of this new proposal, according to https://fightchatcontrol.eu/
Only Italy, Netherlands, Czech Republic and Poland are against. This seems to be based on “leaked documents from the September 12 meeting of the EU Council’s Law Enforcement Working Party”.
I’m not sure if that’d be what it’d look like… distributions are hardly ever that heterogeneous.
I’d bet all the GrapheneOS users would get together in their own corner and nerd out about their customizations.
For the record: 1 in 25 is 4% …the image gives (intentionally?) the illusion of the proportion being higher.
But I’d bet it’s a mix of 2 and 3.
Code being visible is not very useful if you can’t distribute it, extend it, expand it and improve it.
It’s meant in the sense of “underwhelming” (as shown by the follow-up comment the article references). It’s not incompatible to be surprised at how capable AI is (ie. being “impressed”) and at the same time be also unwilling to pay the costs / repercussions and want to ban / regulate it.
In this context, being deeply unimpressed with something is equivalent to calling that something “irrelevant” / “incapable”. If AI was no more impressive than it was before the LLM boom then there wouldn’t have been such a reaction against it to begin with. If anything, people being now opposed to modern AI is proof of how impactful AI has become.
Yea, but he’s (intentionally?) misrepresenting things… people are not “unimpressed” by AI, what they are is not interested in MS “agentic OS”, these are not the same things.
It’s irresponsible to hand in control of your machine to an AI integrated that deeply into the OS, particularly when it’s designed to be tethered to the network and it’s privately owned and managed by human entrepreneurs that do have the company’s interests as first and main priority.
Many Keepass clients have support for not actually deleting entries, and instead moving them to a “Trash” subgroup inside the kdb that is ignored when searching entries. Also they usually keep track of the history of changes to each entry, to make it non-destructive.
Coupled with Syncthing typically automatically creating backups whenever it encounters conflicting changes, I feel this should be enough, at least for me personally.
Yep. I just confirmed it… restarting Firefox seems to make the ID in https://demo.supercookie.me/ change. Thought as long as you keep Firefox session open the id will be the same.
I’m not sure if the links you reference are the whole story though, because they are talking about partitioning the cache per top-level domain, which I would expect wouldn’t have been enough, since the demo is specific to its top-level domain and it’s not necessarily about cross-domain id.
Those are open questions that I don’t think we can answer yet.
If you are asking if Valve did make changes there, I’m expecting the answer is likely no. They haven’t shown anything regarding KDE/desktop mode on the Steam Frame. And we have yet to see how exactly this is integrated with gamescope. But if the device does become popular and interest grows for Linux VR development, then I expect we’ll see people trying to make new VR environments for Linux (or adapt existing ones for VR).
However, given that Valve plans to offer ways to play non-VR games with the Frame, I expect one could add a nested wayland session as if it were a non-Steam non-VR game, so in the VR environment from SteamOS one could have a floating screen showing a traditional KDE session relatively easy, I would expect. And in that sense one could have a desktop VR environment standalone, in the Frame.
LLMs abstract information collected from the content through an algorithm (what they store is the result of a series of tests/analysis, not the content itself, but a set of characteristics/ideas). If that makes it derivative, then all abstractions are derivative. It’s not possible to make abstractions without collecting data derived from a source you are observing.
If derivative abstractions were already something that copyright can protect then litigants wouldn’t resort to patents, etc.