Evan Prodromou

Ugh, please don't convert this project to Kotlin until there's a version that a) builds on Android Studio and b) uses the new Dropbox API. After that, go crazy!

Yes, I think the API limit would still apply. Here's a rough breakdown: Unauthenticated: shared pool of N1 API calls Client authenticated: each client has its own pool of N2...

@strugee So, first, I'm not sure that's possible. If on the server side we delay by (remaining time)/(remaining calls), it would be hard to drain the pool without other players...

Yes, we should definitely clear the OAuth tokens when your password changes, to force re-authentication.

OK, that's interesting.

So, I've been thinking about this. It's hard to do deleting a whole user account a distributed way. We've never done it right in StatusNet; there's always a little residue...

@SteveBell Actually, it's not "basic functionality". It's pretty hard, as I outlined above. Especially hard for federated systems. @michel-sim You can go through and manually delete all your content, unlike...

This is likely to work with a bridge rather than with code internal to pump.io. - Unlike the Facebook, Twitter, etc. bridges, it will probably be two-way. - From either...

At this point in time, I'd suggest writing an OStatus-to-ActivityPub bridge, since it'd be more useful.

@Serkan-devel we are cranking on it right now. I'd expect it for the next version of pump.io, either 5.2.0 or 6.0.0 depending on whether deprecation is backwards-compatible.