Tim Chambers
IMPORTANT: Bot/App Developer #MastodonMigration 📢 For #TwitterAPI devs ➡️ See this list of Apps/Bots heading to #Mastodon—add your service if you're leaving before the free API shutdown in days: https://forms.gle/WLBK1jaE2vaxW1U2A And see the good 🤖 #bots moving over here: Please share to all bot Developers who have already made the jump, and on Twitter, please amplify this tweet: 11 comments
Tim Chambers
@Jackivers They almost certainly will be hit by this. Not sure they have an economic model to make it worth continuing.
Jack Ivers
@tchambers ☺️ Not sure what their model was over in birdland either but (unless I’m missing some masto capability — always possible!) the capability is often handy. (Also just realizing there may be a community privacy prohibition around this kind of tool)
Tim Chambers
@Jackivers Different instances have different rules. Most allow bots as long as they label themselves as such. Some instance are JUST set up for bots.
Jack Ivers
@tchambers The scenario I was thinking of, having seen discussions of various features that might not be appreciated by the community: imagine a long thread with say 50 different participants => unrolled to a public website. Is that a community problem? I realize there’s no one community but wondering, would this be “generally fine” or “usually not ok” … 
Jack Ivers
@martinvermeer @tchambers Ah yes, true. My personal desire is to have several good ones move over here! 
Liaizon Wakest
@tchambers This is great. Any thought about using something other then Google Docs for this? @cryptpad has a good solution that is much less privacy invasive...
Tim Chambers
Would love to, and am a fan of your platform. Will think of this for next one for sure. 
Jeff Barbose
@tchambers It would be helpful to post links with all of these for any pointers to how to write your own bots. |
Gregory's Server
@tchambers Just realizing that thread unroll bots are likely to be wiped out with this Twitter API closure — have you heard from Threadreader or its ilk?