Jacob Hoffman-Andrews
Jacob Hoffman-Andrews
Similarly to how update-blocks now handles all block update requests, create an RPC service to process actions for a certain user on demand. Blocktogether.js and stream.js both enqueue actions, which...
Right now the Actions page only describes one of the possible Action states (cancelled-following). It should describe all of them.
Right now each controller just calls mu.compileAndRender(...) directly, which is probably not very efficient. Instead, should move to an engine that can preload all the templates and render them in...
Right now every time updateBlocks is called, it makes a call to insert a large number of TwitterUsers by uid so additional data can be picked up by updateUsers. This...
Right now, in update-blocks, new blocks are diffed against old ones in-memory, after writing the 'complete' flag to the new block batch. Instead, we should create a transaction that covers...
Right now when a user logs in we store their access token and secret in the Express cookie session, and use that to authenticate subsequent requests. The cookie session should...
The Actions page should provide an easy way to reverse selected Actions. This should also work on clusters (per #95). So for instance, if you blocked a large list of...
It should be possible to paste in a list of screen names or uids in a text area, and ask Block Together to block all of them for you.
When viewing someone else's block list it would be nice to have a column for whether you follow or block each of the users. Ideally this should also be sortable....
Right now if a streaming user (one with 'block new users' enabled) revokes the app, the app will get a message indicating that and will respond by deleting the user...