Same reason copyright abusers threaten people that help remove the DRM from their Amazon-bought e-book so it can be read on their non-Amazon bought e-reader with a $250,000 fine and five years in prison for circumventing a digital lock using DMCA, because it's what the legal API allows them to achieve their end goal.
It's not about if it makes sense from a moral point of view.
The same method is used to block sites that don't respect the decisions the French people have made regarding the limits of the freedom of speech (no hate speech, no terrorist proselytism, no pedo, etc.).
Granted, that's the theory.
When the demands come from a company on the basis of copyright/intellectual property (that is, exclusive broadcasting rights), one can feel less comfortable about this affair; even thought the judgement mentions that the case is backed by the ARCOM, the french authority for broadcasting, which should instead IMHO deal with a couple or two of private TV channels that are obvious vectors of fake news.
But, this is the same copyright that can protect you when you publish programs, source code, images, etc., even when you use a free and open license; the licence has meaning thanks to the copyright.
You raise good, classic points when defending copyright. I would argue that your first examples are for the good of society, and the individual copyright protections are for the good of small creators.
Copyright enforced at this scale, for the profit of a corporation that streams their content off the infrastructure paid for by the public, does make one less comfortable.
And exclusive broadcasting rights… why is that a thing and conflated with copyright regulations? Why would the public regulator charge, say, 1M€ for the steaming right to something that will net 20M€ in advertising? That’s not really about copyright, I’d argue that it’s actually the job of the public channels to stream this content that takes place on stadiums built with public funds, streamed via a largely public TV system, etc.
I suppose the work against sports piracy is profitable enough to continue. Canal+ makes quite a lot of money, and their subscription in France is pricey compared to most other services.
They could, for starters, split the sports bundle and lower its price. Lots of people would probably pay a little bit to watch sports in 4K, instead of hunting for shady streaming websites that do 720p at best.
The most likely answer is that they didn't think about it or didn't understand or didn't care. But on the off chance they did, perhaps they thought the DNS provider would enforce the ruling worldwide.
It shows maliciousness (we can bully this smaller player for a win) and/or total incompetence (we don't even understand how internet works, but we'll issue rulings anyway).
I believe the position of the French government is that anyone in the path of a crime can be ordered to block the part of the crime that relates to them, without having any liability for the crime. So quad9 are not criminals for not blocking pirate sites, but still have to block specific sites when ordered.
Where does this line of reasoning end though? Shouldn’t the browser makers be blocking the sites too? What about curl? What about the OS and local DNS resolvers (unbound etc)? Maybe Ethernet and wifi cards should contain blocking logic? At some point you have to draw a line!
The way it worked is that the French government forced all major ISP to block some sites.
But using a third party DNS circumvents the block, so they went after them too.
Web browsers however (unless they include a VPN or 3rd party DNS) don't allow you to access sites blocked by your ISP. Same goes with ethernet and wifi cards.
I'm not saying I agree with it but that's the logic.
Right, but many browsers include a VPN. Tor Browser bypasses any such blocks. Many browsers also let you set your own DNS servers, so you could pick one that allows circumvention. Same at the OS level, and some OSes come with built in VPN clients. I guess I just don’t see how this stops here, unless legislatures step in to limit the scope. It’s an insane theory of liability that makes all steps in the chain liable for anything bad that end users might do.
I think there's at least one clear line between DNS providers and your examples. In your examples the enjoined parted is providing being a tool - a thing someone else uses - not a service where the enjoined party themselves does the thing.
It's one thing to say that you can't CNC machine guns for customers of your CNC-on-demand service, it's another to say you can't sell CNC machines because someone might use them to make guns.
Here the DNS service is being told they can't direct traffic to pirate sites, not that they can't give out tools (e.g. browsers or local DNS resolvers) that could be used by someone else to direct traffic to pirate sites (or could be used innocently). Your examples are all the latter - tools.
> It's one thing to say that you can't CNC machine guns for customers of your CNC-on-demand service, it's another to say you can't sell CNC machines because someone might use them to make guns.
And yet some places (California for instance) are attempting to do just this by requiring some kind of vaporware AI mediator to review files before the machine operates. Intermediary liability is out of control.
While I'm no fan of that law, it isn't a case of intermediary liability. It's a case of legislators (in a baffling move) deciding that selling 3d printers (and I guess CNC mills?) without vaporware attached should be directly illegal, much like most of the world has decided selling guns should be directly illegal, regardless of how they are used.
It's not illegal to sell these because it would be illegal for the end user to make a gun with them (it might or might not be - but is irrelevant) - it's just illegal to sell them because the legislator said it is.
It’s not the same legal conception of intermediary liability as with online services, but I’d argue that it’s an extension of the same idea. The manufacturer has somehow been conceived as a legally vulnerable intermediary between the user and the printed/milled product, and the legislature is attempting to force them to interfere in the manufacturing process, with the threat of liability as a club.
This same trend is happening all over, from banking to communications to manufacturing, where private industry is deputized by force to police consumer behavior, without consumers receiving any of the usual protections provided by the legal process. We’re effectively witnessing the construction of a privately mediated police state.
The line is drawn wherever a particular judge decides it's drawn, and each judge has a different ability to understand the broader implications of the line being drawn on any individual case.
If phone book publishing were regulated in a way that paid content on the internet is regulated, then absolutely yes. Not only that, people who mention the existence of phone books as means to obtain phone numbers, and people developing software capable of storing phone numbers, would be threatened and harassed too, as enablers of criminal activity. Copyright leeches have enough money to buy laws favorable to them. Which, also, gives them more money to buy even more laws favorable to them. It doesn't have to make sense for you because it's not designed to serve your interests.
Because they've already got the ISPs DNS resolvers blocking shit and when they see clients from those same ISPs still connecting they get hints on which public DNS resolvers people are using. You can make a safe bet French ISPs played an active part in pointing people to go after quad 9.
The tweet is criticizing over-reliance on the "agents will fix it anyway".
The fact that we can fix things faster now doesn't mean that we should throw away caution and prevention. The specific point of his tweet is that we're seeing a lot of people starting to skip proper release engineering.
Agents are quick to fix bugs, yes, but it doesn't mean that users will tolerate software that gets completely broken after each new feature is introduced and takes a certain number of days to heal each time.
Matt Might's website has taught me so much over the years, going all the way back to ... I want to say 2008-2009? From programming languages to Unix-fu to a huge amount of topics in-between. I'm super glad to see his writing still being shared. One of my favorite corners of the web.
I don't understand the rush to be "the first". Facebook isn't the first social media, Google isn't the first search engine, iPhone is not the first smart phone, Microsoft is not the first OS, the list goes on.
Clearly there's an advantage for being an early adopter, but the advantage is often overblown, and the cost to get it is often underestimated.
> You’re a primary maintainer or core team member of a public repo with 5,000+ GitHub stars or 1M+ monthly NPM downloads.
I've been an open source maintainer of one of the biggest open source projects in the world[1], and it wouldn't fill any of these requirements. Anybody else hates it that now "open source" is conflated with Github (a private company, itself not open source) popularity?
I had the same thought, as an OpenStack developer as well (TBH I don't remember if my username here identifies me or not). Yeah, we can apply as an exceptional case, but realistically us being excluded shows the criteria is very much directed towards "github style" open source.
Maybe worth asking for anyway? They might just be setting metrics based on the most popular ways of measuring but if they care about the spirit of the offer it would make sense for them to be flexible with the letter of the requirements.
Eh in a talk I gave i showed how easy it is to buy github stars and fake downloads to become popular, so these things should not be used as indicators of popularity.
And yes I hate it. Some "scanners" flag all my projects as abandoned because I moved to codeberg.
The way I experience this is through unprecedented amount of feature creep. We don't use AI generated code for all our projects, but in the ones we do, I see a weird anti-pattern settle in: Simply because it's faster than ever before to generate a patch and get it merged, it doesn't mean that merging 50+ commits this week makes sense.
Code and feature still need to experience time and stability in order to achieve maturity. We need to give our end users time to try stuff, to shape their opinions and habits. We need to let everyone on the dev team take the time to update their mental model of the project as patches are merged. Heck, I've seen too many Product Owners incapable of telling you clearly what went in and out of the code over the previous 2 releases, and those are usually a few weeks apart.
Making individual tasks faster should give us more time to think in terms of quality and stability. Instead, people want to add more features more often.
I don't know if you're "wrong", but I do feel differently about this.
I've written a ton of open source code and I never cared what people do with it, both "good" or "bad". I only want my code to be "useful". Not just to the people I agree with, but to anyone who needs to use a computer.
Of course, I'd rather people use my code to feed the poor than build weapons, but it's just a preference. My conviction is that my code is _freed_ from me and my individual preferences and shared for everyone to use.
I don't think my code is "stolen", if someone uses it to make themselves rich.
And in that case, use MIT license or something like that for your code, and all is good. If I use AGPL, on the other hand, AI companies should not be allowed to train on that and then use the result of that training while ignoring the license.
> Not just to the people I agree with, but to anyone who needs to use a computer.
Why not say "... but to the people I disagree with"?
Would you be OK knowing your code is used to cause more harm than good? Would you still continue working on a hypothetical OSS which had no users, other than, say, a totalitarian government in the middle east which executes homosexuals? Would you be OK with your software being a critical directly involved piece of code for example tracking, de-anonymizing and profiling them?
As for me that's a risk I'm willing to accept in return for the freedom of the code.
I'm not going to deliberately write code that's LIKELY to do more harm than good, but crippling the potential positive impact just because of some largely hypothetical risk? That feels almost selfish, what would I really be trying to avoid, personally running into a feel-bad outcome?
I think it would be most interesting to find ways to restrict bad usage without crippling the positive impact.
Douglas Crockford[0] tried this with JSON. Now, strictly speaking, this does not satisfy the definition of Open Source (it merely is open source, lowercase). But after 10 years of working on Open Source, I came to the conclusion that Open Source is not the absolute social good we delude ourselves into thinking.
Sure, it's usually better than closed source because the freedoms mean people tend to have more control and it's harder for anyone (including large corporations) to restrict those freedoms. But I think it's a local optimum and we should start looking into better alternatives.
Android, for example, is nominally Open Source but in reality the source is only published by google periodically[1], making any true cooperation between the paid devs and the community difficult. And good luck getting this to actually run on a physical device without giving up things like Google Play or banking apps or your warranty.
There's always ways to fuck people over and there always will be but we should look into further ways to limit and reduce them.
> Open Source is not the absolute social good we delude ourselves into thinking.
Historically the term "Open Source" was specifically developed to divorce the movement from the "social good" ideas that were promoted by Free Software.
That's where I stand. I don't do Open Source to make the world better. I do Open Source because I believe that makes my software better.
I'm not an activist. I'm an engineer. Nothing wrong with activism, all the power to the people doing it, but the licensing I chose for my code doesn't take it into account.
I agree with the GP. While I wouldn’t be happy about such uses, I see the use as detached from the software as-is, given (assuming) that it isn’t purpose-built for the bad uses. If the software is only being used for nefarious purposes, then clearly you have built the wrong thing, not applied the wrong license. The totalitarian government wouldn’t care about your license anyway.
The one thing I do care about is attribution — though maybe actually not in the nefarious cases.
> The totalitarian government wouldn’t care about your license anyway.
I see this a lot and while being technically correct, I think it ignores the costs for them.
In practice such a government doesn't need to have laws and courts either but usually does because the appearance of justice.
Breaking international laws such as copyright also has costs for them. Nobody will probably care about one small project but large scale violations could (or at least should) lead to sanctions.
Similarly, if they want to offer their product in other countries, now they run the risk of having to pay fines.
Finally, see my sibling comment but a lot of people act like Open Source is an absolute good just because it's Open Source. By being explicit about our views about right and wrong, we draw attention to this delusion.
It’s fine to use whatever license you think is right. That includes the choice of using a permissive license. Restrictions are generally an impediment for adoption, due to their legal risk, even for morally immaculate users. I think that not placing usage restrictions on open source is just as natural as not placing usage restrictions on published research papers.
Tragedy of the commons. If all software had (compatible) clauses about permitted usage, then the choice would be to rewrite it inhouse or accept the restrictions. When there are alternatives (copyleft or permissive) which are not significantly worse, those will get used instead, even if taken in isolation, the restricted software was a bigger social good.
If you think you'll ever want to use third-party tools to process that markup, or if some of your private files will transform into public files at some point, then yes, considering popularity makes a lot of sense.
If they're just text files you edit raw that will never interact with anything else but your text editor, then of course popularity doesn't matter at all. But in my experience, my use cases tend to expand over time.
The article even talks about org mode's interoperability, mainly about the fact that pandoc supports it. And then bizarrely ignores the fact that it has much less ecosystem support than Markdown. So this is very much a subject the article itself brings up, and something that therefore also deserves to be critiqued.
OP here. I stuck with orgmode all these years /because/ of the interoperability.
If I'm writing in Org, I can tangle / detangle between other plaintext sources, including source code. As well as export to collaborate.
The proposition is "yes, and", not "either / or".
It's /fine/ to switch to the popular "team" standard and stay there when needed. Several of my workplace documents, including wiki entries start off as local org-mode drafts. Once I'm okay to share, I export to markdown or draft wiki page and solicit comments. After that, if the document is for shared maintenance, I let my org-text alone, and switch to the "team" format.
This is perfectly fine.
That and the many kinds of markdown. I've been bitten enough by having to look up yet another poorly maintained document on how to markdown for /this/ particular app or website or utility, that I'd rather pandoc translate between my (sane, well documented, fully extensible) org text and whatever I need to share with others, than learn edge cases of various markdowns.
Sure, but I think it's safe to say Markdown has more interoperability, no?
Yes you can always use pandoc, but conversion usually brings quirks of its own. And more generally, the less conversion steps you need, the better.
If you just stick to vanilla markup, you don't encounter incompatibilities. The "many kinds of markdown" isn't an issue if you're not using platform-specific extensions in the first place. Which, usually, you're not, unless you need to do something very specific to that application.
Yes, more interoperability at the cost of capability.
Also, yes, conversion is quirky. That is why Org works until it does, and then I trade off being stymied by markdown's more plain-ness, in favour of collaborating with others.
And with vanilla markup, the trouble is that many applications /do not/ use just vanilla markup. People /invariably/ want "one key tweak" (like, front-matter or table of contents or footnotes or some such thing), and everyone ends up doing their own thing.
Perhaps the trouble with markdown is it's /too/ plain. So yes, lots of people can do lots of lowest common denominator stuff, but it does not extend to individuals wanting "just one thing" which also adds up to a lot of people.
Edit: a real-life example... I typically run code from org-mode for interactive testing and debugging --- the kind of stuff we write small throwaway scripts for.
In this one project, I made it so that /I/ or anyone else using org-mode could do it from org, for local development, and anyone else could just use the script as-is... including the CI pipeline.
> Yes, more interoperability at the cost of capability.
Well, then why aren't you using LaTeX? Isn't that more capable?
> And with vanilla markup, the trouble is that many applications /do not/ use just vanilla markup. People /invariably/ want "one key tweak"
And, that's going to be true as someone adopts it outside of Emacs, right?
Surely, someone will decide that the way Org Mode is doing something is wrong, right? They're going to do something like say, "Hey, why don't we permit Markdown style headings, too?" or something similar.
Or are you suggesting Org Mode military police? Felony markup possession?
There's nothing special about Org Mode that makes it immune to the problems you're describing. They will happen immediately upon wider adoption.
And if you somehow do stop it, well, it's tech. If you don't have a patent on it then someone will fork the idea and you'd have Borg Mode directly competing with you anyways.
A Unix novice came to Master Foo and said: “I am confused. Is it not the Unix way that every program should concentrate on one thing and do it well?”
Master Foo nodded.
The novice continued: “Isn't it also the Unix way that the wheel should not be reinvented?”
Master Foo nodded again.
“Why, then, are there several tools with similar capabilities in text processing: sed, awk and Perl? With which one can I best practice the Unix way?”
Master Foo asked the novice: “If you have a text file, what tool would you use to produce a copy with a few words in it replaced by strings of your choosing?”
The novice frowned and said: “Perl's regexps would be excessive for so simple a task. I do not know awk, and I have been writing sed scripts in the last few weeks. As I have some experience with sed, at the moment I would prefer it. But if the job only needed to be done once rather than repeatedly, a text editor would suffice.”
Master Foo nodded and replied: “When you are hungry, eat; when you are thirsty, drink; when you are tired, sleep.”
Okay. You didn't seem to understand that that was a rhetorical question, because you didn't seem to take the next step of reflection.
So, what does your comment to me say if used in response to your own org mode vs markdown comment you made in the post I responded to? You said org mode's capabilities are the reason why you don't want markdown.
You keep making this argument that org mode is just better, but you can immediately find a counterargument yourself to your own point.
Now, it's perfectly fine that that represents how you feel about the software. You can hold whatever opinion you want. But, you're not just trying to explain your opinion. You're trying to convince people that org mode is better. You understand why you're not being very persuasive in your argument, right? You've argued in a way that the only people who will agree with you are those that already hold the same opinion as you.
Org mode's capabilities are the reason why I don't want markdown for me.
Markdown's popularity is the reason why I switch to it for other people (team / colleagues).
LaTeX is too much for day to day use. Its purpose is precision typesetting. That is a lot of work with LaTeX. I don't need to do precision typesetting on a day-to-day basis. But I've used it to format documents for people when they ask me to. Then it's worth the pain. Besides, LaTeX has none of the organisational capabilities enabled by orgmode, for my daily-drive uses.
There is a reason a Physicist---who daily-drives LaTeX, for their publishing work---went through all the trouble to build a note taking system from scratch.
So, once again, utility is contextual, and I refer back to Master Foo's lesson every time I have a problem.
Ahem. When I started with Markdown, I was regularly experiencing all the issues mentioned for years. The most popular format was Word (doc). Perhaps I should have stuck with that?
No? I’m pushing back against advocacy for broader adoption of org mode beyond personal file markup though, which is what I feel like this piece is arguing.
> note that this is not about Emacs at all. This is about Org mode syntax and its advantages even when used outside of Emacs.
One of the advantages of "going with the flow" when you can is that you benefit from numbers. You're a market of one, but by "going with the flow" the total market is huge.
Even if for me personally 185V mains power would be better, I can't buy gear for 185V, none of the electricians around here know how to work with it, the cables and sockets and everything else are defined around the prevailing systems at 220-250V here.
Maybe in my kitchen a 520mm dishwasher would be great, but alas dishwashers you can buy here are 600mm or 450mm ("slimeline") models, so 520mm isn't available.
With my poor hearing 14-bit PCM would be absolutely fine, but Sony's "Compact Disc" used 16-bit so that's what everybody uses and records by default.
If you work with Markdown, there are a lot of existing tools which are ready to use. There are tools for Org Mode, but maybe not as many.
There's definitely a sliding scale here. Refusing to use Twitter because it's full of Nazis is very different from refusing to conform to society's expectation that you wear clothes outside for example. There are people willing to spend most of their lives in jail because they refuse to wear clothes but almost all of us don't think that's a principle we care about enough to prioritise (also some of us get cold).
I think this is moving the goal post. Cloudflare isn't challenging the need to restrict access to some websites, it is challenging who has the right to decide. Quoting the tweet:
> We believe Italy, like all countries, has a right to regulate the content on networks inside its borders. But they must do so following the Rule of Law and principles of Due Process.
I live in Italy, I'm a citizen. I don't feel any safer having the internet regulated by a bunch of bureaucrats than I do state actors and bots.
Bureaucrats are a problem, but they're eventually accountable to the people. Companies are accountable to shareholders located in another country, who don't give a damn about whatever so long as the money keeps coming. I choose bureaucrats against businessmen anytime.