Hacker Newsnew | past | comments | ask | show | jobs | submit | mcv's commentslogin

> The announcement is surprising, because Anthropic has described itself as the AI company with a “soul.”

I can't help but think about how Google once had "Don't be evil" as their motto.

But the thing with for-profit companies is that when push comes to shove, they will always serve the love of money. I'm just surprised that in an industry churning through trillions, their price is $200 million.


We're talking about the US here; they're very good at ignoring solutions to solved problems. See city planning, traffic design, healthcare, zoning, etc. If it's not invented in the US, it can't possibly work there, they claim.

It's not feasible to have a bus stop right in front of every house. It's unavoidable that most people are going to have to walk a bit. How far is reasonable, is a matter of trade-offs. It also depends on how fine grained the network is. If there are buslines every block, it's annoying if they don't stop there. But you have to walk a block or two to get to a bus line anyway, walking that bit more to get to the stop itself, matters a lot less.

> It's not feasible to have a bus stop right in front of every house.

And this is why point-to-point transportation is almost always faster and more convenient, if you can afford to use it. (That load-bearing "if" is important, though.)


> And this is why point-to-point transportation is almost always faster and more convenient

Point-to-point transportation is faster and more convenient because:

1. we don't have bus lanes so buses are forced to sit in the same traffic as cars and 2. buses are often underfunded so have slow/infrequent service.

Point to point transportation is often slower and less convenient if buses and public transit is done right. I can count on my fingers the number of times I used an Uber or drove a car in the 1 month that I stayed in Europe - this was going out every day, in multiple cities, rural and urban, and across different countries.

This is a good thing! If more people use public transit when it's possible, it opens up the roads for the handful of people who actually NEED to use a car.


Bus lanes still seem like the thing people who hate cars propose to intentionally screw over the people who have them. "Hey, we have this road with two or three lanes in each direction but it's fairly congested. Each of the lanes is carrying something like 50 cars per minute during the day! Why don't we impound one of them so we can have a bus carrying 40 people drive on it once every 15 minutes?"

If you have enough density to justify a bus lane, you have enough density to justify a subway.


> If you have enough density to support a bus lane, you have enough density to support a subway.

Not at all. Building a subway in most US cities right now is very expensive. Raising the tax revenue alone is probably a non-starter.

Moreover you're going to have to close the road down anyway to do any form of cut-and-cover or even deep bore construction, which means every business on the corridor and every person who lives on it is going to get angry for as long as the subway is being built.

There's no painless way to do infill public transport. The problem is that nobody in the US is willing to compromise.


> Building a subway in most US cities right now is very expensive.

This is true but seems like a problem worth solving. It's also true of more than subways; we have the same problem with bridges, housing and many other things. Better to get on with fixing it than use it as an excuse for doing something worse.

> Moreover you're going to have to close the road down anyway

That's a one-time cost, and you're not required to close a 500 mile stretch of road for years on end. Dig one block, install the tunnel, cover it, dig the next block.


