{"action":"created","issue":{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1267","labels_url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1267/labels{/name}","comments_url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1267/comments","events_url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1267/events","html_url":"https://github.com/globaleaks/GlobaLeaks/issues/1267","id":74891846,"number":1267,"title":"Make it easier delete multiple Tips for a receiver","user":{"login":"vecna","id":89555,"avatar_url":"https://avatars.githubusercontent.com/u/89555?v=3","gravatar_id":"","url":"https://api.github.com/users/vecna","html_url":"https://github.com/vecna","followers_url":"https://api.github.com/users/vecna/followers","following_url":"https://api.github.com/users/vecna/following{/other_user}","gists_url":"https://api.github.com/users/vecna/gists{/gist_id}","starred_url":"https://api.github.com/users/vecna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vecna/subscriptions","organizations_url":"https://api.github.com/users/vecna/orgs","repos_url":"https://api.github.com/users/vecna/repos","events_url":"https://api.github.com/users/vecna/events{/privacy}","received_events_url":"https://api.github.com/users/vecna/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/labels/C:%20GLBackend","name":"C: GLBackend","color":"02e10c"},{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/labels/OTF-D8.6:%20Make%20it%20easier%20to%20delete%20multiple%20Tips","name":"OTF-D8.6: Make it easier to delete multiple Tips","color":"e6e6e6"},{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/labels/OTF-D8:%20Flood%20Resiliency","name":"OTF-D8: Flood Resiliency","color":"e6e6e6"},{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/labels/U:%20Receiver","name":"U: Receiver","color":"e102d8"}],"state":"open","locked":false,"assignee":{"login":"vecna","id":89555,"avatar_url":"https://avatars.githubusercontent.com/u/89555?v=3","gravatar_id":"","url":"https://api.github.com/users/vecna","html_url":"https://github.com/vecna","followers_url":"https://api.github.com/users/vecna/followers","following_url":"https://api.github.com/users/vecna/following{/other_user}","gists_url":"https://api.github.com/users/vecna/gists{/gist_id}","starred_url":"https://api.github.com/users/vecna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vecna/subscriptions","organizations_url":"https://api.github.com/users/vecna/orgs","repos_url":"https://api.github.com/users/vecna/repos","events_url":"https://api.github.com/users/vecna/events{/privacy}","received_events_url":"https://api.github.com/users/vecna/received_events","type":"User","site_admin":false},"milestone":null,"comments":18,"created_at":"2015-05-10T10:44:48Z","updated_at":"2015-06-28T14:58:37Z","closed_at":null,"body":"In case of congestion, tips need to be deleted without clicking on every button from the outside, and without having a warning every time is clicked on it, and without having a DELETE command for every Tip. Still, thinking to the open data feed + end2end encryption change seriously this issue. so before think to the steps proposed, is better if we analyze the doubts below.\r\n\r\n### Steps\r\n\r\n  * delete button has to be moved in another point of the page\r\n  * Receiver \"select\" the tip in order to apply the command later, like gmail with the delete\r\n  * REST API taking a list of Tip ID\r\n\r\n### Doubts \r\n \r\nI don't think this procedure can solve a flood in the end2end model. The preview will not be usable anymore, the user will require the possibility to tag/name a Tip like #1156 and for sure an user will access to **all** the tip before delete them. \r\n\r\nIn addition, the delete concept maybe should be forget. the \"action\" that a receiver express is \"this tip is meaningful to be analyzed\" or \"this tip is not meaningful\", the effect for the receiver will be the same, but for the open data feed this will correspond more truthfully to \"10 submission received, 90% shit\" and not to \"10 submission received, 20% shit\" (with 70% deleted, not disclosed).  \r\n\r\n\r\n\r\n<bountysource-plugin>\r\n---\r\nWant to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/14045217-make-it-easier-delete-multiple-tips-for-a-receiver?utm_campaign=plugin&utm_content=tracker%2F316378&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F316378&utm_medium=issues&utm_source=github).\r\n</bountysource-plugin>"},"comment":{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/comments/116288815","html_url":"https://github.com/globaleaks/GlobaLeaks/issues/1267#issuecomment-116288815","issue_url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1267","id":116288815,"user":{"login":"evilaliv3","id":217034,"avatar_url":"https://avatars.githubusercontent.com/u/217034?v=3","gravatar_id":"","url":"https://api.github.com/users/evilaliv3","html_url":"https://github.com/evilaliv3","followers_url":"https://api.github.com/users/evilaliv3/followers","following_url":"https://api.github.com/users/evilaliv3/following{/other_user}","gists_url":"https://api.github.com/users/evilaliv3/gists{/gist_id}","starred_url":"https://api.github.com/users/evilaliv3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/evilaliv3/subscriptions","organizations_url":"https://api.github.com/users/evilaliv3/orgs","repos_url":"https://api.github.com/users/evilaliv3/repos","events_url":"https://api.github.com/users/evilaliv3/events{/privacy}","received_events_url":"https://api.github.com/users/evilaliv3/received_events","type":"User","site_admin":false},"created_at":"2015-06-28T14:58:37Z","updated_at":"2015-06-28T14:58:37Z","body":"i agree but i i do not find that we should waste a column for this right now. as you suggested we should allow user to define short names for context/receivers/fields to  be used in such this visualizations.\r\n\r\nanyway stop using this ticket takinking about whatever comes to your mind and eventually open new one.\r\nnext out of topic comments will be from now on deleted silently :)"}}