→@[email protected]Apr 8, 2017

@Gargron Hey man, what would you say to making the public timeline GET API call authorisation-free (GET /api/v1/timelines/public)

Use case: The Twitter public timeline was/is used in sample apps as it’s easy to get the public timeline with an unauthorised GET. I was using the App.net API which had the same thing for samples on Set (https://ind.ie/labs/set/). Would love to port those to show the Mastodon.social public timeline instead but don't want to embed credentials in open source app.

Show threadMMN-o ✅⃠Apr 8, 2017
@aral Reasonably the public timeline should be just an Atom feed as any other for consumption in ordinary feed readers. I hope @gargron does this too, but #Mastodon has a somewhat privacy-through-obscurity perspective on what to make easily available and what you have to script together to get a full picture of.
Show thread→@[email protected]Apr 8, 2017
@mmn @Gargron That would work for my purposes too but for simple sample apps, a JSON feed would be easier to parse (and thus used mored) than an XML feed. Given the option of having an ‘anonymously’ consumable feed or not, Atom would be better than nothing for my purposes (ideally, we’d have both) :)
Show threadMMN-o ✅⃠
@aral Yeah, feed as feed. They're all translatable into each other anyway given that they're Activity Streams (and !GNUsocial for example delivers both .as and .atom since there's a simple method to call for output-formatting a stream).
As you probably understood, my point was more regarding public availability without authorisation. .)
Apr 8, 2017 at 9:57amWeb