Air Canada Has to Honor a Refund Policy Its Chatbot Made Up

Corgana@startrek.website to Technology@beehaw.org – 177 points –
Air Canada Has to Honor a Refund Policy Its Chatbot Made Up
wired.com
41

You are viewing a single comment

We've started asking users not to do this. No issues with posting an archive link, though.

Why in the world would you ask people to stop cercomventing a pay wall

There's no need to be rude.

I'm not asking people not to circumvent paywalls. In fact, if you reread my comment, I recommended the user leave an archive link, which is a method of bypassing paywalls that doesn't involve posting the full contents of the article to this site.

Probably because it could raise copyright issues for Beehaw since Beehaw would be hosting the article.

At some point we have to ask oursevles what is more important IP law, or dessiminating information.

Lemmy was founded on the idea that different instances can decide questions like this for themselves.

It seems that Beehaw has chosen one direction, but there may be other instances out there that have chosen another direction.

Still, asking oneself is part of that system.

Maybe, but users from other instances would be lowest opinions I would expect the admins to consider. I would expect mods, financial contributers, and users registered to this instance to have a far greater day in how this instance is run.

so there's just no answer as to why we can't paste the text?

There was an answer from a mod, they don't want to infringe on the copyright here.

It's really only a copyright problem if they're making money from it right?

No. It is worse if they try to make money on it, but a profit motive isn't necessary.

Unfortunately there's another problem with archive.is / archive.ph / archive.today . Their owner has some beef with Cloudflare DNS and returns bogus results to them so anyone using 1.1.1.1 as DNS can't visit them.

The Cloudflare side of the story: https://news.ycombinator.com/item?id=19828702 The archive side: https://twitter.com/archiveis/status/1018691421182791680

Note that that discussion was from 2019 but the situation was never resolved and the issue persists to this day.