I agree with you (and importantly you can't make a subway political football the way you can make a bus lane), but my experience doing transit advocacy points otherwise. Americans in dense areas are feeling the HCOL pinch and are not very willing to float extra taxes to fund transit expansion.

IMO it comes back to the fact that Americans are just not willing to accept change of any kind right now. The economy feels too shaky, the electorate too divided (even within states and municipalities), and there's too little faith in government to architect the kind of change you'd need to build subways, underground metros, or even BRT. We need a larger feeling of unity even at a state level to make the changes necessary, which is why municipalities continue to do bare minimum maintenance of roadways and pretty much nothing else. The last big set of constriction in dense urban areas was funded by the Obama stimulus from the GFC which was passed 17 years ago.


It was probably always a good idea to do it the other way around anyway: You don't start with transit, you start by building more housing. Tons of it. Then the cost of living starts to get back under control and the density increases some, which you need in order to make transit work regardless.

We did that with computer networks. We had this high-quality voice call service, and then someone thought it should be switched to transmit data instead, of which voice calls were just one type. Now you have a minimum voice latency of a few hundred ms because voice traffic is competing with data traffic, and you didn't actually get much more data throughput because it was only one wire pair.

> If you have enough density to justify a bus lane, you have enough density to justify a subway.

That assumes a linear city, where everyone lives within a short walking distance of the same street.

In actual cities, bus lines from different neighborhoods converge on main streets. While individual lines may have 10–15 minute intervals, bus traffic on the main streets may be high enough to justify dedicated bus lanes.

Then, as the city grows, it can make sense to replace the bus lanes with light rail and direct bus lines with collector lines connecting to the rail line. Which should be cheap, as a dedicated lane is usually the most expensive part in building light rail.

But you generally want to avoid building subways until you have no other options left. Subway lines tend to be an order of magnitude more expensive than light rail lines. Travel times are also often higher, as the distances between stops are longer and there is more walking involved.


Heavy rail and light rail costs are very comparable unless you want to bury them. But it doesn't matter which you bury, they still cost about the same.

> That assumes a linear city, where everyone lives within a short walking distance of the same street.

Isn't that the assumption you're making? That there is a single primary street that everything converges and then diverges from which is common to every bus route? Meanwhile in practice any given person standing on the You Are Here dot could want to go in any of the eight directions from where they currently are.

A route that goes east-west isn't going to have much in the way of shared route with one that goes northeast-southwest except for the one point where they intersect, and isn't it better to have multiple routes intersecting in multiple places in terms of minimizing trip latency and maximizing coverage?

> Which should be cheap, as a dedicated lane is usually the most expensive part in building light rail.

But that's the thing that makes the bus lane so expensive!

By the time you have an area with enough congestion to be considering a bus lane, the problem is generally that you can't add a lane because the land adjacent to the existing road is already developed and not available, otherwise you would just add an ordinary lane that buses could use too. But converting one of the existing lanes in an area which is already congested makes the traffic exponentially worse than putting the new thing underground.

Essentially, if you can add a lane then you add an ordinary lane and if you can't add a lane but need one then it's time to dig.


Public transit depends on the assumption that some trips are more common than others. If any given person is equally likely to go to any direction, public transit becomes too expensive to build. And it becomes impossible to make the city dense without turning the traffic into a nightmare.

A typical direct bus line starts from somewhere, goes through a number of neighborhoods, reaches a major street, and follows it to a central location. The number of directions that need a bus line is typically much higher than the number of streets reaching the central location. (For example, you need ~10-degree intervals at 10 km from the center to guarantee a reasonable walking distance to the nearest bus stop.) Hence the bus lines eventually converge.

Once you have enough bus traffic that a dedicated lane makes sense, transforming an ordinary lane into a bus lane will make the traffic faster for the average person. It's not a Pareto improvement, as the traffic will become worse for those who drive on that route. But it's not a huge loss for them either. If you already have 20+ buses/hour making frequent stops during the rush hour, the throughput for that lane will already be much lower than for the other lanes.


> Point to point transportation is often slower and less convenient if buses and public transit is done right.

Only if you're also intentionally making point-to-point worse.

Note that I'm not comparing to "get in your own car and drive", which has the disadvantage of having to park. I'm comparing the ideal taxi-shaped thing to the ideal bus-and-tram-and-train-shaped thing.


> Only if you're also intentionally making point-to-point worse

I feel like you missed my last paragraph. If public transit is better then more people would use it and there would be fewer cars on the road. Can you imagine how terrible point-to-point traffic in SF would be if everyone was driving to work instead of relying on Caltrain or BART?


No, I didn't miss it. I'm saying that public transit can be better than it currently is, but it would take much more to make it better than point-to-point transit.

Self driving cars for hire (Waymo, Tesla, others) can be that point-to-point system that is affordable. We will just have to build tunnels to deal with the increase in traffic. Hopefully the Boring Company or someone else can get tunneling costs way down.

I generally agree that self-driving cars are going to take this niche, but not with tunnels. Tunnels add the same dedicated infrastructure problems as mass public transit.

I'd suspect most car trips today are 1 or 2 passengers with the back seat and trunk empty; we'll eventually see new form factors of on-demand vehicle that trim off unneeded space. If you need to get from A to B alone, no cargo to speak of, you order a ride that covers that class and it's small. If you're taking a shuttle from the airport with your whole family and luggage, you order a ride with those specs.


If you are not being facetious, what you are describing is closer to a subway system, which has the disadvantage of being very expensive.

Hopefully someone else, so it actually happens and isn't overpromised and underdelivered.

(Also, tunnels are useful not just for the increase in traffic, but for moving car traffic away from non-car traffic, which makes both kinds of traffic safer, faster, and more efficient.)


As long as one of those points is a transit stop then yeah, robotaxis make sense. In that model you don’t need the tunnels.

They make even more sense if they are a bit larger and can accommodate multiple people at once. Something like a large van or small bus.


No, it's not unavoidable. Just ditch the buses and switch to cars, soon to be self-driving.

Even the rush hour traffic is trivially solved by mild carpooling (small vans for 4-6 people).


Not Just Bikes makes a compelling argument that self driving cars are not the answer, and will almost certainly make things worse

Would you care to summarize their argument?

Self-driving cars still take up space on the road. Even more than human-driven cars, because now there will also be cars transporting 0 people. It's going to make congestion worse. Public transit is the solution to congestion. Well, one of the solutions, because bikes are probably a better solution for most people: they do start in front of your home, can park anywhere, and don't cause congestion the way cars do.

We're talking about cities, of course; in rural areas, nothing beats cars.


> Self-driving cars still take up space on the road

This is a false argument. Think about this: a bus every 10 minutes is effectively 500-900 meters long! It easily "takes" as much space as 100+ cars. In other words, nothing would change from the traffic perspective if instead of 1 bus every 5 minutes, you had 100 individual cars.

The "people in the shape of a bus" argument makes sense only when you're talking about the performance in a very narrow case of transporting people in a steady, uninterrupted stream of buses. Or if you need to size your traffic bottlenecks.

Moreover, a bus route necessarily is unoptimal for at least some people on a bus. They are effectively "thicker" than other people because they take up more "effective space". But wait, there's more! Buses also necessarily move slower due to stops, so the "effective length" of a bus becomes even longer because cars will clear the road faster.

But wait, there's even more! A single bus needs about 3 drivers to be effective. So with the average daily busload of around 15 people, you have almost 20% of the bus taken by the drivers on average. This makes bus trips pretty expensive. Not quite to the level of Uber/Lyft, but surprisingly close.

And these problems are fundamental. That's why urbanists like NJB don't like to talk about that.


Nothing about this addresses NJB's argument that self-driving cars take up more space than regular cars, because there will now be cars with 0 people in them.

Ultimately the thing you want to transport is not cars, it's people. Walking fits the most people in a limited amount of space, then bikes, buses and other forms of public transport, then cars with 4 people in them, then cars with 3 people in them, then cars with 2 people in them, then cars with only 1 person in them, and finally empty cars. More cars will never reduce congestion.

But to address your point: A bus in a dedicated lane takes up more space than a bus that's stuck in car traffic, you are right about that. On the other hand, when congestion is so bad that cars simply don't move, no matter how many lanes they have, getting people out of cars into more efficient forms of transport, will also help cars. And a bus that actually goes, can do that. If you look in cities with good public transport, more people go by public transport than by car. In cities with good bicycle infrastructure, more people go by bike than by car. That means even cars are less likely to get stuck in traffic in those cities. Even if you take away a car lane.

I don't know where you got the idea that a bus needs 3 drivers.


> Nothing about this addresses NJB's argument that self-driving cars take up more space than regular cars, because there will now be cars with 0 people in them.

And? There are also buses that trundle around with nobody but the driver in it. Or unused bikes and e-scooters that litter the sidewalks.

> Ultimately the thing you want to transport is not cars, it's people.

Yeah. And let's make it efficient. Put these people into 3-level bunk beds. This way they can travel all together in just 1 bus to their assigned workplace. And you don't need to run buses until they're allowed to clock off their shift.

Efficiency!

> On the other hand, when congestion is so bad that cars simply don't move

In this case you close the downtown offices and force them to work on alternate days, like they do in India with cars. Remote work already can replace 70% of all work, and with AI this number will grow.

Apart from that, mild carpooling will decrease the number of cars by 2x. Small vans with 6 seats can _easily_ remove all congestion.

> no matter how many lanes they have, getting people out of cars into more efficient forms of transport, will also help cars.

Just one ask for urbanists. Can you just stop lying, please? Just one thing. Don't say that "transit help cars". It doesn't. There is a lot of research from _you_ (e.g. https://archive.strongtowns.org/journal/2020/1/7/does-buildi... ) that proves this. Transit does NOT decrease the travel time for cars ("traffic") it _increases_ it by increasing congestion due to increased housing density that transit forces.

You want to pack people into 3x3 jails ("microapartments")? Fine. But be honest about it.


> a bus every 10 minutes is effectively 500-900 meters long!

uhhhhhh what. What does every 10 minutes have to do with this at all

> It easily "takes" as much space as 100+ cars.

are you ok??? have you seen a bus before??

> A single bus needs about 3 drivers to be effective

I have never ever seen a bus with 3 drivers in it. If you're talking about 3 drivers over the course of 24h, those drivers are not in the bus at the same time, and therefore don't make up 20% of the passengers on the bus. If you're saying the average bus route serves 15 people per day, you are certainly mistaken.


> If you're saying the average bus route serves 15 people per day, you are certainly mistaken.

Definitely mistaken for London - currently (according to DFT's numbers) about 18 people per bus average (not per day, though.)


> uhhhhhh what. What does every 10 minutes have to do with this at all

See the word "effective". Think about the road space that a bus requires but doesn't use if it is just once per 10 minutes.

> I have never ever seen a bus with 3 drivers in it. If you're talking about 3 drivers over the course of 24h, those drivers are not in the bus at the same time, and therefore don't make up 20% of the passengers on the bus.

Yes, I'm talking about the drivers that are needed for a reasonable 16-hour bus service. And the typical ratio is actually a bit more than 3 drivers per 1 bus.

> If you're saying the average bus route serves 15 people per day, you are certainly mistaken.

No. I'm saying that on _average_ there are 15 people in a bus. More during the rush hour, fewer during the off-hours.


So where is the 20% of passengers are drivers thing even coming from?

3/(3+15) = 3/18 = 1/6 ~= 20%

> See the word "effective". Think about the road space that a bus requires but doesn't use if it is just once per 10 minutes.

Excepting the case of a dedicated bus lane, the amount of road space a bus is preventing other cars from taking up at a given time is equal to the size of the bus. Technically, it's less than that in the case of bus stops littered amongst parking. In the case of a dedicated lane, it reduces the maximum throughput of the thoroughfare, but it's not a simple thing to model as there are other effects that the bus can have to reduce the number of cars when the rate limit of thoroughfare would be pertinent (i.e. usually rush hour). Just saying "think about it" when saying a bus takes up the space of 100+ cars doesn't really substantiate such a bold claim.

> Yes, I'm talking about the drivers that are needed for a reasonable 16-hour bus service. And the typical ratio is actually a bit more than 3 drivers per 1 bus.

> No. I'm saying that on _average_ there are 15 people in a bus. More during the rush hour, fewer during the off-hours.

If there is an average of 15 passengers on the bus during the operations of the bus and there is an average of 1 driver on the bus during the operations of the bus, then it is 1/16th occupied by driver(s). For it to be taken 20% by driver occupancy, then it would require there to be an average of 4 passengers on the bus during operations.


I actually am citing the traffic engineering handbook, the section about computing the efficacy of bus lanes. And I'm using deliberately conservative estimates.

> If there is an average of 15 passengers on the bus during the operations of the bus and there is an average of 1 driver on the bus during the operations of the bus, then it is 1/16th occupied by driver(s)

No. For the bus to be viable, all 3 drivers have to be "virtually present" there. A bus _has_ to be available at all times with a reasonable interval, otherwise it might as well not exist.

Or in other words, a passenger needs to be paying the salary for even the missing drivers.


> We're talking about cities, of course; in rural areas, nothing beats cars.

Where I grew up in NW Scotland, it's a five hour round trip to go to the supermarket. You pretty much need a car for that.

Where I live right now it's a five minute walk to the supermarket, but I still need a car because the things I work on are a long way from where I live, often up steep muddy mountain tracks.

When I lived in the middle of Glasgow people used to come up and have a go at me about driving a massive V8 4x4 in the middle of a city. What am I supposed to do with it? Bike to the suburbs and then go and drive up a mountain?

"But why not get a job where you don't need to drive hundreds of miles in a massive 4x4?"

Because then the things on the tops of mountains don't get fixed when they break, and the radios don't work properly, and then people like you die in a fire.

Sometimes it's hard for people to grasp that just because their not-really-a-job tapping numbers into an Excel spreadsheet all day can be done from home or from an easily walkable city centre location, it doesn't mean that everyone's job looks like that.

I do wish I could usefully use a cargo bike. Those things are awesome.


What people really misunderstand in these discussions is that no one is talking about completely killing off driving as an option, and no one says that public transportation works in literally 100% of circumstances.

We just want there to be viable public transportation options for situations where it makes sense. This even makes it easier for the people who do have to drive, like you, as there will be less congestion because a single bus can replace literally dozens of cars, combine that with a single tram and a single metro car and you're replacing literally hundreds of cars that would otherwise be on the roads instead.


Exactly. It would be awesome if we had viable public transport options in rural areas too, although necessarily they would not be as frequent of flexible as in cities. There wouldn't be the requirement for them so much, because of the lower population density and the different patterns of vehicle use.

But growing up in a rural area where there are two buses a day none of which are useful for anything other than high school pupils (although they're not school buses) it does tend to limit everyone's options.


> What people really misunderstand in these discussions is that no one is talking about completely killing off driving as an option

I find this statement utterly hypocritical. Sure, we're not killing off driving. We are just choking off the roads with bike lanes, forcing extra-high density ("just build more"), removing parking, forcing the drivers to pay for transit that they don't use, and just to pay in general.

But no, we're not preventing driving. Not at all.

Urbanists want to stop people from using cars as much as they can force that.


If you actually had to pay a proper price for your parking space, which is currently heavily subsidized, you would suddenly consider taking public transit instead, even if that were priced at actual cost.

In what way is a piece of ground I own "heavily subsidised"?

> Urbanists want to stop people from using cars as much as they can force that.

If you live in a city, you probably don't need a car.


You call it "choking off" roads; I call it basic geometry. Reallocating a lane of traffic to bikes or transit moves exponentially more human beings through the exact same amount of physical space. But sure, pretend that a single occupant dragging around a 4 ton metal box to buy groceries is the absolute pinnacle of spatial efficiency.

And the fact that you're complaining about "removing parking" is hilarious. Street parking is objectively the most useless, wasteful allocation of already limited public space imaginable. You expect cities to dedicate premium real estate to act as a subsidized storage locker for your private, empty vehicle for the 95% of the day you aren't even using it. Then you complain about non-drivers "forcing" you to pay for transit, while everyone else's taxes are literally subsidizing the free public storage of your personal property.

Let's also talk about your entitlement to those roads. When you complain about "choking off" streets, what you're really whining about is that cities are finally prioritizing actual residents over commuters who are just driving through. Most car traffic in urban centers is just people transiting. Why should a neighborhood sacrifice its safety, noise pollution levels, air quality, and public space just to act as a high-speed shortcut for people who don't even live there?

And please, spare me the inevitable "but what about rural areas" argument. We are talking about dense cities. Nobody is coming for your car in bumfuck nowhere; you can keep driving there all you want. (Though honestly, here in the Netherlands, you don't even have to drive in the countryside because you can usually just grab a train or get anywhere by bike, but that's beside the point.) Urban planning applies to urban areas.

I live in the Netherlands. Millions of people here take transit and ride bikes every single day. And guess what? Nobody banned cars. In fact, it's widely considered one of the best places in the world to drive specifically because everyone who doesn't want or need to drive isn't forced to be on the road getting in your way. We just realized that sacrificing huge swaths of our cities so commuters can treat our neighborhoods as a shortcut is incredibly stupid, and there are infinitely better ways of using the limited space in cities than to let drivers park their cars there.

Giving people viable choices isn't a totalitarian conspiracy to oppress drivers, it's just good urban design. It's wild that you are so used to forced car dependency that simply offering people an alternative feels like a personal attack.

P.S., I'm also a driver, I just don't need to do it 90% of the time because I live in a sane country where I can just bike to the other side of the city in 20 minutes.


> Reallocating a lane of traffic to bikes or transit moves exponentially more human beings through the exact same amount of physical space.

Except that bike lanes in the US, on average, carry fewer people than car lanes that they replaced. So yes, it's indeed "choking off". It's done to force the density increases. After all, if you can't commute anymore (roads are sabotaged and transit is slooooowwww), you'll have an option to live closer to the workplace. In a new expensive apartment in a high-rise.

Bike lanes also kill businesses. There were studies showing otherwise, so I replicated them, and they now show the opposite. Places in Seattle and Portland with bike lanes that displaced traffic lanes are declining faster than areas around them. The previous positive results were caused by spurious correlations during the general upswing in the urban economy after the 2008 crisis.

> Then you complain about non-drivers "forcing" you to pay for transit, while everyone else's taxes are literally subsidizing the free public storage of your personal property.

There is no free parking around me anywhere. And I'm also paying around $2000 a year in car tab and property taxes for transit that I don't use. And before you ask, in my state user fees pay for 90%+ of the total road maintenance expenses.

> We are talking about dense cities.

Yeah. They need to be _de_-densified in the longer term. But even dense cities will benefit from removing bike lanes and adding self-driving taxis.

> I live in the Netherlands. Millions of people here take transit and ride bikes every single day. And guess what? Nobody banned cars.

I got my driving license at the age of almost 30, and I lived in several large cities. And I _also_ lived in Amsterdam. People ride bikes in Amsterdam because there usually are no other comparable options. Transit typically takes ages longer, and car parking is non-existant. Of course, people justify that by telling themselves how they love to ride bikes even in cold wind and rain.


Some areas around Amsterdam have a two-tier bus system, with regular buses with regularly spaced stops, and a network of fast long-distance buses with far less stops and dedicated lanes over their entire trip. They have proven to be incredibly reliable; during the occasional day of terrible weather when trains leave people stranded, these buses still manage to get everybody home in a reasonable time.

I would have hoped that Wargames was in their training set.

Religion has been far more politicised in the US than elsewhere. And not exactly in a direction that makes sense to me (a European protestant).

European Protestantism and American Protestantism differ in substantial ways. Crudely, European Protestantism went the way of Hegelian dialectics and evolving beyond the Christianity of the Bible. American (conservative) Protestantism largely reacted against that. I think both groups are largely held together by politics today though their politics differ in the expected ways.

What counts as "long-lived"? Our shortest lived branches are quick fixes because something got merged into main that doesn't work properly.

I'd like main to always be ready for production, but that seems an elusive goal no matter what git workflow you use.

The best way to prevent complex merges does not depend on your git strategy, but on how modular you make your code. If a change requires changes to only a single file, and your files aren't too big, there's little chance of conflict. The more files need to be changed (often because the same thing needs to be declared in 4 different places), the bigger the chance of conflict. Same with larger files. Each file should have a single concern.


For the purposes of this discussion, I'd say a "long-lived" branch is one that keeps running into merge conflicts with other code that's been developed in ignorance of the branch's contents, or a branch that acquires enough changes to not be easily reviewable in its entirety. But generally, I'd say if it lives longer than a day, that's getting too old. (Exceptions apply.)

Code should live in main/master and be in a production environment as soon as possible, but it does not have to run for all, most or even any customers/clients from the start. You can gate it behind feature switches, preprocessor directives, global constants, whatever. As long as it has an active purpose and is being developed further, it is not dead. Ideally, it will have tests.

The result of merging back to main often is that other changes will be made in awareness of your new code, and all merging will happen organically and in small increments. You also get to develop complex features bit by bit, in a way that can be verified in a real environment in a controlled way. And everything can be deployed anytime, which should happen often.

Being able to verify incrementally and get quick feedback lowers the risk of otherwise releasing a hitherto completely untested large feature into the wild in one go.

This does not absolve you from making sure that your changes actually work as intended. That will be easier if you portion the work into smaller chunks that are easier to understand than a whole, complex, all-or-nothing feature.

Of course you will still have to make sure that your small chunks fit together and make up a good "whole". However, the idea is that you're doing this exact work anyway when developing a larger feature on the side, but you might as well cut it up to deliver in much smaller increments.

This approach has its own costs and drawbacks, but in my experience it often produces a substantial net-reduction in friction and accumulated complexity and risk, and it keeps things moving, which is a benefit on its own. This is from my perspective in backend development, and it will not apply universally, but widely. Essentially, whenever you can get away with it, you should strive to deliver like this.


This is great. My workflow is also heading in that direction, so this is a great roadmap. I've already learned that just naively telling Claude what to do and letting it work, is a recipe for disaster and wasted time.

I'm not this structured yet, but I often start with having it analyse and explain a piece of code, so I can correct it before we move on. I also often switch to an LLM that's separate from my IDE because it tends to get confused by sprawling context.


Will it also bypass content bans in the US? Or should Europe create its own freedom.eu for that?

I'm sure I don't have to point out the irony of the current censorship-happy government in the US pretending to be a champion of free speech in other countries. I mean, there are plenty of countries with far worse censorship of course, but for the US to attack the EU specifically on this, is pure propaganda.


I think people getting arrested for social media posts is specifically a UK thing. That and Russia are the only European countries where I've heard of that happening.

In most European countries, you'd have to go pretty far to get in legal trouble for social media posts. It's not impossible, but that's also true in the US. There are and have always been limits to speech. Everywhere. Also in the US (and not just under Trump, although he'd definitely increasing government censorship).

* Threats

* Blackmail

* Libel/slander

These are all restricted by law, because they hurt, silence or coerce people. Hate speech does the exact same thing. It's ridiculous to call hate speech protected free speech, while threats and blackmail are not.

A far worse attack on free speech is banning or restricting criticism of the government. That is the primary reason for free speech protections, and yet that's the very thing that the current US government is attacking on an unprecedented scale. See for example recent attacks on Jimmy Kimmel and Steven Colbert. That's something that would be unimaginable in many European countries.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: