I see that @[email protected] has made it to Mastodon. I have suspended it from religion.masto.host, and will suspend any other content scraping bots I become aware of.

Thread readers scrape content without the consent of the creator, move it to a website outside of the creator's control, and sometimes monetise it, as discussed here:

https://twitter.com/erynnbrook/status/1099086911463800832

Erynn Brook on Twitter

“Why I don’t like thread compilers: a thread. Please do not compile. I’ve blocked threadreaderapp and it won’t store my threads.”

Twitter

@amv In case others agree with this take, is there a way a "thread-unrolling" bot would look appropriate to folks? For example if the content was ephemeral and the site ran no ads?

Many people used the bot on the birdsite not because they wanted to exploit creators, but because they found it genuinely useful. I'd love to see discussion of how those useful features can be baked into the #fediverse in a consensual, friendly way.

@astrojuanlu @amv This is something I'm interested in knowing (and this now become circular and meta), but I'd commented on a feature request for Mailbrew about Mastodon support ( it scans feeds to surface web links you may have miss in a daily email digest).

I referenced this (public) toot about the communities dislike to scraping bots - so hopefully there's some way a happy medium can be devised - that both helps users, but protects tooters.