From Nitter matrix group:

basically, it demands that I:

1. Permanently take down nitter.net and the GitHub repository, and delete all "X Data" in both 2. Stop all use of the "Twitter" and "X" marks 3. Cease all access to X data, including copies 4. Delete all X account credentials and session tokens 5. Confirm compliance in writing within three business days

The claims asserted are breach of X's Terms of Service, Developer Agreement and Developer Policy; the Texas Harmful Access by Computer Act; and the Lanham Act. It threatens litigation against me personally. X states it has also sent notice to GitHub and to my domain registrar.

▲

phatfish 4 hours ago | parent | next [-]

So much free speech.

▲

scosman 4 hours ago | parent | next [-]

A new case where the "free as in speech, not free as in beer" clarification helps.

▲

pjot 4 hours ago | parent [-]

Where do you get this free beer?

▲

tom_alexander 3 hours ago | parent | next [-]

This is why I prefer "gratis" vs "libre" instead of "free as in speech" vs "free as in beer". gratis/libre are clear and succinct.

As for an actual answer: parties, weddings.

▲

amlib 2 hours ago | parent | next [-]

I'm sure this has already been answered somewhere in slashdot hundreds of years ago, but why not just go with "free as in freedom"? And perhaps use the word freedom insted of free when possible

	▲	tom_alexander an hour ago \| parent [-]
		Because freedom isn't free! But in all seriousness, "free as in freedom" seems fine to me but it is replacing the already unambiguous "free as in speech". You're still stuck with the sometimes-confusing "free as in beer" and they're still cumbersome compared to gratis/libre.

▲

kwarcode 30 minutes ago | parent | prev [-]

Weddings tend to have a free speech or two, too.

▲

jack_pp 3 hours ago | parent | prev [-]

friends

▲

dminik an hour ago | parent | prev | next [-]

The global town square is locked up in a gated community.

▲

antonvs 3 hours ago | parent | prev [-]

Is this what free speech absolutism looks like?

▲

pessimizer 5 hours ago | parent | prev [-]

> 1. Permanently take down nitter.net and the GitHub repository[...]

This is the one that they know they have absolutely no grounds to demand, which is why they started with it. Everything else can be conformed with without even really damaging Nitter (the project.)

> 4. Delete all X account credentials and session tokens

could be trouble for individual servers, but is on legally shaky ground, and servers can simply go down at the first strong challenge and open back up under another name. Nitter the project doesn't need to have any credentials or tokens.